| 1 | 7 | ||||||||||||||||||||||
| 9 | |||||||||||||||||||||||
| 2 | |||||||||||||||||||||||
| 3 | |||||||||||||||||||||||
| 4 | |||||||||||||||||||||||
| 8 | 5 | ||||||||||||||||||||||
| 6 | |||||||||||||||||||||||
1. Reviewing existing documentation such as project charters, business cases, and user manuals to extract requirements and insights from stakeholders.
2. The process of gathering and documenting requirements from stakeholders through various techniques such as interviews, surveys, and workshops.
3. A person or organization with a vested interest or concern in the project and its outcomes.
4. A facilitated discussion with a small group of stakeholders to gather diverse perspectives and insights on the project requirements.
5. A method of obtaining stakeholder requirements by holding one-on-one discussions to gather insights and information.
6. Creating a working model or prototype of the project to gather feedback and refine requirements based on stakeholder input.
7. A technique that involves directly observing stakeholders in their natural environment to understand their behaviors and interactions.
8. Interactive sessions with stakeholders to discuss and prioritize project requirements, facilitate collaboration, and reach consensus on key priorities.
9. A creative technique used to generate ideas and solutions for project requirements through a collaborative and structured group session.