3395 Registered Users
Skip Navigation LinksHome > ITTO Section > Project Scope Management > Collect Requirements


- Collect Requirements Process deals with converting project needs to stakeholder requirements.
- Requirements are the basis for scope baseline and other aspects like cost and quality planning.
- Requirements are classified as follows :
- Business Requirements
- Stakeholder Requirements
- Solution Requirements
> Functional Requirements
> Non-Functional Requirements
- Transition Requirements
- Project Requirements
- Quality Requirements
- Requirements can be functional or technical
- While many requirements might be collected as part of this process, not all make it to the project scope and that decision is based on different constraints. The purpose of Collect Requirements Process is to collect and prioritize stakeholder requirements.


- Scope Management Plan: The Scope Management Plan provides guidance for different processes in Scope knowledge area. Scope Management Plan specifies the boundaries in terms of what type of requirements need to be collected.
- Requirements Management Plan: This has details about the collect requirements process specific to this project.
- Stakeholder Management Plan: This has the process details about how different stakeholder needs will be handled based on the project context.
- Project Charter: The project charter has the high-level project requirements, helping in detailing of the project requirements.
- Stakeholder Register: While detailing the project requirements, it is necessary to ensure all stakeholders in the project are accounted.

Tools & Techniques

- Interviews: One-to-one discussions with stakeholders with prepared set of questions to record and analyse the responses to detail the requirements.
- Focus Groups: Sometimes a specific combination of stakeholders involving SMEs, moderated in a controlled environment might get better throughput in the collect requirements process.
- Facilitated Workshops: In case of workshops, the end-users and the design / development team sit together to understand the requirements called VoC (Voice of Customer) and coming out with the best possible solution. It is also called as JAD or QFD based on the industry. While Focus Groups are moderated by a mediator, workshops are discussions among cross-functional team aimed at consensus based on priorities.
- Group Creativity Techniques: These are aimed at facilitating creativity or bringing out innovative ideas or out-of-the-box thinking.
- Brainstorming: A group discussion technique aimed at generating ideas.
- Nominal group technique: A group discussion technique with voting process to prioritize ideas.
- Idea/mind mapping: A technique aimed at grouping ideas to get an idea about commonality and differences in a group.
- Affinity Diagram: A technique wherein large number of ideas are categorized into groups for further analysis.
- Multicriteria Decision Analysis: Based on different project criteria the ideas are ranked in order to be analysed and make a decision
- Context Diagrams: This is used to depict interaction between people and processes for a specific context to provide clarity about a specific requirement.
- Document Analysis: Analysis if existing project documents or information might give better clarity about requirements rather than meeting different stakeholders.


- Requirements Documentation: This has the requirements listing with priority. There are different types of requirements –
> Business Requirements
> Stakeholder Requirements
> Solution Requirements
> Project Requirements
> Transition Requirements
- Requirements Traceability Matrix: This document tracks the requirements across different phases. The different sections across the milestone documents part of different phases are mapped in order to ensure that all requirements are covered.

Match the Following

1. Prototypes - a. Voting Process
2. Nominal group technique - b. Storyboards
3. Workshop - c. Job Shadowing
4. Observation - d. QFD
5. Surveys – e. Commonality and Differences
6. Idea/mind mapping – f. Statistical Analysis
7. Affinity Diagram – g. Group Classification

Match the Following (Answers)

1. Prototypes - b. Storyboards
2. Nominal group technique - a. Voting Process
3. Workshop - d. QFD
4. Observation - c. Job Shadowing
5. Surveys – f. Statistical Analysis
6. Idea/mind mapping – e. Commonality and Differences
7. Affinity Diagram – g. Group Classification