Project Planning (PP) - CMMI-Dev V1.3 Training

CMMI Version 1.3 Model Upgrade Training November 2010

Summary of Changes in PP

Made no substantive changes to specific goals or specific practices Revised the definitions of the following terms in the glossary: project and project startup

Deleted the term “program” from the glossary

Added information on how PP applies to product lines and Agile environments in the introductory notes

Removed the material that addressed IPPD

Added subpractices to specific practices 2.3 and 2.4

Modified the informative material so that the development of WBS can be based on other considerations in addition to the product or product architecture

Informative Material Changes

₁

Introductory Notes

• Deleted the statement “planning begins with requirements that define the product and project” so that the discussion of planning would be more broadly applicable to all constellations

• Added guidance that the project plan may be a stand-alone document or be distributed across multiple documents

• Provided guidance for product lines on the benefits of using this process area for creating and maintaining core assets, developing products to be built using core assets, and orchestrating the overall product line effort

• Added information about how Project Planning works with Agile methodologies

CMMI Version 1.3 Model Upgrade Training November 2010

Informative Material Changes

₂

SG 1 Establish Estimates

• Revised the notes by deleting the long list of factors to consider when estimating project planning parameters to instead only refer to requirements associated with the project, its stakeholders, or that impact the project

SP 1.1 Estimate the Scope of the Project

• Noted that the WBS can be structured according to products, work products, and tasks

• In subpractice 1, broadened the concept of WBS development to describing the project work, and removed notes that focused such activity on the product architecture, product, and product components

Informative Material Changes

₃

SP 1.2 Establish Estimates of Work Product and Tasks Attributes

• Added notes on service level and availability as attributes for estimating • Restructured the example box into two example boxes, one for attributes used

to estimate, and one for work products for which size estimates are made • Added several examples of attributes to estimate and moved the example box

of work products for which size estimates are made to subpractice 3

• In subpractice 1, added quality attributes expected in the final product as part of the technical approach for the project

• In subpractice 2, deleted the example box of current methods to determine attributes due to the mismatch between the header and examples

CMMI Version 1.3 Model Upgrade Training November 2010

Informative Material Changes

₄

SP 1.3 Define Project Lifecycle Phases

• Added guidance about the definition of lifecycle phases to support logical decision points at which the appropriateness of continued reliance on the project plan and strategy is determined

• Added that explicit phases for ‘project start-up’ and ‘project close-out’ may be included in the project lifecycle

Informative Material Changes

₅

SP 2.1 Establish the Budget and Schedule

• In subpractice 1, changed the description of milestones to be more complete Milestones are pre-planned events or points in time at which a thorough review of status is conducted to understand how well stakeholder requirements are being met. (If the project includes a developmental milestone, then the review is conducted to ensure that the assumptions and requirements associated with that milestone are being met.) Milestones can be associated with the overall project or a particular service type or instance. • In subpractice 4, added customer priorities, marketable features, and end-user

value as examples of tools and inputs that can help determine optimal ordering of activities

• In subpractice 6, as part of a discussion on corrective action criteria, indicated that the project plan defines when the criteria are applied and by whom

SP 2.2 Identify Project Risks

• In subpractice 1 tools example box, changed “performance models” to “process, project, and product performance models” to be more inclusive

CMMI Version 1.3 Model Upgrade Training November 2010

Informative Material Changes

₆

SP 2.3 Plan Data Management

• Added two subpractices

4. Determine the requirements for providing access to and distribution of data to relevant stakeholders.

5. Decide which project data and plans require version control or other levels of configuration control and establish mechanisms to ensure project data are controlled.

SP 2.4 Plan the Project’s Resources

• Added status reports to the example work products • Added two subpractices and associated notes

Informative Material Changes

₇

SP 2.5 Plan Needed Knowledge and Skills

• Added training plans to the example work products

SP 2.7 Establish the Project Plan

• Added guidance on including lifecycle considerations that may be beyond the life of the project (e.g., transition to operations)

SP 3.2 Reconcile Work and Resource Levels

• Modified guidance on how reconciliation is typically accomplished to replace “lowering” with “modifying” because requirements are not always lowered

CMMI Version 1.3 Model Upgrade Training November 2010

Additional Unique Changes in Other Models

₁

CMMI-ACQ

Made changes to the informative material

SP 1.1 Establish the Acquisition Strategy

• Added consideration of modern engineering concepts (quality attributes, product line considerations) as part of establishing the acquisition strategy SP 1.3 Establish Estimates of Work Product and Task Attributes

• Added notes in subpractice 1 that “the technical approach is often developed as part of and included in the acquisition strategy”

SP 2.1 Establish the Budget and Schedule

• Deleted the subpractice 6 notes paragraph that described the basis for corrective action criteria

SP 2.6 Plan Stakeholder Involvement

• Added notes about working with suppliers that use an Agile method SP 2.7 Plan Transition to Operations and Support

• Added “identification of the maintenance organization” to the example box of items typically included in the plan

Additional Unique Changes in Other Models

₂

CMMI-SVC

Renamed this PA to be “Work Planning”

In document CMMI-Dev V1.3 Training (Page 93-98)