Posted by tac_admin, August 23, 2011

Requirements Management in the Capability Maturity Model (CMM)

The CMM provides a framework for process improvement that consists of key process areas or organizational activities that have been found to be influential in various aspects of the development process and software quality.

The purpose of requirements management is to establish a common understanding between the customer and the software team of the customer’s requirements. The first key in getting from level 1 to level 2 of the CMM is requirements management.

Levels of CMM:

  1. Initial: Ad hoc, even chaotic; success depends solely on individual heroics and efforts.
    • Key Process Areas
      • N/A
  2. Repeatable: Basic project management to track application functionality, cost, and schedule.
    • Key Process Areas:
      • Requirements management
      • Software project planning
      • Software project tracking and oversight
      • Software subcontract management
      • Software quality assurance
      • Software configuration management
  3. Defined: The process for management and engineering is documented, standardized, and integrated. All projects us an approved, tailored version of the process.
    • Key Process Areas
      • Organization process focus
      • organization process definition
      • Training program
      • Integrated software management
      • Software product engineering
      • Intergroup coordination
      • Peer reviews
  4. Managed: Detailed measures of the software process and software quality metrics are collected. Both process and software products are understood and controlled.
    • Key Process Areas
      • Quantitative process management
      • Software quality management
  5. Optimizing: Continuous process improvement is enabled by use of metrics and from piloting innovative ideas and technologies.
    • Key Process Areas
      • Defect prevention
      • Technology change management
      • Process change management

One response to “Requirements Management in the Capability Maturity Model (CMM)”

  1. […] A business analyst has to be prepared and trained in office productivity applications, so he or she can document and track requirements. […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Get in touch today

Speak directly with The Analyst Coach
and get pointed in the right direction.





Preferred Contact EmailPhone

Subscribe to receive our free white paper on how weak requirements effect strong companies




tesra-circleanalyst

Sign up to get your FREE Business Analyst Survival Guide

Don't worry, we hate spam too. We will never share your information to third parties.