The purpose of Project Monitoring and Control (PMC) is to provide an understanding of the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan.
SG 1 Actual project performance and progress are monitored against the project plan.
SP 1.1 Monitor actual values of project planning parameters against the project plan. SP 1.2 Monitor commitments against those identified in the project plan. SP 1.3 Monitor risks against those risks identified in the project plan. SP 1.4 Monitor the management of project data against the project plan. SP 1.5 Monitor stakeholder involvement against the project plan. SP 1.6 Periodically review the project’s progress, performance, and issues. SP 1.7 Review the project’s accomplishments and results at selected project milestones.
SG 2 Corrective actions are managed to closure when the project’s performance or results deviate significantly from the plan.
SP 2.1 Collect and analyze issues and determine corrective actions to address them. SP 2.2 Take corrective action on identified issues. SP 2.3 Manage corrective actions to closure.
PROJECT PLANNING -- PROJECT MANAGEMENT (ML2)
The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.
SG 1 Estimates of project planning parameters are established and maintained.
SP 1.1 Establish a top-level work breakdown structure (WBS) to estimate the scope of the project. SP 1.2 Establish and maintain estimates of work product and task attributes. SP 1.3 Define project lifecycle phases on which to scope the planning effort. SP 1.4 Estimate the project’s effort and cost for work products and tasks based on estimation rationale.
SG 2 A project plan is established and maintained as the basis for managing the project.
SP 2.1 Establish and maintain the project’s budget and schedule. SP 2.2 Identify and analyze project risks. SP 2.3 Plan for the management of project data. SP 2.4 Plan for resources to perform the project. SP 2.5 Plan for knowledge and skills needed to perform the project. SP 2.6 Plan the involvement of identified stakeholders. SP 2.7 Establish and maintain the overall project plan.
SG 3 Commitments to the project plan are established and maintained.
SP 3.1 Review all plans that affect the project to understand project commitments. SP 3.2 Adjust the project plan to reconcile available and estimated resources. SP 3.3 Obtain commitment from relevant stakeholders responsible for performing and supporting plan execution.
PROCESS AND PRODUCT QUALITY ASSURANCE -- SUPPORT (ML2)
The purpose of Process and Product Quality Assurance (PPQA) is to provide staff and management with objective insight into processes and associated work products.
SG 1 Adherence of the performed process and associated work products to applicable process descriptions, standards, and procedures is objectively evaluated.
SP 1.1 Objectively evaluate selected performed processes against applicable process descriptions, standards, and procedures. SP 1.2 Objectively evaluate selected work products against applicable process descriptions, standards, and procedures.
SG 2 Noncompliance issues are objectively tracked and communicated, and resolution is ensured.
SP 2.1 Communicate quality issues and ensure the resolution of noncompliance issues with the staff and managers. SP 2.2 Establish and maintain records of quality assurance activities.
QUANTITATIVE PROJECT MANAGEMENT -- PROJECT MANAGEMENT (ML4)
The purpose of Quantitative Project Management (QPM) is to quantitatively manage the project to achieve the project’s established quality and process performance objectives.
SG 1 Preparation for quantitative management is conducted.
SP 1.1 Establish and maintain the project’s quality and process performance objectives. SP 1.2 Using statistical and other quantitative techniques, compose a defined process that enables the project to achieve its quality and process performance objectives . SP 1.3 Select subprocesses and attributes critical to evaluating performance and that help to achieve the project’s quality and process performance objectives. SP 1.4 Select measures and analytic techniques to be used in quantitative management.
SG 2 The project is quantitatively managed.
SP 2.1 Monitor the performance of selected subprocesses using statistical and other quantitative techniques. SP 2.2 Manage the project using statistical and other quantitative techniques to determine whether or not the project’s objectives for quality and process performance are being satisfied. SP 2.3 Perform root cause analysis of selected issues to address deficiencies in achieving the project’s quality and process performance objectives.
REQUIREMENTS DEVELOPMENT -- ENGINEERING (ML3)
The purpose of requirements Development (RD) is to elicit, analyze, and establish customer, product, and product component requirements.
SG 1 Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements.
SP 1.1 Elicit stakeholder needs, expectations, constraints and interfaces for all phases of the product lifecycle. SP 1.2 Transform stakeholder needs, expectations, constraints and interfaces into prioritized customer requirements.
SG 2 Customer requirements are refined and elaborated to develop product and product component requirements.
SP 2.1 Establish and maintain product and product component requirements, which are based on the customer requirements. SP 2.2 Allocate the requirements for each product component. SP 2.3 Identify interface requirements.
SG 3 The requirements are analyzed and validated.
SP 3.1 Establish and maintain operational concepts and associated scenarios. SP 3.2 Establish and maintain a definition of required functionality and quality attributes. SP 3.3 Analyze requirements to ensure that they are necessary and sufficient. SP 3.4 Analyze requirements to balance stakeholder needs and constraints. SP 3.4 Validate requirements to ensure the resulting product will perform as intended in the user’s environment.
REQUIREMENTS MANAGEMENT -- PROJECT MANAGEMENT (ML2)
The purpose of Requirements Management (REQM) is to manage requirements of the project’s products and product components and to ensure alignment between those requirements and the project’s plans and work products.
SG 1 Requirements are managed and inconsistencies with plans and work products are identified.
SP 1.1 Develop an understanding with the requirements providers on the meaning of the requirements. SP 1.2 Obtain commitment to requirements from project participants. SP 1.3 Manage changes to requirements as they evolve during the project. SP 1.4 Maintain bidirectional traceability among requirements and work products. SP 1.5 Ensure that project plans and work products remain aligned with the requirements.
RISK MANAGEMENT -- PROJECT MANAGEMENT (ML3)
The purpose of Risk Management (RSKM) is to identify potential problems before they occur so that risk handling activities can be planned and invoked as needed across the life of the product or project to mitigate adverse impacts on achieving objectives.
SG 1 Preparation for risk management is conducted.
SP 1.1 Determine risk sources and categories. SP 1.2 Define parameters used to analyze and categorize risks and to control the risk management effort. SP 1.3 Establish and maintain the strategy to be used for risk management.
SG 2 Risks are identified and analyzed to determine their relative importance.
SP 2.1 Identify and document risks. SP 2.2 Evaluate and categorize each identified risk using defined risk categories and parameters, and determine its relative priority.
SG 3 Risks are handled and mitigated as appropriate to reduce adverse impacts on achieving objectives.
SP 3.1 Develop a risk mitigation plan in accordance with the risk management strategy. SP 3.2 Monitor the status of each risk periodically and implement the risk mitigation plan as appropriate.