Requirements definition and management REQM
Managing requirements through the entire delivery and operational lifecycle.
Revision notes
Updates for SFIA 9
- Minor changes to content only.
- You can move to SFIA 9 when you are ready - SFIA 8 skill descriptions will still be available to use.
- Previous SFIA assessments or skills mapping are not impacted by this change.
Guidance notes
Requirements may be related to software, systems, data, processes, products or services.
Activities may include, but are not limited to:
- eliciting and analysing requirements, both functional and non-functional
- ensuring customer requirements, priorities and acceptance criteria are accurately captured and validated
- organising and prioritising requirements using techniques such as, but not limited to, product roadmaps, epics, user stories and backlogs
- specifying and validating requirements, constraints and acceptance criteria to a level that enables effective development and operations of new or changed software, systems, processes, products or services
- negotiating trade-offs that are acceptable to key stakeholders and within budgetary, technical, regulatory and other constraints
- adopting and adapting requirements management lifecycle models.
The requirements lifecycle approach will be based on the context of the work and may be selected from predictive (plan-driven) or adaptive (iterative/agile) approaches.
Understanding the responsibility levels of this skill
Where lower levels are not defined...
- Specific tasks and responsibilities are not defined because the skill requires a higher level of autonomy, influence, and complexity in decision-making than is typically expected at these levels. You can use the essence statements to understand the generic responsibilities associated with these levels.
Where higher levels are not defined...
- Responsibilities and accountabilities are not defined because these higher levels involve strategic leadership and broader organisational influence that goes beyond the scope of this specific skill. See the essence statements.
Developing skills and demonstrating responsibilities related to this skill
The defined levels show the incremental progression in skills and responsibilities.
Where lower levels are not defined...
You can develop your knowledge and support others who do have responsibility in this area by:
- Learning key concepts and principles related to this skill and its impact on your role
- Performing related skills (see the related SFIA skills)
- Supporting others who are performing higher level tasks and activities
Where higher levels are not defined...
- You can progress by developing related skills which are better suited to higher levels of organisational leadership.
Click to learn why SFIA skills are not defined at all 7 levels.
Show/hide extra descriptions and levels.
Levels of responsibility for this skill
2 | 3 | 4 | 5 | 6 |
Level 1
Requirements definition and management: Level 2
Uses standard techniques to elicit, specify and document requirements for simple subject areas with clearly-defined boundaries.
Assists in the definition and management of requirements.
Assists in the creation of a requirements baseline/backlog.
Assists in investigating and applying changes to requirements.
Requirements definition and management: Level 3
Defines and manages scoping, requirements definition and prioritisation activities for small-scale changes and assists with more complex change initiatives.
Follows agreed standards and applies appropriate techniques to elicit and document detailed requirements. Provides constructive challenge to stakeholders as required. Reviews requirements for errors and omissions.
Prioritises requirements and documents traceability to source.
Provides input to the requirements baseline/backlog. Investigates, manages and applies requests for changes to requirements, in line with change management policy.
Requirements definition and management: Level 4
Defines and manages scoping, requirements definition and prioritisation activities for initiatives of medium size and complexity.
Contributes to selecting the requirements approach.
Facilitates input from stakeholders, provides constructive challenge and enables effective prioritisation of requirements.
Establishes requirements baselines or backlogs, obtains appropriate agreement to requirements and ensures traceability to source.
Requirements definition and management: Level 5
Plans and drives scoping, requirements definition and prioritisation activities for large, complex initiatives.
Selects, adopts and adapts appropriate requirements definition and management methods, tools and techniques. Contributes to the development of organisational methods and standards for requirements management.
Obtains input and agreement to requirements from a diverse range of stakeholders. Negotiates with stakeholders to manage competing priorities and conflicts.
Establishes requirements baselines or backlogs. Ensures changes to requirements are investigated and managed.
Requirements definition and management: Level 6
Champions the importance and value of requirements management principles and selecting effective requirements management lifecycle models.
Develops organisational policies, standards and guidelines for requirements definition and management.
Plans and leads scoping, requirements definition and priority setting for complex, strategic programmes.
Drives adoption of, and adherence to, policies and standards. Develops new methods and organisational capabilities for requirements management.