Confirmed users
1,867
edits
MDN/QA/testplan: Difference between revisions
Jump to navigation
Jump to search
m
→ToDO Complete a risk assessment
m (→Open Questions) |
|||
| Line 39: | Line 39: | ||
==ToDO Complete a risk assessment== | ==ToDO Complete a risk assessment== | ||
* The team discusses and agrees a set of risks that they are comfortable with assuming. Assumed risk isn’t a static conversation, but it is good to build a skeleton that the team can agree on and enhance over time. | * The team discusses and agrees on a set of risks that they are comfortable with assuming. Assumed risk isn’t a static conversation, but it is good to build a skeleton that the team can agree on and enhance over time. | ||
* The product should be broken into user stories so a team can apply a hierarchy of risk. It is important to identify and engage as many stakeholders as possible, each individual will have a unique and important point of view. | * The product should be broken into user stories so a team can apply a hierarchy of risk. It is important to identify and engage as many stakeholders as possible, each individual will have a unique and important point of view. | ||