Page History
| Warning | ||
|---|---|---|
| ||
Please note that the articles in this documentation feature media from app version 2.0.5. Interface elements may differ in newer versions. Refer to the latest app version for the most accurate information. |
| Table of Contents |
|---|
What is a risk?
...
- Internals
- listen to your team, and pair with other team members, including developers, to expose risks that otherwise could escape
- Product Context & Market
- listen to your users to understand what's important to them, what they most value, and the things that frustrate them the most; these will give ideas of potential risks
- listen to your business and what's important to them, be on the same page, and don't ignore aspects that ultimately matter to your company and management
- experiment with similar products, as you'll gain knowledge about what common and sometimes implicit expectations users may have whenever using your own product
- Success
- try to understand what "success" means to different stakeholders
- understand "where the money comes from" vs. "what are the common user/usage flows"
- Background Knowledge
- learn more about quality attributes, to become aware of different aspects that people value differently; these are the different dimensions of quality that we can have in the back of our mind that inform us about what risks can target quality aspects
- learn more about heuristics tailored for testing, as these can be used to provide some ideas for test charters but also ideas for many diverse experiments during the test session itself