200209–CSSA0001 – 16/25/2015 10:30 AM CSSA Cepeda Systems & Software Analysis, Inc. SCAMPI.

Slides:



Advertisements
Similar presentations
Chapter 4 Scope Management
Advertisements

Service Agency Accreditation Recognizing Quality Educational Service Agencies Mike Bugenski
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
Sarbanes Oxley & CMMI Mazars / Lamri
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright 2003, ProcessVelocity, LLP. CMM and Capability Maturity Model are registered in the U.S. Patent and Trademark Office. CMMI and SCAMPI are service.
Griffith UNIVERSITY Software Quality Institute An Overview of Appraisal Assistant A tool to support process assessment / appraisal Software Quality Institute.
Appraisal Requirements for CMMI
SM CMM Integration, SCAMPI, SCAMPI Lead Assessor, SCAMPI Lead Appraiser, and SEI are service marks of Carnegie Mellon University.  CMM and CMMI are registered.
Stepan Potiyenko ISS Sr.SW Developer.
Standard CMMI Appraisal Method for Process Improvement (SCAMPI)
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
© 2001 by Carnegie Mellon University C S a r n e g i e M e l l o n o f t w a r e E n g i n e e r i n g I n s t i t u t e CMMI SM CMMI SM Appraisal Overview.
Fundamentals of Information Systems, Second Edition
200209–CSSA0001 – 16/27/ :25 PM CSSA Cepeda Systems & Software Analysis, Inc. GENERIC.
IS 2620: Developing Secure Systems Jan 13, 2009 Secure Software Development Models/Methods Week 2: Lecture 1.
CMMI December 3rd 2014.
Release & Deployment ITIL Version 3
What is Business Analysis Planning & Monitoring?
Process: A Generic View
Integrated Capability Maturity Model (CMMI)
Chapter 10.
PMP® Exam Preparation Course
COMPANY CONFIDENTIAL Page 1 Final Findings Briefing Client ABC Ltd CMMI (SW) – Ver 1.2 Staged Representation Conducted by: QAI India SM - CMMI is a service.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Chapter 2 Process: A Generic View
Software Engineering Lecture # 17
Copyright 2003 Northrop Grumman Corporation 0 To PIID or Not to PIID: Lessons Learned in SCAMPI Evidence Preparation To PIID or Not to PIID: Lessons Learned.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Process Assessment Method
Managing CMMI® as a Project
Georgia Institute of Technology CS 4320 Fall 2003.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
“CBA IPI® vs. SCAMPISM Appraisal Methods: Key Differences”
Everything You Ever Wanted to Know About CMMI in 30 Minutes or LESS CCS TECHNICAL SERVICES (484) CCS TECHNICAL SERVICES (484) William.
Develop Project Charter
1 Agenda for measurement r1. CMMI r2. Other thrusts.
Gary Natwick & Geoff Draper November 2003 Product-Based Approach for CMMI ® Appraisals CMMI ® Technology Conference & User Group 2003 assured.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CMMI November 25 th Copyright © 2015 Accenture All rights reserved. The aim of the presentation is to introduce Capability Maturity Model Integrated.
Minimizing SCAMPI Costs via Quantitative Methods Ron Ulrich, Northrop Grumman Rick Hefner, Northrop Grumman CMMI.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Software Engineering (CSI 321) Software Process: A Generic View 1.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
The Project Management Process Groups
CMMI for Services, Version 1.3 Speaker: Business Excellence Date:
Project Management PTM721S
Transitioning from CBA-IPI to SCAMPI Appraisals: Lessons Learned
An Effective and Efficient Approach to ARC C Appraisals
Fundamentals of Information Systems, Sixth Edition
Identify the Risk of Not Doing BA
CMMI Q & A.
TechStambha PMP Certification Training
Chapter 3 Managing the Information Systems Project
SEI SCAMPI B/C Project: A Partner’s Perspective
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Enterprise Improvement LEAN Initiative Presentation
Sandra Cepeda, 5:00 - 5:30 Cepeda Systems & Software Analysis, Inc.
Use of Tailored PIIs November 17, 2003
CIS12-3 IT Project Management
Objective Evidence For Appraisals
Presented to National Defense Industrial Association
IS 2620: Developing Secure Systems
Class “B” Appraisal Implemented Lessons Learned
Presentation transcript:

