Requirements management is the systematic process of eliciting, documenting, analyzing, tracking, and validating the needs and expectations of stakeholders throughout a project's lifecycle. Rooted in business analysis and systems engineering, it serves as the critical bridge between stakeholder vision and successful delivery, ensuring that what gets built aligns with what's actually needed. A well-managed requirements process prevents costly rework, scope creep, and project failureβstudies consistently show that requirements defects discovered late in development cost exponentially more to fix than those caught early. The discipline balances competing concerns: capturing enough detail to be actionable while remaining flexible enough to accommodate change, all while maintaining traceability from business goals through implementation to acceptance testing.
What This Cheat Sheet Covers
This topic spans 12 focused tables and 111 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Requirements Elicitation Techniques
| Technique | Example | Description |
|---|---|---|
One-on-one: "Walk me through your daily workflow"Group: Round-robin discussion with 3-5 SMEs | Structured or semi-structured conversations with stakeholders to gather detailed information about needs, processes, and constraints. | |
Full-day facilitated session with cross-functional teamCollaborative whiteboard mapping of user journey | Joint Application Development sessions bringing together stakeholders, users, and developers to collaboratively define requirements in real-time. | |
Rapid ideation: Generate 50 ideas in 15 minutesMind mapping clustered by theme | β’ Group creativity technique to generate a large number of ideas quickly β’ encourages wild ideas without judgment. | |
Shadow customer service rep for 2 hoursTime-motion study of warehouse process | Watching users perform actual tasks in their work environment to discover unstated needs and workflow inefficiencies. | |
Online form with Likert scale + open-ended questionsNPS survey sent to 1,000 users | β’ Structured data collection from a large number of stakeholders β’ useful for quantifying opinions and priorities. | |
8-10 users discuss feature prototypes for 90 minutesFacilitated discussion with target demographics | Moderated group discussion to explore attitudes, perceptions, and preferences about a product or concept. |