Home

PM Insights

« 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.

Figure 1 - Requirements Discovery Techniques Figure 1 – Requirements Discovery Techniques

Requirements workshop

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:

  1. Who owns the scope and cost of the project?
  2. Who can provide the required guidance on the functionality of the new system?
  3. Who could be impacted by the new system?
  4. Who…

View original post 653 mots de plus

Publicités

Laisser un commentaire

Choisissez une méthode de connexion pour poster votre commentaire:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s