Requirements
Manage requirements and their traceability throughout the IT solutions delivery life cycle to serve business needs.
Improvement Planning
Practices-Outcomes-Metrics (POM)
Representative POMs are described for Requirements at each level of maturity.
- 1Initial
- Practice
- Practices are ad hoc and are on a best endeavour basis.
- 2Basic
- Practice
- Gather both functional and non-functional requirements within IT through qualitative data collection techniques such as interviews and workshops.
- Outcome
- The IT solution delivered will address the IT requirements of the organization.
- Metric
- # of IT requirements specified.
- 3Intermediate
- Practice
- Engage and Involve all relevant stakeholders (business & IT) and users as necessary during the requirements gathering process.
- Outcome
- Ensures both functional and non-functional requirements from both IT and other business units are gathered resulting in increased buy-in by stakeholders.
- Metric
- % of stakeholders made up from IT and other business units involved in the requirements gathering process.
- 4Advanced
- Practice
- Evaluate methods to allow user/business requirements to be traced from requirements source to design, implementation and testing (in both directions).
- Outcome
- Methods are available to allow requirements to be traced in both directions throughout the Solutions Delivery lifecycle.
- Metric
- % of requirements traceability methods that allow bidirectional traceability through the full Solutions Delivery lifecycle.
- 5Optimized
- Practice
- Introduce new and emerging innovative methods and techniques for requirements gathering, analysis, design and implementation into Solutions Delivery on a continual basis with external stakeholder input.
- Outcome
- The quality of the implemented IT solution is improved.
- Metric
- # of requirements gathering methods introduced with input from external stakeholders.