–CSSA0001 – 16/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. SCAMPI A FOR ASI

200209–CSSA0001 – 26/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. ARC V1.1  The Appraisal Requirements for CMMI (ARC) V1.1 Defines the Requirements Considered Essential to Appraisal Methods Intended for Use With CMMI Models  Appraisal Principles  Start With an Appraisal Reference Model  Use a Formalized Appraisal Process  Involve Senior Management As the Appraisal Sponsor  Focus the Appraisal on the Sponsor’s Business Objectives  Observe Strict Confidentiality and Non-attribution of Data  Approach the Appraisal Collaboratively  Focus on Follow-on Activities and Decision-making Based Upon the Appraisal Results  The Appraisal Requirements for CMMI (ARC) V1.1 Defines the Requirements Considered Essential to Appraisal Methods Intended for Use With CMMI Models  Appraisal Principles  Start With an Appraisal Reference Model  Use a Formalized Appraisal Process  Involve Senior Management As the Appraisal Sponsor  Focus the Appraisal on the Sponsor’s Business Objectives  Observe Strict Confidentiality and Non-attribution of Data  Approach the Appraisal Collaboratively  Focus on Follow-on Activities and Decision-making Based Upon the Appraisal Results

200209–CSSA0001 – 36/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. ARC APPRAISAL METHOD CLASSES CharacteristicsClass AClass BClass C Amount of Objective Evidence Gathered (Relative) HighMediumLow Ratings GeneratedYesNo Resources Needs (Relative) HighMediumLow Team Size (Relative)LargeMediumSmall Appraisal Team Leader Requirements Lead Appraiser Lead Appraiser or Person Trained & Experienced Person Trained & Experienced

200209–CSSA0001 – 46/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. WHAT IS SCAMPI?  The Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Is a Class A Appraisal Method That Provides Benchmark Quality Ratings Relative to CMMI Models  SCAMPI Objectives  Gain Insight Into an Organization’s Engineering Capability by Identifying the Strengths and Weaknesses of Its Current Processes  Relate These Strengths and Weaknesses to the CMMI Model  Prioritize Improvement Plans  Focus on Improvements (Correct Weaknesses That Generate Risks) That Are Most Beneficial to the Organization Given Its Current Level of Organizational Maturity or Process Capabilities  Derive Capability Level Ratings, As Well As a Maturity Level Rating  Identify Development/acquisition Risks Relative to Capability/maturity Determinations  The Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Is a Class A Appraisal Method That Provides Benchmark Quality Ratings Relative to CMMI Models  SCAMPI Objectives  Gain Insight Into an Organization’s Engineering Capability by Identifying the Strengths and Weaknesses of Its Current Processes  Relate These Strengths and Weaknesses to the CMMI Model  Prioritize Improvement Plans  Focus on Improvements (Correct Weaknesses That Generate Risks) That Are Most Beneficial to the Organization Given Its Current Level of Organizational Maturity or Process Capabilities  Derive Capability Level Ratings, As Well As a Maturity Level Rating  Identify Development/acquisition Risks Relative to Capability/maturity Determinations

200209–CSSA0001 – 56/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. SCAMPI V1.1 HIGHLIGHTS  Single, Integrated Appraisal Method to Support  Internal Process Improvement  Supplier Selection: High-value Discriminator  Process Monitoring: After Contract Award (Incentive/Award Fees)  Detailed Method Definition - SCAMPI Method Definition Document (MDD)  Emphasis Moves From “Discovery” to “Verification”  Four Data Gathering Mechanisms (Objective Evidence Sources)  Instruments, Presentations, Documents, Interviews  Focused Investigation  Application of Efficient Techniques for Collection and Management of Appraisal Data  Single, Integrated Appraisal Method to Support  Internal Process Improvement  Supplier Selection: High-value Discriminator  Process Monitoring: After Contract Award (Incentive/Award Fees)  Detailed Method Definition - SCAMPI Method Definition Document (MDD)  Emphasis Moves From “Discovery” to “Verification”  Four Data Gathering Mechanisms (Objective Evidence Sources)  Instruments, Presentations, Documents, Interviews  Focused Investigation  Application of Efficient Techniques for Collection and Management of Appraisal Data

