Requirements definition and management REQM

(modified)

Managing requirements through the entire delivery and operational life cycle.

Guidance notes

(new)

Requirements may be related to software, systems, data, processes, products or services.

Activities may include - but are not limited to...

  • eliciting and analysing requirements
  • specifying and validating requirements and constraints to a level that enables effective development and operations of new or changed software, systems, processes, products and services
  • negotiating trade-offs that are acceptable to key stakeholders and within budgetary, technical, regulatory, and other constraints
  • adopting and adapting of requirements management life cycle models

The requirements life cycle approach will be based on the context of the work and may be selected from predictive (plan-driven) or adaptive (iterative/agile) approaches.

Requirements definition and management: Level 6

(modified)

Develops organisational policies, standards, and guidelines for requirements definition and management. Champions the importance and value of requirements management principles and the selection of appropriate requirements management life cycle models. Drives adoption of, and adherence to, policies and standards. Develops new methods and organisational capabilities. Plans and leads scoping, requirements definition and priority setting for complex, strategic programmes.

Requirements definition and management: Level 5

(modified)

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. Obtains input from, and formal agreement to, requirements from a diverse range of stakeholders. Negotiates with stakeholders to manage competing priorities and conflicts. Establishes requirements baselines. Ensures changes to requirements are investigated and managed. Contributes to the development of organisational methods and standards.

Requirements definition and management: Level 4

(modified)

Establishes the requirements base-lines, obtains formal agreement to requirements, and ensures traceability to source. Contributes to selection of the requirements approach. Defines and manages scoping, requirements definition and prioritisation activities for initiatives of medium size and complexity. Facilitates input from stakeholders, provides constructive challenge and enables effective prioritisation of requirements. Reviews requirements for errors and omissions. Investigates, manages, and applies authorised requests for changes to base-lined requirements, in line with change management policy.

Requirements definition and management: Level 3

(unchanged)

Defines and manages scoping, requirements definition and prioritisation activities for small-scale changes and assists with more complex change initiatives. Follows agreed standards, applying appropriate techniques to elicit and document detailed requirements. Provides constructive challenge to stakeholders as required. Prioritises requirements and documents traceability to source. Reviews requirements for errors and omissions. Provides input to the requirements base-line. Investigates, manages and applies authorised requests for changes to base-lined requirements, in line with change management policy.

Requirements definition and management: Level 2

(modified)

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. Assists in investigating and applying authorised changes.