Intro to Project Management: Project Scope Management - Collecting Requirements, Interviews Focus Groups Surveys Prototypes User Stories Workshops

Collecting Requirements: A Project Manager's Guide

What This Is

Collecting requirements is the process of gathering and documenting the needs and expectations of stakeholders to ensure that the project meets their needs. This is crucial for successful project delivery, as it helps prevent scope creep, reduces rework, and ensures that the project meets its objectives. For example, when building a new software application, collecting requirements involves understanding the needs of the end-users, such as functionality, usability, and performance.

Key Terms & Formulas

• Requirements Gathering: The process of collecting and documenting stakeholder needs and expectations.
• Stakeholder: An individual or group with a vested interest in the project.
• Requirements Document: A document that outlines the project's requirements, including functional and non-functional requirements.
• Functional Requirements: Describe what the system should do.
• Non-Functional Requirements: Describe how the system should behave.
• User Story: A statement that describes a user's need or goal.
• Use Case: A description of how a user interacts with the system.
• Prototyping: A technique used to visualize and test the system's functionality.
• Survey: A method used to collect data from a large group of people.
• Focus Group: A method used to gather feedback from a small group of people.
• Interview: A method used to gather information from an individual or small group.
• Requirements Elicitation Techniques: Methods used to gather and document requirements, such as brainstorming, mind mapping, and SWOT analysis.
• Requirements Validation: The process of verifying that the requirements are complete, consistent, and feasible.
• Requirements Prioritization: The process of ranking requirements based on their importance and urgency.
• ROI (Return on Investment) Analysis: A method used to evaluate the potential return on investment of a project.
• Cost-Benefit Analysis: A method used to evaluate the potential costs and benefits of a project.

Step-by-Step / Process Flow

1. Identify Stakeholders: Determine who has a vested interest in the project and needs to be involved in the requirements gathering process.
2. Develop a Requirements Gathering Plan: Create a plan that outlines the requirements gathering techniques, timelines, and resources needed.
3. Gather Requirements: Use various techniques, such as interviews, focus groups, surveys, and prototyping, to gather requirements from stakeholders.
4. Document Requirements: Create a requirements document that outlines the project's requirements, including functional and non-functional requirements.
5. Validate Requirements: Verify that the requirements are complete, consistent, and feasible.
6. Prioritize Requirements: Rank requirements based on their importance and urgency.
7. Develop a Requirements Management Plan: Create a plan that outlines how requirements will be managed throughout the project.

Common Mistakes

• Mistake: Not involving stakeholders in the requirements gathering process.
• Correction: Involve stakeholders in the requirements gathering process to ensure that their needs and expectations are met.
• Mistake: Not validating requirements.
• Correction: Validate requirements to ensure that they are complete, consistent, and feasible.
• Mistake: Not prioritizing requirements.
• Correction: Prioritize requirements to ensure that the most important and urgent requirements are addressed first.

Exam Tips

• Tip: Be able to describe the different requirements gathering techniques and when to use them.
• Tip: Understand the importance of validating requirements and how to do it.
• Tip: Be able to explain the difference between functional and non-functional requirements.

Quick Practice Questions

1. If a project has a CPI (Cost Performance Index) of 0.8, is the project under or over budget? Answer: Under budget. Explanation: A CPI of 0.8 indicates that the project is performing better than expected, resulting in a lower cost.
2. What is the purpose of a requirements document? Answer: To outline the project's requirements, including functional and non-functional requirements. Explanation: A requirements document provides a clear understanding of the project's objectives and scope.
3. What is the difference between a user story and a use case? Answer: A user story describes a user's need or goal, while a use case describes how a user interacts with the system. Explanation: User stories are typically used in Agile development, while use cases are used in more traditional development methodologies.

Last-Minute Cram Sheet

• Requirements Gathering: The process of collecting and documenting stakeholder needs and expectations.
• Stakeholder: An individual or group with a vested interest in the project.
• Requirements Document: A document that outlines the project's requirements, including functional and non-functional requirements.
• Functional Requirements: Describe what the system should do.
• Non-Functional Requirements: Describe how the system should behave.
• User Story: A statement that describes a user's need or goal.
• Use Case: A description of how a user interacts with the system.
• Prototyping: A technique used to visualize and test the system's functionality.
• Survey: A method used to collect data from a large group of people.
• Focus Group: A method used to gather feedback from a small group of people.
• Interview: A method used to gather information from an individual or small group.
• Requirements Elicitation Techniques: Methods used to gather and document requirements, such as brainstorming, mind mapping, and SWOT analysis.
• Requirements Validation: The process of verifying that the requirements are complete, consistent, and feasible.
• Requirements Prioritization: The process of ranking requirements based on their importance and urgency.
• ROI (Return on Investment) Analysis: A method used to evaluate the potential return on investment of a project.
• Cost-Benefit Analysis: A method used to evaluate the potential costs and benefits of a project.
• CPI (Cost Performance Index): A measure of a project's cost performance, calculated as EV / AC.
• EV (Earned Value): The value of work completed, calculated as % complete × BAC.
• BAC (Budget at Completion): The total budget for the project.
• SV (Schedule Variance): The difference between the planned and actual schedule, calculated as EV / PV.
• CV (Cost Variance): The difference between the planned and actual cost, calculated as EV / AC.