Requirements Capture
Also Known As
- Enablers (in Scaled Agile Framework (SAFe))
- Features (in Scaled Agile Framework (SAFe))
- Full-Kitting (in TameFlow)
- Needs Analysis
- Requirement Elicitation
- Requirement Gathering
- User Stories (in Extreme Programming)
- User Stories (in Scaled Agile Framework (SAFe))
- User Stories (in Scrum)
Related
Addresses / Mitigates
- Feature Fit Risk: Ensures that features align with client needs and expectations.
- Coordination Risk: Reduces coordination risks around deciding what should be built.
- Communication Risk: Helps in explaining exactly what should be built.
Attendant Risks
- Schedule Risk: Thorough requirements capture can be time-consuming.
Used By
- Extreme Programming: XP captures requirements through user stories and continuous dialogue with the customer.
- Scaled Agile Framework (SAFe): SAFe captures requirements as Features and Stories, refined through backlog grooming.
- Scrum: Capturing requirements is done through user stories and the product backlog in Scrum.
- TameFlow: Full-Kitting ensures all requirements and inputs are gathered before starting work.
- Waterfall Development: The requirements gathering and analysis phase in Waterfall involves collecting and documenting all possible requirements of the system to be developed.
Description
"Requirements capture is the process of collecting information about the requirements of a system or project, typically through discussions and interactions with stakeholders." - Requirements capture, Wikipedia
Requirements Capture involves gathering and documenting the requirements for the software. This process ensures that the development team has a clear and comprehensive understanding of what needs to be built, helping to align the final product with client expectations and reducing the risk of costly changes later in the project.
Variations
| Requirements Type | Description | Reference |
|---|---|---|
| User Stories | Short descriptions of functionality from the user's perspective. | User Story, Wikipedia |
| Use Cases | Detailed descriptions of system interactions for specific goals. | Use Case, Wikipedia |
| Functional Specification | Formal document detailing system behaviour and requirements. | Functional Specification, Wikipedia |
Used By
Extreme Programming
An Agile software development methodology that emphasizes customer satisfaction, teamwork, and frequent delivery of small, functional software increments.
Why: XP captures requirements through user stories and continuous dialogue with the customer.
- User Stories
Scaled Agile Framework (SAFe)
A set of organization and workflow patterns for scaling lean and agile practices across large enterprises.
Why: SAFe captures requirements as Features and Stories, refined through backlog grooming.
- Features
- User Stories
- Enablers
Scrum
An Agile framework for managing and completing complex projects.
Why: Capturing requirements is done through user stories and the product backlog in Scrum.
- User Stories
TameFlow
A management approach for knowledge work that integrates Theory of Constraints, Kanban, and Agile principles to optimize the flow of work, information, and value.
Why: Full-Kitting ensures all requirements and inputs are gathered before starting work.
- Full-Kitting
Waterfall Development
A traditional linear and sequential development methodology where each phase must be completed before moving on to the next.
Why: The requirements gathering and analysis phase in Waterfall involves collecting and documenting all possible requirements of the system to be developed.