CMMI

1. CMMI Capability Maturity Model Integrated

2. CMMI Overview Quality Frameworks

3. Priorities of a Software Company You are president of a software company. What are your priorities or goals for operation? • Operating Efficiency (speed) • Predictability • Repeatability (consistency) • Cost / effort control

4. Obstacles to Achieving Goals What do you think are likely to be major obstacles to a software company's goals? • personnel turn-over • lack of visibility – few measurements or objective way to evaluate progress • project complexity • insufficient skill or knowledge • lack of defined processes

5. How to Improve Ability to Achieve • How can you improve your company's ability to achieve its goals? • hire better developers? • offer more incentives? (pay, ownership, bonuses) • more training? • ...training in what? • use project management software?

6. Claimed Benefits of CMMI • Predictability • progress and completion of project follows plan more closely • Repeatability • can reliably estimate new project complexity based on past performance • Improved Productivity • some organizations report 30% reduction in cost • Better Quality • following a defined method (that includes testing, review, and audit) reduces omissions and missed tasks

7. Process & Quality The SEI premise: “The quality of a system or product is highly influenced by the quality of the process used to develop and maintain it."

8. CMMI Staged Representation - 5 Maturity Levels Level 5 Process performance continually improved through incremental and innovative technological improvements. Optimizing Level 4 Quantitatively Managed Processes are controlled using statistical and other quantitative techniques. Process Maturity Level 3 Defined Processes are well characterized and understood. Processes, standards, procedures, tools, etc. are defined at the organizational level. Proactive. Level 2 Managed Processes are planned, documented, performed, monitored, and controlled at the project level. Often reactive. Level 1 Initial Processes are unpredictable, poorly controlled, reactive.

9. Optimizing Defined Over reliance on experience of good people – when they go, the process Managed goes. “Heroics.” Behaviors at the Five Levels Maturity Level Process Characteristics Behaviors Focus on "fire prevention"; Focus is on continuous quantitative improvement improvement anticipated and desired, and impacts assessed. Greater sense of teamwork and inter- Process is measured and controlled Quantitatively Managed dependencies Reliance on defined process. People understand, support and follow the process. Process is characterized for the organization and is proactive Process is characterized for projects and is often reactive Focus on "fire fighting"; Process is unpredictable, poorly controlled, and reactive Initial effectiveness low – frustration high.

10. Required. Specific for each process area. CMMI Terminology & Structure Maturity Levels (1 - 5) Process Area 1 Process Area 2 Process Area n Required. Common across all process areas. Specific Generic Goals Goals Common Features Commitment Ability Verifying Directing to Perform Implementation to Perform Implementation Specific Generic Required Required Informative Practices Practices Informative Sub practices , typical work products, Sub practices , typical work products, discipline amplifications, generic discipline amplifications, generic practice elaborations, goal and practice elaborations, goal and practice titles, goal and practice notes, practice titles, goal and practice notes, and references and references

11. What does CMMI offer?

12. Key Process Areas • "Process Areas" are general areas • They can be grouped into 4 categories: Process Management Project Management Engineering Support

13. Project Management • What process areas do you think a software company should have for "Project Management"?

14. Project Management PP Project Planning PMC Project Monitoring and Control SAM Supplier Agreement Management (Not Applicable) IPM Integrated Project Management RSKM Risk Management QPM Quantitative Project Management

15. Engineering Discipline • What process areas do you think a software company should have for "Engineering"?

16. Engineering REQM Requirements Management RD Requirements Development TS Technical Solution PI Product Integration VER Verification VAL Validation

17. Support (Supporting Processes) • What process areas do you think a software company should have for "Support"?

18. Support CM Configuration Management PPQA Process and Product Quality Assurance MA Measurement and Analysis DAR Decision Analysis and Resolution CAR Causal Analysis and Resolution

19. Process Management • What process areas do you think a software company should have for "Process Management"?

20. Process Management OPD Organizational Process Definition OPF Organizational Process Focus OT Organizational Training OPP Organizational Process Performance

21. How to Evaluate a Process Area • How do you know if your organization's "process" incorporates a process area? • Ask project staff? Answer may be designed to please.

22. Evaluating Process Area • How do you know if your organization's "process" incorporates a process area? 1. Must meet "specific goals" of the process area. and 2. Incorporate "specific practices" for the process area.

23. Example: Project Planning SG 1 Establish Estimates Practices for this goal: • Estimate the Scope of the Project • Estimate Work Product & Task Attributes • Define Project Lifecycle • Estimate Effort & Cost

24. CMMI Level 2 Managed

25. Level 2 : Managed At maturity level 2, requirements, processes, work products, and services are managed. The status of the work products and the delivery of services are visible to management at defined points (for example, at major milestones and at the completion of major tasks).

26. Level 2 Benefits The process discipline reflected by maturity level 2 helps to ensure that practices are retained during times of stress. When these practices are in place, projects are performed and managed according to their plans. This doesn't mean the project will finish according to plan.

27. Level 2 - Key Process Areas CMMI suggests ("requires") our company implement practices in these process areas: • CM - Configuration Management • MA - Measurement and Analysis • PMC - Project Monitoring and Control • PP - Project Planning • PPQA - Process and Product Quality Assurance • REQM - Requirements Management • SAM - Supplier Agreement Management (Not Applicable)

28. Generic Goals and Practices • Each process area has specific goals and practices. • There are also generic goals and practices that apply to all process areas.

29. Generic Goals GG 1 • GG 1 Achieve Specific Goals • GP 1.1 Perform Specific Practices Meaning: Know just write it down... do it!

