Requirements Life Cycle Management
Describes how to manage and maintain requirements and design information from inception through retirement — ensuring traceability, reuse, prioritization, change control, and approval.
Manages requirements from first capture to retirement — tracing, prioritising, approving, and changing them.
Requirements have a life longer than the project that produced them. RLCM is what stops a backlog turning into a graveyard: every requirement remains traceable to a need, prioritised against value, and changed under explicit control. Twenty per cent of the ECBA exam lives here for that reason.
In practice
The BA traces requirements both ways (need → requirement → design → test, and back), keeps them current as understanding evolves, prioritises them by value, urgency, risk and dependencies, assesses every proposed change for impact, and routes them through agreed approval before work continues.
Relationships with other knowledge areas
- →Consumes confirmed information from Elicitation & Collaboration.
- →Operates inside the governance defined by BAPM.
- →Provides the prioritised, approved input that Requirements Analysis & Design Definition turns into specifications.
- →Surfaces traceability that Solution Evaluation needs to assess delivered value.
Where this lands on the exam
BACCM touchpoints
- Need. Every requirement is traceable to a Need and survives only as long as the Need does.
- Value. Prioritisation is value-led, not feature-led.
- Change. Requirement changes are themselves changes — assessed, approved, and tracked.
Language to listen for in scenario stems
When a stem says 'a requirement has changed', 'two stakeholders disagree', 'we need to know what else this affects', or 'who must approve' — it is RLCM.
Key concepts
The ideas that anchor everything else in this knowledge area.
Linking requirements forward and backward — to source, to related requirements, to designs, to test cases — so impact and coverage can be assessed.
Keeping requirements accurate, current, and reusable as the initiative evolves.
Ordering requirements by value, urgency, risk, dependency, and effort.
Reaching consensus from authorized stakeholders that a requirement or design is ready to act on.
Common pitfalls
Patterns that frequently cost initiatives — and exam points.
- ⚠No traceability — change impact becomes guesswork.
- ⚠'Approved' that isn't really approved by the right people.
- ⚠Stale requirements lingering in the backlog forever.
- ⚠Prioritization driven by loudest stakeholder, not by value.
Tasks
The 5 tasks that make up this knowledge area. Click any task to expand its inputs, outputs, techniques, and guidelines. Technique tags are clickable.