The term 'Management' in CMMI-SVC context refers to Senior Management or High-level Management. This includes an individual or group possessing the organizational authority and accountability to:
Establish, approve, and authorize organizational policies and standards for service delivery.
Allocate and commit resources (personnel, funds, infrastructure) needed to implement policies and achieve service objectives.
Resolve issues that are beyond the scope or authority of operational or project management.
They typically review the effectiveness and health of the organization's standard service processes and the overall performance of the service delivery system, rather than engaging in the daily execution or detailed technical management of specific projects or programs.
In Large or Medium-Sized Organizations, establishing the High-Level Management for CMMI-SVC is based on functional authority, not merely a reporting title. This role, often referred to as Senior Management, is typically held by an individual or group that is:
Accountable for the organizational business objectives and performance of the entire service delivery domain.
Authorized to establish, approve, and institutionalize organizational standard service processes (Policy Setting Authority).
Authorized to commit organizational resources (e.g., infrastructure budget, strategic personnel/training) beyond the scope of a single program or project.
This level is usually one or two steps removed from the day-to-day operational management (e.g., Project/Program Managers). For instance, the Vice President or Director overseeing all service delivery who reports to the C-Suite and holds the policy-setting authority is often the correct choice.
The PMO (Project/Program Management Office) or the Service Management Office is typically excluded from this role, as their function is generally operational (managing execution, resource deployment, and process compliance), lacking the necessary organizational strategic policy and resource commitment authority.
In Small or Tiny Organizations (where staff take on multiple roles), Senior Management is defined by the individual or small group that possesses ultimate organizational authority over the service delivery function. This could be:
The CEO, Owner, or Managing Partner.
The Delivery/Service Head who reports directly to the CEO and has full authority to define the organization's service policies and commit necessary resources.
The Key Criteria Remains Authority: This person or group must be empowered to establish and change organizational standard service processes and authorize significant resource allocation for service improvements.
Crucially, the QA Head typically reports to Senior Management (to ensure independence) but does not generally serve as a voting member of the Senior Management body when that body is performing the high-level decision-making and policy-setting functions required by CMMI. Their input is presented, but their role is assurance, not management resolution.
The fundamental value of Management Reviews (MRs) is to ensure that the service delivery system and its processes are effectively managed, continually aligning organizational performance with the overall business objectives. They provide Senior Management with the necessary objective insight to govern the organization's service capabilities and resolve systemic issues that operational management cannot address.
The purpose of Management Reviews (MR) is to enable Senior Management to formally govern and oversee the institutionalization and effectiveness of the service system.
The review primarily focuses on:
Service Performance and Progress: A summary of organizational service performance, status against strategic objectives, and aggregated progress of service projects/programs.
Process Health and Compliance: Reviewing the results of Process and Product Quality Assurance (PPQA) activities, including noncompliance issues, trends, and organizational process strengths/weaknesses.
Systemic Risks and Issues: Examining high-level risks that impact the organization's ability to achieve its service objectives and inter-group issues that operational management cannot resolve.
Resource and Policy Needs: Evaluating the adequacy of committed resources and assessing the need to change or update organizational standard service policies and infrastructure (which they are authorized to do).
In essence, Management Reviews ensure that the organizational standard processes are effective, appropriately resourced, and continually aligned with the business objectives.
The frequency of Management Reviews (MR) in a short-cycle service environment is primarily determined by the organizational service cadence and the need for timely governance oversight before systemic issues become irreversible. CMMI supports two primary cadences:
Periodic Reviews: These reviews are scheduled to coincide with the natural operational rhythm of the service projects.
Typical Cadence for Short Projects: For services spanning one month or less, the periodic review is often conducted Monthly, Bi-Weekly, or, most effectively, at the close of a specified service cycle (End-of-Service Review). This ensures that lessons learned, aggregate resource consumption, and systemic compliance data are reviewed promptly.
Event-Driven Reviews: These are mandatory, immediate reviews triggered by high-impact events that threaten business objectives, serving as a critical governance check.
Relevant Events: These are often set based on thresholds, such as the breach of a critical organizational performance metric, a major process non-compliance finding by QA, or the initiation of a new organizational strategic objective that requires resource commitment.
The frequency must be high enough to allow Senior Management to govern, not just audit, the service system effectively, given the rapid turnaround of the services.
In contrast to the rapid-cycle approach of smaller firms, large organizations and government contractors typically adhere to a more formal and less frequent cadence for Management Reviews (GP 2.10). This approach is necessary due to the hierarchical structure, the complexity of cross-organizational resource allocation, and the long duration of service programs.
Periodic Reviews: These are scheduled to coincide with business planning and financial reporting cycles.
Typical Cadence: Quarterly (every three months) or Semi-Annually (every six months). This frequency ensures that the Senior Management team reviews summarized, aggregated performance metrics across portfolios or business units, allowing for decisions on large-scale organizational policy changes, infrastructure investment, and long-term risk mitigation.
Event-Driven Reviews: These remain critical but are triggered only by events with significant strategic or financial impact on the organization as a whole.
Relevant Events: Examples include the failure of a critical service system component, an adverse external audit report, or a major, systemic organizational risk (e.g., security breach, compliance failure) that demands immediate resource commitment from the executive level.
The fundamental difference lies in tempo and scope: large organizations review for strategic stability and organizational governance, while small, rapid environments review for timely tactical adjustment and immediate process health.
The execution of the Management Review must be defined as a formal process, which can be clearly structured using the ETVX (Entry, Task, Validation, Exit) model:
1. Entry (The Required Inputs)
Entry is satisfied by the review frequency (Periodic or Event-Driven) and the preparation of all required, objective data (the 'go/no-go' for holding the meeting). This includes:
The compilation of data from across the organization, such as: aggregate service performance metrics, summaries of Process and Product Quality Assurance (PPQA) non-compliance, current high-level risk status, and resource usage reports.
The identification of the responsible person (typically the management delegate) for compiling and presenting each data set.
2. Task (The Review Execution)
The Task is the execution of the meeting itself. This involves:
Adhering to a defined agenda that is aligned with organizational business objectives.
Formally evaluating the compiled data against objective criteria for success (e.g., meeting established performance thresholds for process health).
Documenting formal minutes that capture the presentation of facts, the discussion, and the authorized decisions.
3. Validation and Exit (Decisions and Closure)
Exit is defined by the generation of authorized and trackable outputs.
Outputs are not merely decisions; they are recorded, assigned actions that authorize necessary policy changes, resource commitments, or systemic corrective measures.
Validation is the process of tracking these actions to closure using the organization's governance mechanism, ensuring that the issues raised by Senior Management are resolved at the organizational level, thereby closing the management control loop.