When mining requirements, you should take into account the broader context. You must identify what potential problems may have a negative impact on your product in the future. Those risks often come from the outside. Let's revisit our Uber-like service scenario. An example risk for your service could be a potential change in legislation: you should be aware that some countries may try to change the law to remove you from their market. Uber's way to mitigate those risks is to have local partners cope with regional limitations.
Future risks aside, you must also be aware of current issues, such as the lack of subject matter experts in the company, or heavy competition on the market. Here's what you can do:
- Be aware of and note any assumptions being made. It's best to have a dedicated document for tracking those.
- Ask questions to clarify or eliminate your assumptions, if possible.
- You need to consider the dependencies inside your project, as they can...