200209–CSSA0001 – 66/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PRACTICE IMPLEMENTATION INDICATORS  Practice Implementation Indicators (PIIs) - the “Footprints” That Are the Necessary or Incidental Consequence of Practice Implementation  Include Artifacts As Well As Information Gathered From Interviews With Managers and Practitioners  PII-based Process Appraisal Uses PIIs As the Focus for Verification of Practice Implementation  This Is in Contrast to an Observation-based Approach (CBA IPI) That Relies on the Crafting of Observations That Pertain to Model Implementation Strengths or Weaknesses  Practice Implementation Indicators (PIIs) - the “Footprints” That Are the Necessary or Incidental Consequence of Practice Implementation  Include Artifacts As Well As Information Gathered From Interviews With Managers and Practitioners  PII-based Process Appraisal Uses PIIs As the Focus for Verification of Practice Implementation  This Is in Contrast to an Observation-based Approach (CBA IPI) That Relies on the Crafting of Observations That Pertain to Model Implementation Strengths or Weaknesses

200209–CSSA0001 – 76/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PRACTICE IMPLEMENTATION INDICATOR TYPES  Direct Artifacts  Tangible Outputs Resulting Directly From Implementation of a Practice; CMMI’s “Typical Work Products”  e.g., Project Plan, Project Performance Measures  Indirect Artifacts  Artifacts That Are a Side-effect or Indicative of Performing a Practice  e.g., Meeting Minutes, Reviews, Logs, Reports  Affirmations  Oral or Written Statements Confirming or Supporting Implementation of the Practice  e.g., Interviews, Questionnaires  Direct Artifacts  Tangible Outputs Resulting Directly From Implementation of a Practice; CMMI’s “Typical Work Products”  e.g., Project Plan, Project Performance Measures  Indirect Artifacts  Artifacts That Are a Side-effect or Indicative of Performing a Practice  e.g., Meeting Minutes, Reviews, Logs, Reports  Affirmations  Oral or Written Statements Confirming or Supporting Implementation of the Practice  e.g., Interviews, Questionnaires

200209–CSSA0001 – 86/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. EXAMPLE – INDICATORS OF PRACTICE IMPLEMENTATION Establish A Top-level Work Breakdown Structure (WBS) To Estimate the Scope of the Project PP SP1.1-1: Direct Artifacts  Top-level WBS  Task Descriptions  Work Package Descriptions Indirect Artifacts  Meeting Minutes  Team Charter  WBS Development Notes Affirmations  “I Worked on the WBS Team”  “We Used the WBS”

200209–CSSA0001 – 96/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. FI PI FI LI Char. FI PI FI LI Char. SCAMPI AGGREGATION AND RATING Organizational Unit Level Organizational Unit Level (Optional) Corroboration Coverage Must Have Direct Artifacts, Combined With Either Indirect Artifact or Affirmation Must Have Sufficient Objective Evidence for Implementation of Each Practice, for Each Instance Must Have Face-to-Face (F2F) Affirmations (Avoid “Paper-only Appraisals”) (Practices) Inst. I1 I2 I3 I4 Direct Indicator(s) xx Indirect Indicator(s) xx Affirmation Indicator(s) xx … … Strength(s) Weakness(es) Obs. FI PI FI LI Char. LI Preliminary Findings Weakness(es) Strength(s) Char. LI Final Findings Goals Maturity Levels Capability Levels Process Areas

200209–CSSA0001 – 106/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PRACTICE IMPLEMENTATION INDICATOR DESCRIPTIONS  A PIID Is a Structure or Schema Defined to Provide a Repository for the Practice Implementation Indicator Information.  PIDDs Have Multiple Uses:  During Model Implementation – Provide a Mechanism by Which the Implementation of a Model Practice Can Be Described.  Appraisal – Provide a Mechanism to Verify Practice Implementation Effectively and Efficiently.  After Model Implementation – Provide Vehicle for Training New Personnel, for Internal Monitoring of Practice Implementation, Etc.  PIDDs Are Used to Capture Data for Both Specific Practices and Generic Practices  A PIID Is a Structure or Schema Defined to Provide a Repository for the Practice Implementation Indicator Information.  PIDDs Have Multiple Uses:  During Model Implementation – Provide a Mechanism by Which the Implementation of a Model Practice Can Be Described.  Appraisal – Provide a Mechanism to Verify Practice Implementation Effectively and Efficiently.  After Model Implementation – Provide Vehicle for Training New Personnel, for Internal Monitoring of Practice Implementation, Etc.  PIDDs Are Used to Capture Data for Both Specific Practices and Generic Practices

