Gathering requirements
Regardless of a project's size, well-defined requirements are critically important because they define the purpose of any project. If these requirements are not clearly defined and agreed upon, they can lead to severe consequences at all stages of development, for example, the functionality does not meet user expectations, or the project encounters technical difficulties not foreseen at the initial stages. Therefore, it is necessary to pay attention to the process of gathering and analyzing requirements.
Knowing the context
When mining requirements, you should consider 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...
