Click on the underlined words for more information on these tools.
The linked documents may contain variations but are very useful.
Collecting Stakeholders Requirements is an essential activity before you can define Scope in a written Project Scope Statement. You need to ensure you have identified all your project's Stakeholders, and then collected all their Needs and Expectations. "How can I do that?" you ask. Here are some tools.
Information gathering techniques. Try these!
a) Interviews: formal or informal
b) Focus Groups: interactive, conversational, seeking desired results
e) Questionnaires and Surveys: written, quick, suitable for large population
f) Observations: job shadowing
g) Prototype experience: feedback from working model
h) Benchmarking against other organizations: compare best practices
i) Past projects: lessons learned
Tools for Resolving
Stakeholder Requirements Conflicts
You will need to Resolve Stakeholders Requirements before attempting to define Scope in a written Project Scope Statement. You will be looking for agreement and a sign-off, on your Project Scope Statement , from your Key stakeholders. Here are some tools to help resolve those conflicts.
1. Seek Expert Judgment from:
a) Other units within the organization
c) Your Stakeholders
d) Professional and Technical Associations
e) Industry Groups
f) Other Subject Matter Experts
3. Group Creativity Techniques such as:
b) Affinity Diagram (grouping ideas into categories)
4. Priority Setting
5. Negotiation, concessions (gave and take, trade-off)
6. Higher Authority (refer to higher management). This would usually be a