# Requirements Management

The ongoing practice of organizing, maintaining, tracing, prioritizing, and governing requirements as needs and solutions evolve.

- Type: practice
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/requirements-management/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Define requirement types, attributes, ownership, decision rights, and a shared repository.
2. Record requirements with source, rationale, priority, status, and acceptance evidence.
3. Connect requirements to needs, designs, delivery items, tests, and releases as appropriate.
4. Assess proposed changes and maintain consistent versions and baselines where needed.
5. Review requirement quality, coverage, conflicts, and continuing relevance.
6. Retire obsolete requirements while preserving necessary decision history.

## A 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.

## Where 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.

## Sources

1. [ISO/IEC/IEEE 29148:2018 — Requirements Engineering](<https://www.iso.org/standard/72089.html>) — International Organization for Standardization · International standard
2. [Business Analysis Knowledge Areas](<https://www.iiba.org/knowledgehub/the-business-analysis-standard/5-applying-business-analysis-tasks/5-3-business-analysis-knowledge-areas/>) — International Institute of Business Analysis · Professional standard

## Related topics

- [Product Requirement](<https://wiki.soroush.uk/topic/product-requirement/>)
- [Requirements Traceability](<https://wiki.soroush.uk/topic/requirements-traceability/>)
- [Change Control](<https://wiki.soroush.uk/topic/change-control/>)
