« Requirements cannot be observed or asked for from the users, but have to be created together with all the stakeholders. » – Vesa Torvinen
Figure 1 shows the variety of techniques that can be used for requirements identification during the pre-envisioning/envisioning stage.
The key stakeholders need to be identified before starting the requirements workshop. Key stakeholders are then gathered together for a short time period, typically two or three days. The objective of the workshop is to identify and capture high level features of the product. The workshop can be facilitated by a product owner or a product manager or a business analyst.
The key stakeholders are the following but not limited to:
- Who owns the scope and cost of the project?
- Who can provide the required guidance on the functionality of the new system?
- Who could be impacted by the new system?
View original post 653 mots de plus