Requirements Management
The ongoing practice of organizing, maintaining, tracing, prioritizing, and governing requirements as needs and solutions evolve.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/requirements-management/
01What it means
Requirements management maintains requirements and their relationships throughout a product or system life cycle. It covers status, priority, ownership, versions, traceability, changes, and approvals; requirements engineering is broader and also includes eliciting, analyzing, specifying, verifying, and validating requirements.[1][2]
02Why it matters
Complex products accumulate interdependent customer, business, regulatory, and technical obligations. Managing those obligations helps teams understand change impact, preserve rationale, demonstrate coverage, and avoid building from stale or contradictory information.
03When to use it
Use explicit requirements management when products are regulated, safety-critical, contract-driven, integration-heavy, long-lived, or coordinated across many teams. A small product should apply the principles proportionately rather than create a heavyweight repository.
04How it works
- Define requirement types, attributes, ownership, decision rights, and a shared repository.
- Record requirements with source, rationale, priority, status, and acceptance evidence.
- Connect requirements to needs, designs, delivery items, tests, and releases as appropriate.
- Assess proposed changes and maintain consistent versions and baselines where needed.
- Review requirement quality, coverage, conflicts, and continuing relevance.
- Retire obsolete requirements while preserving necessary decision history.
05A practical example
A health platform links consent requirements to regulations, interface designs, API behavior, acceptance tests, and release evidence. When policy changes, the team can identify affected components and verify the updated behavior without manually searching separate documents.
06Where it breaks
Detailed repositories are costly to maintain and can create false confidence when links are stale. Management does not ensure that requirements are correct or valuable, and excessive control can slow learning in low-risk product areas.
Common mistakes
- Treating requirements management as document storage.
- Recording requirements without source, rationale, or ownership.
- Creating traceability links that nobody maintains or uses.
- Applying safety-critical process weight to every product change.
07Sources
- ISO/IEC/IEEE 29148:2018 — Requirements EngineeringInternational Organization for Standardization · International standardISO/IEC/IEEE 29148:2018 — Requirements Engineering
- Business Analysis Knowledge AreasInternational Institute of Business Analysis · Professional standardBusiness Analysis Knowledge Areas