Confirmed users
1,867
edits
MDN/QA/testplan: Difference between revisions
m
→ToDO Complete a risk assessment
| Line 52: | Line 52: | ||
==ToDO Complete a risk assessment== | ==ToDO Complete a risk assessment== | ||
* 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. | * <strike>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.</strike> | ||
* 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. | ||
* The list of stakeholders often include; project managers, developers, testers, UX, IT, DBAs, the security team, etc. Sometimes the product has high enough visibility in the organization that a proxy for the CEO is beneficial. | * <strike>The list of stakeholders often include; project managers, developers, testers, UX, IT, DBAs, the security team, etc. Sometimes the product has high enough visibility in the organization that a proxy for the CEO is beneficial.</strike> | ||
User stories and features are grouped into three categories | User stories and features are grouped into three categories | ||