30. Generic Goals GG2 GG 2Institutionalize a Managed Process • GP 2.1 Establish an Organizational Policy • GP 2.2 Plan the Process • GP 2.3 Provide Resources • GP 2.4 Assign Responsibility • GP 2.5 Train People • GP 2.6 Manage Configurations • GP 2.7 Identify and Involve Relevant Stakeholders • GP 2.8 Monitor and Control the Process • GP 2.9 Objectively Evaluate Adherence • GP 2.10 Review Status with Higher Level Mgmt

31. GG2 - connecting the goals GP 2.1 Establish an Organizational Policy GP 2.2 Plan the Process GP 2.4 Assign Responsibility GP 2.3 Provide Resources GP 2.5 Train People GP 2.6 Manage Configurations GP 2.7 Identify and Involve Relevant Stakeholders GP 2.8 Monitor and Control the Process GP 2.9 Objectively Evaluate Adherence GP 2.10 Review Status with Higher Level Mgmt It needs commitment (from management) to work Plan first Assign the jobs to someone You need resources to do your job You need know-how to do it Who cares about this? Get their input ... is the job really being done? ... is it really working?

32. Specific Goals and Practices • PP - Project Planning • CM - Configuration Management • MA - Measurement and Analysis • PMC - Project Monitoring and Control • PPQA - Process and Product Quality Assurance • REQM - Requirements Management • SAM - Supplier Agreement Management

33. PP - Project Planning Specific Goals and Practices: SG 1 Establish Estimates • Estimate the Scope of the Project • Estimate Work Product & Task Attributes • Define Project Lifecycle • Estimate Effort & Cost

34. PP - Project Planning (continued) SG 2 Develop a Project Plan • Establish the Budget and Schedule • Identify Project Risks • Plan for Data Management • Plan for Project Resources • Plan for Needed Knowledge and Skills • Plan Stakeholder Involvement • Establish the Project Plan

35. Project Planning - subpractices SP 2.1 Establish the Budget and Schedule • identify major milestones • identify task dependencies • identify constraints • define a budget and schedule Work Products Schedule Schedule Dependencies Budget

36. PP - Project Planning (continued) SG 3 Obtain Commitment to the Plan • Review Plans • Reconcile Work and Resource Levels • Obtain Plan Commitment

37. Activity 4 • What Configuration Management practices did you really use? • Describe the actual activity/practice use used. • If none, they write "none".

38. CM - Configuration Management SG 1 Establish Baselines • Identify Configuration Items • Establish a Configuration Management System • Create or Release Baselines SG 2 Track and Control Changes • Track Change Requests • Control Configuration Items SG 3 Establish Integrity • Establish Configuration Management Records • Perform Configuration Audits

39. MA - Measurement & Analysis SG 1 Align Measurement and Analysis Activities • Establish Measurement Objectives • Specify Measures • Specify Data Collection and Storage Procedures • Specify Analysis Procedures SG 2 Provide Measurement Results • Collect Measurement Data • Analyze Measurement Data • Store Data and Results • Communicate Results

40. PMC - Project Monitoring and Control SG 1 Monitor Project Against Plan • Monitor Project Planning Parameters • Monitor Commitments • Monitor Project Risks • Monitor Data Management • Monitor Stakeholder Involvement • Conduct Progress Reviews • Conduct Milestone Reviews SG 2 Manage Corrective Action to Closure • Analyze Issues • Take Corrective Action • Manage Corrective Action

41. Activity 5 • What Project Monitoring & Control practices did you really use? • Describe the actual activity/practice use used. • If none, they write "none".

42. PPQA - Process & Product QA SG 1 Objectively Evaluate Processes and Work Products • Objectively Evaluate Processes • Objectively Evaluate Work Products and Services SG 2 Provide Objective Insight • Communicate and Ensure Resolution of Noncompliance Issues • Establish Records

43. PPQA subpractices SP 1.2 Objectively Evaluate Work Products & Services • clearly state the criteria for evaluating work products • use the stated criteria for evaluation • evaluate products before they are delivered to customer • evaluate work products at milestones • record results of evaluation • identify lessons learned that could improve processes in the future

44. Activity 6 • What Product and Process QA practices did you really use? • Describe the actual activity/practice use used. • If none, they write "none".

45. REQM - Requirements Management SG 1 Manage Requirements • Obtain an Understanding of Requirements • Obtain Commitment to Requirements • Manage Requirements Changes • Maintain Bidirectional Traceability of Requirements • Identify Inconsistencies Between Project Work and Requirements

46. SAM - Supplier Agreement Management SG 1 Establish Supplier Agreements • Determine Acquisition Type • Select Suppliers • Establish Supplier Agreements SG 2 Satisfy Supplier Agreements • Execute the Supplier Agreement • Monitor Selected Supplier Processes • Evaluate Selected Supplier Work Products • Accept the Acquired Product • Transition Products

47. Beyond Level 2... Process Areas from Level 3

48. Validation - "do the right thing" The purpose of Validation is to show that a product fulfills its intended use in the intended environment. SG 1 Prepare for Validation • Select Products for Validation • Establish the Validation Environment • Establish Validation Procedures and Criteria SG 2 Validate Product or Components • Perform Validation • Analyze Validation Result

49. Verification - "do the thing right" The purpose of Verification is to ensure that work products meet their specified requirements. SG 1 Prepare for Verification • ... see documentation SG 2 Perform Peer Reviews • SP 2.1 Prepare for Peer Reviews • SP 2.2 Conduct Peer Reviews • SP 2.3 Analyze Peer Review Data SG 3 Verify Selected Work Products • ... see documentation

50. Process Assets Artifacts that describe, implement, and improve processes. Includes: • Organization’s set of standard processes, including the process architectures and process elements • Descriptions of approved life-cycle models • Guidelines and criteria for tailoring a standard process • Organization’s measurement repository • Organization’s process asset library