200209–CSSA0001 – 116/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PROCESS AREA PIDDs (SPECIFIC PRACTICES)

200209–CSSA0001 – 126/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. GENERIC PRACTICES PIIDs – OVERALL GUIDANCE

200209–CSSA0001 – 136/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. GENERIC PRACTICES PIDDs – APPLIED TO A PROCESS AREA

200209–CSSA0001 – 146/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PREPARING FOR THE APPRAISAL  Prior to the appraisal, the organization populates the PIDDs  PIIDs Contain All the Specific and Generic Practices for the Process Areas in the Scope of the Appraisal  The Organization Answers These Questions For Each Practice In The Process Areas Being Appraised:  Do We Do This?  What Artifact Can We Provide As Evidence?  Where Can the Artifact Be Found?  Prior to the appraisal, the organization populates the PIDDs  PIIDs Contain All the Specific and Generic Practices for the Process Areas in the Scope of the Appraisal  The Organization Answers These Questions For Each Practice In The Process Areas Being Appraised:  Do We Do This?  What Artifact Can We Provide As Evidence?  Where Can the Artifact Be Found?

200209–CSSA0001 – 156/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. SCAMPI PROCESS FLOW – PLAN & PREPARE Plan for Appraisal Prepare Appraisal Team & Participants Obtain/Analyze Initial Objective Evidence (OE) Prepare to Collect OE 1 Questionnaires Optional Scope, Appraisal Plan Trained team Participants oriented 1 Questionnaires/Mapping/Documents PII (mapping) Database Readiness Review and Data Collection Plan

200209–CSSA0001 – 166/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. Verify OE Direct & Indirect Artifacts, Affirmations, Strengths, and Weaknesses SCAMPI PROCESS FLOW – CONDUCT APPRAISAL Examine OE Questionnaire results, PII Database, Documents, Interviews Validate Practice Implementation Gaps Document OE Characterize Implementation of Practices Generate Assessment Results Final Findings, Ratings Preliminary Findings and Findings Feedback Instantiation-level & Organizational Unit-level Characterizations Recorded/Updated Appraisal Data (e.g., tagged notes, PII Database,Gaps) Note: Shading indicates iterative process.

200209–CSSA0001 – 176/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. SCAMPI PROCESS FLOW – REPORT RESULTS Deliver Appraisal Results Findings Presentation and Final Report * Package & Archive Appraisal Results Lessons Learned, Appraisal Record (sponsor), Appraisal Report/Feedback (SEI) * Final report is optional

200209–CSSA0001 – 186/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PROPOSED PLAN FOR ASI  SCAMPI A for Requirements Management, Project Planning, Measurement & Analysis, Organizational Process Focus, and Risk Management (?) for Pilot Projects  Team Training/Readiness Review: 04/27-04/30  Appraisal: 05/24-05/27  Commitment  Work with Sandra to Prepare for Appraisal (February-April)  Provide 1 person for the appraisal team (Needs to Have Taken Intro to CMMI Class)  SCAMPI A for Requirements Management, Project Planning, Measurement & Analysis, Organizational Process Focus, and Risk Management (?) for Pilot Projects  Team Training/Readiness Review: 04/27-04/30  Appraisal: 05/24-05/27  Commitment  Work with Sandra to Prepare for Appraisal (February-April)  Provide 1 person for the appraisal team (Needs to Have Taken Intro to CMMI Class)

–CSSA0001 – 196/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PATH FORWARD

200209–CSSA0001 – 206/25/ :30 AM CSSA Cepeda Systems & Software Analysis, Inc. PATH FORWARD  Baseline Process Descriptions  Execute Processes in Pilot Projects (objective evidence should be generated)  Collect Metrics  Gather lessons learned and process improvements  Implement process improvements  Continue Weekly Telecons and Monthly Meetings  Prepare for Appraisal  Suz will be Lead Process Improvement Consultant  Sandra will be Lead Appraiser  Baseline Process Descriptions  Execute Processes in Pilot Projects (objective evidence should be generated)  Collect Metrics  Gather lessons learned and process improvements  Implement process improvements  Continue Weekly Telecons and Monthly Meetings  Prepare for Appraisal  Suz will be Lead Process Improvement Consultant  Sandra will be Lead Appraiser