WEBINAR: Solving the Process Maturity Challenge Presented by David Consulting Group (DCG) and MKS, Inc.
Establishing Effective Measurements in Support of the SEI CMMI 1
Terms • CMMI Capability Maturity Model Integration Set of guidelines to achieve process maturity • Level 15 Numerical designation of process maturity per the CMMI 2
Terms Maturity Levels 5 Optimizing 4 Managed 3 Defined 2 Repeatable 1 Initial 3
Presentation Objective • To present recommendations for establishing an effective measurement program compliant with CMMI Level 3 Process Areas • Topics include: • Steps to developing an effective and practical measurement program • An overview of the CMMI measurement requirements for Level 2 and 3 • A recommended set of metrics which comply with the model requirements and promote process improvement 4
Establishing a Measurement Program Steps to developing an effective and practical measurement program • Obtain the sponsorship and support of senior management • Create an organizational metrics “guru” role – e.g CMO (Chief Measurement Officer) • Agree on criteria for measurement selection (see following slides) and the business goals to support 5
Establishing a Measurement Program • Think through and address implementation requirements – e.g., tools, training, data collection and reporting processes, etc. • Define and document measurements in a Measurement Plan – current and new 6
Criteria for Selecting Measurements • Measurements should support business goals and needs. For this presentation, assuming the following business needs: • Meeting cost, schedule and technical commitments • Managing and improving software quality • Managing and improving software productivity • Managing and improving process effectiveness • The measurements must satisfy CMMI Level 3 practices • The measurements must be relatively easy to implement and be kept to an effective minimum number 7
Criteria for Selecting Measurements per Watts Humphrey* • The measures must be robust – i.e., precise and relatively unaffected by minor changes in tools, methods, or product characteristics. • The measures should suggest a norm – i.e., the meaning of a high or low value should be obvious. • The measures should relate to specific product or process properties – i.e., errors, size, or resources expended. • The measures should suggest an improvement strategy – i.e., should indicate what needs to be improved. * from Managing the Software Process 8
Criteria for Selecting Measurements per Watts Humphrey* • The measures should be a natural result of the process. – The effort to collect measurements should be kept to a minimum. • The measures should be simple. – They should not be difficult to explain. • The measures should be both predictable and trackable – i.e., measures that provide planned versus actual comparisons. * from Managing the Software Process 9
CMMI measurement requirements CMMI measurement requirements for the Level 2 and 3 Process Areas 10
Level 2 Process Area Measurement and Analysis Measurement and Analysis describes the need to develop and sustain a measurement capability that is used to support management information needs. 11
CMMI Measurement Requirements • CMMI defines measurements requirements for: Level 2 – Measurements and Analysis – Project Planning • Estimating project attributes – Project Monitoring and Control • Monitoring project performance Level 3 – Integrated Project Management – Requirements Development – Product Integration – Verification – Validation 12
CMMI Measurement Requirements • Measurements are also needed to support CMMI activities: • For project monitoring and control, estimates and actuals for: • Schedule • Size of software work products • Effort • Cost • Critical Computer Resources (disk, memory, etc) • PPQA audit results • Numbers and status of change requests and problem reports against configuration items • Historical process data from across the organization • Defect data from peer reviews and testing activities • Data on the conduct of peer reviews 13
Levels of Data Collection and Reporting Organizational Measurements Project Project Project Project Org. A B C D Tasks TASKS TASKS TASKS TASKS TASKS Planning Planning Planning Planning EPG Tracking Tracking Tracking Tracking PPQA CM CM CM CM Process Def. Reqs. Reqs. Reqs. Reqs. Audits Design Design Design Design Training Code Code Code Code …….. …….. …….. …….. …….. 14
CMMI Compliant Metrics A recommended set of compliant metrics which promote process improvement 15
Recommended CMMI Measures Measures CMMI PAs Business Need Justification Level of Supported Tracking Cost – planned vs. actual PP SP 2.1 Meeting cost To manage cost Project PMC SP 1.1 commitments commitments; to identify PMC SP 1.6 & address cost issues as PMC SP 2.2 early as possible IPM SP 1.2 OPD SP 1.4 MA SP 1.2 MA SP 2.1 Effort – planned vs. PP SP 1.1 Meeting cost To identify and address Project, PP SP 1.2 actual, including: and schedule staffing issues; to support Task PP SP 1.4 commitments current & future planning PP SP 2.1 • Development tasks PMC SP 1.1 • Maintenance PMC SP 1.6 • Project mgmt. tasks PMC SP 1.7 PPQA SP 2.2 • Intergroup tasks OPD SP 1.4 • Quality Assurance OPF SP 1.3 • EPG tasks IPM SP 1.2 IPM SP 1.4 16
Sample Chart Project Level Cost Measurement Example 100% 250 90% 80% 200 70% 60% 150 $K 50% 40% 100 30% 20% 50 10% 0 0% Jan02 Feb02 Mar02 Apr02 May02 Jun02 $K Plan $K Actual % Work Complete Cost ($K) Jan02 Feb02 Mar02 Apr02 May02 Jun02 50 100 150 200 250 275 $K Plan 25 80 120 175 $K Actual 15% 30% 40% 50% % Work Complete 17
Recommended CMMI Measures Measures CMMI PAs Business Need Justification Level of Supported Tracking Schedule – planned vs. PP SP 1.1 Meeting To identify and address Project, Task PP SP 1.2 actual, including: schedule schedule issues PP SP 1.4 commitments PP SP 2.1 (Same as for Effort) PMC SP 1.1 PMC SP 1.6 PMC SP 1.7 PPQA SP 2.2 OPD SP 1.4 OPF SP 1.3 IPM SP 1.2 IPM SP 1.4 Size & Requirements RD SP 2.1 Meeting cost, To identify and address Project RD SP 3.3 (e.g., Function Points) – schedule, and scope issues, e.g., “reqs. PP SP 1.2 estimated vs. current functionality creep”; to support current PP SP 1.4 commitments replanning and future PMC SP 1.1 planning; to support PMC SP 1.6 productivity OPD SP 1.4 IPM SP 1.2 IPM SP 1.4 IPM SP 1.5 18 IPM SP 1.6
Sample Chart Project Level Size Measurement Example 80 70 60 Function Points 50 Allowable Growth Updated 40 Threshold estimate Original or count 30 Size Estimate 20 10 0 Jan02 Feb02 Mar02 Apr02 May02 Jun02 Plan Current Threshold Size (Function Points) Jan02 Feb02 Mar02 Apr02 May02 Jun02 Plan 50 50 50 50 50 50 Current 50 54 54 66 Threshold 62.5 62.5 62.5 62.5 62.5 62.5 19
Recommended CMMI Measures Measures CMMI PAs Business Need Justification Level of Supported Tracking Critical Computer PP SP 2.4 Meeting To manage critical Project Resources – planned vs. PMC SP 1.1 technical hardware requirements actual commitments IPM SP 1.2 IPM SP 1.3 Productivity – planned OPD SP 1.4 Meeting cost To support future Org., Project vs. final IPM SP 1.6 and schedule planning; to analyze commitments process capability PP SP 1.4 PP SP 2.1 PMC SP 1.1 PMC SP 1.6 20
Recommended CMMI Measures Measures CMMI PAs Business Need Justification Level of Supported Tracking Defects, Peer Review, VER SP 2.1 Meeting and To manage, assess and Org., Project, and Test Data VER SP 2.3 improving improve product quality Task product quality VER SP 3.2 needs PP SP 1.2 OPD SP 1.4 Change Requests & CM SP 2.1 Managing To track the backlog of Org., Project Problem Reports quality software problems in delivered programs and the plan to fix them 21
Recommended CMMI Measures Measures CMMI PAs Business Need Justification Level of Supported Tracking Training – planned vs. OT SP 2.2 Managing To plan and track training Org., Project actual training to ensure business needs are met; to manage training cost Training Effectiveness Managing To identify and improve Course OT SP 2.3 training aspects of training courses effectiveness that need improvement PPQA Audit results Managing To ensure processes are Org., Project, PPQA SP 2.2 (audits and % of non process compliant to documented Procedure compliance findings) compliance procedures and standards and products 22
Peer Review Measures Collected • Program, function, and work product identifiers • Type and phase of review or test, e.g., design inspection or unit test • Who attended and how much time was spent preparing (reviews) • How long the review meeting lasted (reviews) • Size of the work product, e.g., pages of design • Total defects detected (by severity) • Time spent fixing defects (rework) 23
Recommend
More recommend
