Quest 2015 Webinar Series:
|
|
- Marvin Simon
- 6 years ago
- Views:
Transcription
1 presents the Quest 2015 Webinar Series: You Want to Use SCRUM, You Are Told To Use CMMI-- How They Can Work Together Elegantly WEBINAR SERIES WEBINAR SERIES Featuring Neil Potter of The Process Group
2 You Want to Use Scrum, You are Told to Use CMMI How They can Work Together Elegantly and Both Provide Benefit Neil Potter The Process Group 1!
3 Agenda Summary of Scrum and CMMI Approach Maturity Level 2 and Scrum Comparison How About Other Components of Level 2? Adding Level 3 Management and Engineering Practices Requirements / backlog Release planning, sprint planning and daily standups Sprint composition How About the Other Components of Level 3? Summary 2!
4 Summary of Scrum Team defined steps Potentially Deliver Potentially Deliver 1 day 1 day Product Backlog Release Planning Sprint Planning Analysis Design Code Test Sprint Review Sprint Retrospective Review Backlog Sprint Planning Analysis Design Code Test Sprint Review Sprint Retrospective Review Backlog Sprint Planning Analysis 2-4 week Sprint 2-4 week Sprint 3!
5 Level 5 Optimizing Summary of CMMI (Level 2) v1.3 Focus Process Areas Causal Analysis and Resolution Organizational Performance Management Quality Productivity 4 Quantitatively Managed 3 Defined Allocate time for work Plan work Manage change Know status / quality 2 Managed 1 Initial Organizational Process Performance Quantitative Project Management Integrated Project Management (IPM) Risk Management (RSKM) Decision Analysis and Resolution (DAR) Requirements Development (RD) Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL) Organizational Process Definition (OPD) Organizational Process Focus (OPF) Organizational Training (OT) Requirements Management (REQM) Project Planning (PP) Project Monitoring and Control (PMC) Measurement and Analysis (MA) Configuration Management (CM) Process and Product Quality Assurance (PPQA) Supplier Agreement Management (SAM) Risk Rework 4!
6 Level 5 Optimizing Summary of CMMI (Level 3) v1.3 Focus Process Areas Causal Analysis and Resolution Organizational Performance Management Quality Productivity 4 Quantitatively Managed Use / refine standard org. practices Estimate with data Coordinate projects Manage risk Systematic decisions Elicit requirements Design 3 Defined 2 Managed Defect removal Learn and improve 1 Initial Organizational Process Performance Quantitative Project Management Integrated Project Management (IPM) Risk Management (RSKM) Decision Analysis and Resolution (DAR) Requirements Development (RD) Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL) Organizational Process Definition (OPD) Organizational Process Focus (OPF) Organizational Training (OT) Requirements Management (REQM) Project Planning (PP) Project Monitoring and Control (PMC) Measurement and Analysis (MA) Configuration Management (CM) Process and Product Quality Assurance (PPQA) Supplier Agreement Management (SAM) Risk Rework 5!
7 Visibility Into the Process Level 1 IN OUT Process is an amorphous entity Visibility into the project s process is limited Difficult to establish the status of the project s progress and activities Based Copyright on SEI Intro CMM-SW The Process class! Group. All rights reserved.! 6!
8 Visibility Into the Process Level 2 Chunks of work (increment, sprint, phase) IN OUT Customer requirements and work products are managed Basic project management practices have been established Project management practices allow visibility into the project on defined occasions Management reacts to problems as they occur Based Copyright on SEI Intro CMM-SW The Process class! Group. All rights reserved.! 7!
9 Visibility Into the Process Level 3 IN OUT Tasks in the project s defined process are visible Accurate and rapid status updates are available Management proactively prepares for risks that may arise Based Copyright on SEI Intro CMM-SW The Process class! Group. All rights reserved.! 8!
10 Similarities and Differences No In Scrum? Some requirements Some design Coding Some test Some lessons learned Level 3 coverage - very dependent on how YOU define the phases Approx. 47% coverage of Level 2 Most Requirements Management Most Project Planning Most Project Monitoring/Control Most Measurement Analysis (effort and progress) 9!
11 Approach: Run the Business! Identify problem areas Add practices to address them Focus on high-risk areas of project, not low risk Source does not matter:» WWW» PMI» CMMI» ITIL»... Goal = achieve desired result (not documentation ) 10!
12 Maturity Level 2 and Scrum Comparison 11!
13 Scrum and CMMI Level 2 PMC (progress tracking and corrective action) MA (objectives & measures) CM (baselines & versions) SAM (supplier selection & management) PPQA (process & product check) Backlog Planning REQM REQM REQM ò ò ò Sprint 1 Sprint 2 Sprint 3 REQM PP (plans, estimates) Green = Maturity Level 2 PAs Requirements Design Code Peer Review/Test Integrate Test Release Requirements Design Code Peer Review/Test Integrate Test Release Requirements Design Code Peer Review/Test Integrate Test Release 12!
14 Requirements Management REQM CMMI Practice Scrum Practice SP 1.1 Develop an understanding with the requirements providers on the meaning of the requirements. SP 1.2 Obtain commitment to the requirements from the project participants. SP 1.3 Manage changes to the requirements as they evolve during the project. SP 1.5 Identify inconsistencies between the project plans and work products and the requirements. Review of Product Backlog (requirements) with Product Owner and team. Release Planning and Sprint Planning sessions that seek team member commitment. Add requirements changes to the Product Backlog. Manage changes in the next Sprint Planning meeting. Daily Standup Meeting to identify issues. Release planning and Sprint Planning sessions to address inconsistencies. Sprint Burndown chart that tracks effort remaining. Release Burndown chart that tracks story points that have been completed. This shows how much of the product functionality is left to complete. No traceability in Scrum [SP 1.4 Maintain bidirectional traceability among the requirements and work products] 13!
15 Project Planning PP CMMI Practice Scrum Practice SP 1.1 Establish a top-level work breakdown structure (WBS) to estimate the scope of the project. Backlog). SP 1.2 SP 1.3 SP 1.4 SP 2.1 SP 2.4 SP 2.6 SP 3.2 Establish and maintain estimates of the attributes of the work products and tasks. Define the project life-cycle phases upon which to scope the planning effort. Estimate the project effort and cost for the work products and tasks based on estimation rationale. Establish and maintain the project s budget and schedule. Plan for necessary resources to perform the project. Plan the involvement of identified stakeholders. Reconcile the project plan to reflect available and estimated resources. The standard tasks used in a Scrum process combined with specific project tasks (Sprint Story Points, used to estimate the difficulty (or relative size) of a Story (requirement). The Scrum process. Scrum Ideal Time estimate (similar to billable hours or Full-time Equivalents). Scrum estimates (in Ideal Time). Estimates of what work will be in each release. Release Plan / Sprint Backlog. Project Taskboard. Scrum estimates in Ideal Time Release Plan, Sprint Backlog and assignments. Scrum process roles (including team, Scrum Master, Product Owner). [Note: The stakeholders listed in Scrum might not be the complete list of stakeholders for the project, e.g., customers, other impacted teams.] Sprint Planning meeting. Daily Scrum meeting. 14!
16 Project Monitoring and Control PMC CMMI Practice Scrum Practice SP 1.1 Monitor the actual values of the project planning parameters against the project plan. Sprint Burndown chart that tracks effort remaining. Release Burndown chart that tracks completed story points. This shows how much of the product functionality is left to complete. Project Task Board used to track stories (requirements) that are done, in progress, or ones SP 1.2 Monitor commitments against those identified in the project plan. SP 1.6 Periodically review the project's progress, performance, and issues. SP 2.3 Manage corrective actions to closure. No risk assessment / tracking in Scrum [SP 1.3 Monitor risks against those identified in the project plan] that need verification. Discussions on team commitments at the: Daily Scrum meeting. Sprint Review meeting. Sprint Burndown chart that tracks effort remaining. Release Burndown chart that tracks Story Points that have been completed. This shows how much of the product functionality is left to complete. Daily Scrum meeting. Sprint Review meeting. Retrospectives. Tracking of actions from: Daily Scrum meeting. Sprint Review meeting. [Note: This assumes that teams will track (and not lose) actions.] 15!
17 Measurement and Analysis SP 1.2 Specify measures to address the measurement objectives. SP 1.4 Specify how measurement data will be analyzed and reported. SP 2.1 Obtain specified measurement data. SP 2.2 Analyze and interpret measurement data. SP 2.4 Report results of measurement and analysis activities to all relevant stakeholders. Sprint Burndown chart that tracks effort remaining. Release Burndown chart that tracks story points that have been completed. This shows how much of the product functionality is left to complete. [Note: These two measures could be used to track the progress of declared project objectives, such as On time, and On budget. ] The Scrum process does describe the purpose and use the Sprint and Release Burndown charts. [Note: CMMI expects clearly defined analysis]. Daily Scrum meeting where Sprint and Release Burndown data are collected. Daily Scrum meeting where Sprint and Release Burndown data are analyzed. Daily Scrum meeting where Sprint and Release Burndown charts are reviewed. [Note: Not all interested stakeholders will necessarily be at the Scrum meeting.] 16!
18 How About the Other Components of Level 2? 17!
19 How About the Other Components of Level 2? Configuration Management (CM): CM is not specifically called out in Scrum. However, in an Agile environment it is pretty easy to add a layer of CM to protect your work. Product and Process Quality Assurance (PPQA): Some basic PPQA activities are being done naturally when the Scrum Master checks that the Scrum process is being followed. Scrum does not specifically call out a level of objective process and product check, nor does it state that particular standards or processes should be defined and used. Supplier Agreement Management (SAM): Not included in Scrum. 18!
20 Adding Gates and Governance Establish gates at the end of each, or several, sprints:! Negotiate upfront what will be available at the gates (some design, some code, some tests)." Work with process QA staff early so that there is agreement as to what will be audited and when." Product Backlog Release Planning Sprint Planning Analysis Design Code Test Sprint Review Sprint Retrospective Review Backlog Sprint Planning Analysis Design Code Test Sprint Review Sprint Retrospective Review Backlog Sprint Planning 19!
21 Adding Level 3 Engineering Practices + Sprint composi-on 20!
22 Scrum and CMMI Level 2+3 PMC (progress tracking and corrective action) MA (objectives & measures) CM (baselines & versions) SAM (supplier selection & management) PPQA (process & product check) IPM (planning with assets, data, program-level tracking) RSKM (risk management) OT (planned training program) OPF (process improvement focus) OPD (process asset creation / update) DAR (tradeoffs using criteria) Backlog Planning REQM REQM REQM ò ò ò Sprint 1 Sprint 2 Sprint 3 REQM / RD PP / IPM (plans, estimates) Green = Maturity Level 2 PAs Blue = Maturity Level 3 PAs Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release 21!
23 Requirements / Backlog Priority User Story Estimate (Points) As an account owner, I want to withdraw cash As an account owner, I want to deposit cash As an account owner, I want to deposit check(s) As an account owner, I want to deposit foreign check(s) Typical format: As a <user>, desired action 1-liners can be ambiguous and lead the developer to guess 22!
24 Requirements Example: Using Use Cases for Elicitation [RD SG1], Definition [RD SG2] Name: Withdraw Cash Actor: Account Owner Preconditions: 1. The Account Owner is logged in to the ATM. 2. The Account Owner has at least 1 account with a positive balance. 3. The ATM contains cash. Postconditions: 1. The requested amount of cash has been dispensed. 2. The account balance is reduced by the amount withdrawn plus any fees. 3. The ATM cash balance is reduced by the amount withdrawn. Priority: High [SG = Specific Goal] 23!
25 Requirements (cont d.) Using Use Cases for Elicitation [RD SG1], Definition [RD SG2] Normal flow: Actor Actions 1. Select Withdrawal action. 3. Select desired account. 5. Enter desired amount. 7. Remove cash from dispenser. System Responses 2. Display user s accounts. 4. Ask user to enter amount. 6. If amount is okay, dispense cash and debit account. Alternative Flow: Step 4: display list of common amounts, let user select one Exceptions: Step 6: amount is not a multiple of $20.00 Step 6: amount exceeds $400 Step 6: amount exceeds account balance Step 6: amount exceeds cash available in ATM 24!
26 Requirements Example Analysis [RD SG3] Find ambiguities and errors in the requirements definition. Determining Requirements Priorities Using Models to Clarify Requirements Reviewing and Inspecting Requirements Documents Generating Test Cases Reducing the Expectation Gap Through Prototyping Requirement Test Case ~~~~~~~~~ ~~~~~~~ ~~~~~~~~~ ~~~~~~~ ~~~~~~~~~ ~~~~~~~ ~~~~~~~~~ ~~~~~~~ ~~~~~~~~~ ~~~~~~~ Error Error 25!
27 Scrum and CMMI Level 2+3 PMC (progress tracking and corrective action) MA (objectives & measures) CM (baselines & versions) SAM (supplier selection & management) PPQA (process & product check) IPM (planning with assets, data, program-level tracking) RSKM (risk management) OT (planned training program) OPF (process improvement focus) OPD (process asset creation / update) DAR (tradeoffs using criteria) Backlog Planning REQM REQM REQM ò ò ò Sprint 1 Sprint 2 Sprint 3 REQM / RD PP / IPM (plans, estimates) Green = Maturity Level 2 PAs Blue = Maturity Level 3 PAs Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release 26!
28 Design: Architecture + design notes Peer-reviews to find defects Check interfaces for errors Component test System test Analyze the results: Engineering the System e.g., defect density, pass/escape rate, cause 27!
29 Sprint Composition Allocating Time for Engineering The intent of Scrum is to produce a potentially shippable product every sprint. This could be very small in earlier sprints, and larger is later sprints. Tasks such as, User story analysis and architecture, can be added to the first few sprints 90% Analysis, 10% Code Example % s Final testing and odds-and-ends will likely end up on the backlog and be grouped into a last few sprints. Sprint: % Analysis, 20% Code 70% Analysis, 30% Code 60% Analysis, 40% Code 50% Analysis, 50% Code 28!
30 Adding Level 3 Management Practices Release planning, sprint planning and daily standups 29!
31 Scrum and CMMI Level 2+3 PMC (progress tracking and corrective action) MA (objectives & measures) CM (baselines & versions) SAM (supplier selection & management) PPQA (process & product check) IPM (planning with assets, data, program-level tracking) RSKM (risk management) OT (planned training program) OPF (process improvement focus) OPD (process asset creation / update) DAR (tradeoffs using criteria) Backlog Planning REQM REQM REQM ò ò ò Sprint 1 Sprint 2 Sprint 3 REQM / RD PP / IPM (plans, estimates) Green = Maturity Level 2 PAs Blue = Maturity Level 3 PAs Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release 30!
32 Planning Using Best Practices and Data Use existing assets [IPM SG1] The Organization s Process Assets Organization's Set of Standard Processes Lifecycle Model Descriptions Work Environment Standards Team Rules and Guidelines Tailoring Guidelines Organization's Process Asset Library Organization's Measurement Repository Use Project A s Process Project A Plan Project B s Process Project B Plan Refine Project C s Process Project C Plan [IPM = Integrated Project Management] 31!
33 Planning - Dependencies & Stakeholders Manage [IPM SG1], Dependencies [IPM SG2] Dependencies Deliverable from a Scrum team Program manager or Scrum of Scrums Ship Date" Sprint start Sprint end Deliverable 2" Deliverable 8" Package" & Ship" Deliverable 1" Deliverable 7" Integrate" & Test" Deliverable 3" Deliverable 4" Deliverable 5" Deliverable 6" "Jan "Feb "Mar "Apr "May "Jun" 32!
34 Planning Using Risk Management Risk [RSKM SG2+3] Action items will likely be more numerous and detailed" Status of action items" Risk Item! (Potential Future Problem)! Consequence! Lkli.! Imp.! Pri.! Action- Likelihood! Action-Impact! Who! When! Status! New operating system might not be stable! Unable to ship! 10! 10! 100! Test OS more! Identify 2nd OS! Joe! System communication problems with XYZ! Feature x unavailable! 8! 9! 72! Develop sys interface doc! Add replan milestone! Kim! We may not have the requirements right! Requirements may change late in the cycle! Database S/W might be late! Database expert might leave! Delay next project + no usage of demo! 9! 6! 54! Prototype of UI!! Use Case style requirements! New defects! 7! 7! 49! Prototype top 10 requirements! Revenue delay! Schedule delay! 4! 8! 32! Check with supplier! 2! 10! 20! Make sure Jim is happy! Total! 327! Incremental release! Limit distribution! Limit distribution! Help supplier! Earmark Fred! Lois! Joe! Pete! Jane! Keep track of the top 20% or top 2-3 risks 33!
35 Daily Standups Risk [RSKM SG2+3] + Manage [IPM SG2] Duration: 5-15 mins per day. What: What did you do since the last meeting? What will you do before the next meeting? What is impacting progress (impediments)? What risks (potential problems) do you see? What is state of each task on the Critical Path (longest calendar path)? [IPM = Integrated Project Management] 34!
36 How About the Other Components of Level 3? 35!
37 Scrum and CMMI Level 2+3 PMC (progress tracking and corrective action) MA (objectives & measures) CM (baselines & versions) SAM (supplier selection & management) PPQA (process & product check) IPM (planning with assets, data, program-level tracking) RSKM (risk management) OT (planned training program) OPF (process improvement focus) OPD (process asset creation / update) DAR (tradeoffs using criteria) Backlog Planning REQM REQM REQM ò ò ò Sprint 1 Sprint 2 Sprint 3 REQM / RD PP / IPM (plans, estimates) Green = Maturity Level 2 PAs Blue = Maturity Level 3 PAs Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release Requirements (RD) Design (TS) Code (TS) Peer Review/Test (VER) Integrate (PI) Test (VAL) Release 36!
38 Collecting and Using Retrospective Data (Improve [OPF], update assets [OPD], train [OT]) Backlog Planning Sprint 1 Sprint 2 Sprint 3 Training needs Retrospective / progress / quality data Retrospective / progress / quality data Retrospective / progress / quality data Organize Improve the process Add tailoring options Improve tools Train 37!
39 Summary Scrum/Agile is a framework. Scrum is a good implementation for many of the practices in Level 2. The source of new practices is not important: Realize that they do exist, and have done for decades. Goals and problems can be addressed by adding practices to Scrum/Agile. Care needs to be taken to: a) keep the new practice small and easy to use. b) refine the practice over time. c) maintain the intent of Agile (early feedback, visibility). 38!
40 Q & A Neil Potter The Process Group neil@processgroup.com 39!
41 Appendix 40!
42 Waterfall / Scrum processgroup.com/monthlytidbits.html#tidbit12 41!
43 Generic Practices? Approximately half of the Level 2 GPs of REQM, PP, PMC and MA are implemented by Scrum. GP 2.2 GP 2.3 GP 2.4 GP 2.6 GP 2.8 Establish and maintain the plan for performing the REQM/PP/PMC/MA process. Provide adequate resources for performing the REQM/PP/PMC/MA process, developing the work products, and providing the services of the process. Assign responsibility and authority for performing the process, developing the work products, and providing the services of the REQM/PP/PMC/MA process. Place designated work products of the REQM/PP/PMC/MA process under appropriate levels of control. Monitor and control the REQM/PP/PMC/MA process against the plan for performing the process and take appropriate corrective action. The Scrum lifecycle definition and the milestones to perform Scrum. The resources and schedule time allocated to perform Scrum planning, monitoring and requirements activities. The resource assignments allocated to perform Scrum planning, monitoring and requirements activities. [Note: Scrum does not explicitly require CM to be done. However, this can be performed using a digital camera, backed up drive, or share drive with versioning and controls turned on.] Scrum Master monitoring that the steps of Scrum are followed. 42!
44 #1: Business Requirements Example Requirements Format (RD SG 2) Vision and Scope #2: User Requirements Quality Attributes System Requirements Business Rules Use Cases #3:Functional Requirements Requirements Information Other Nonfunctional Requirements Constraints Based on In Search of Excellent Requirements, Copyright 2000 by Karl E. Wiegers. Modifications & additions Copyright 2002 The Process Group Copyright The Process Group. All rights reserved.! PGV1! 43!
45 Agile Principles - 1 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. CMMI compatible Source: 44!
46 Agile Principles - 2 The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity -- the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 45!
47 References 1. Implementing Scrum (Agile) and CMMI Together. Process Group Post newsletter, March 2009." processgroup.com/pgpostmar09.pdf" 2. Adding Practices to Scrum to Achieve Your Goals (and comparison with CMMI Level 3)" processgroup.com/pgpostapr2013.pdf" 3. Scrum definition" scrumalliance.org" 4. CMMI: Guidelines for Process Integration and Product Improvement." cmmiinstitute.com/assets/reports/10tr033.pdf" 5. Scrum and CMMI Level 5: The Magic Potion for Code Warriors, by Jeff Sutherland, Carsten Ruseng Jakobsen, and Kent Johnson." 6. Potter, N., Sakry, M., Making Process Improvement Work - A Concise Action Guide for Software Managers and Practitioners, Addison-Wesley, 2002." processgroup.com/book.html" 46!
Comparing Scrum And CMMI
Comparing Scrum And CMMI How Can They Work Together Neil Potter The Process Group help@processgroup.com www.processgroup.com Version 1.0 1 Agenda Definition of Scrum Agile Principles Definition of CMMI
More informationManaging a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination)
Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Neil Potter The Process Group neil@processgroup.com 1 Agenda Summary of PMBOK, CMMI
More informationScrum, Creating Great Products & Critical Systems
Scrum, Creating Great Products & Critical Systems What to Worry About, What s Missing, How to Fix it Neil Potter The Process Group neil@processgroup.com processgroup.com Version 1.2 1 Agenda Scrum / Agile
More informationCMMI for Acquisition Quick Reference
AGREEMENT MANAGEMENT PROJECT MANAGEMENT (ML2) The purpose of Agreement Management (AM) is to ensure that the supplier and the acquirer perform according to the terms of the supplier agreement. SG 1 The
More informationCMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide
processlabs CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide CMMI-DEV V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAR - Causal Analysis and Resolution...
More informationCMMI for Technical Staff
CMMI for Technical Staff SES CMMI Training Series April 7, 2009 Audio Conference #: Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM
More informationCMMI for Services Quick Reference
CAPACITY AND AVAILABILITY MANAGEMENT PROJECT & WORK MGMT (ML3) The purpose of Capacity and Availability Management (CAM) is to ensure effective service system performance and ensure that resources are
More informationRisk Management. Kickoff Presentation
Risk Management Kickoff Presentation The Process Group Tel. 972-418-9541 Fax. 972-618-6283 E-mail: help@processgroup.com http://www.processgroup.com Copyright Intent The attendee of the classes Software
More information8. CMMI Standards and Certifications
Computer Science and Software Engineering University of Wisconsin - Platteville 8. CMMI Standards and Certifications Yan Shi SE 3730 / CS 5730 Lecture Notes This note is partially based on http://www.sei.cmu.edu/reports/10tr033.pdf
More informationDORNERWORKS QUALITY SYSTEM
DORNERWORKS QUALITY SYSTEM ALIGNMENT WITH CMMI INTRODUCTION Since its beginning, DornerWorks has had quality as one of our main goals. We have delivered solutions for over a dozen aircraft, including several
More informationA Global Overview of The Structure
A Global Overview of The Structure CMMI for Development V.1.2 Module 2 M02/GO/v1.2 Agenda Overview of CMMI General Structure of CMMI CMMI Model Representations Generic Goals and Practices CMMI by PAs and
More informationSCRUM and the CMMI. The Wolf and the Lamb shall Feed Together
The Wolf and the Lamb shall Feed Together Dr. Tami Zemel Tangram Hi-Tech Ltd. Shlomi Oren Creo Israel Ltd. The Scrum is an agile, lightweight process developed as a mean to deal with ever changing requirements
More information9/24/2011 Sof o tw t a w re e P roc o e c s e s s s Mo M d o e d l e s l 1 Wh W a h t t i s i s a Pr P oc o ess s 2 1
Software Process Models 1 What is a Process 2 1 What is a Process? Given input, transforms it into output Consist of a set of activities Ordering among the activities (a partial order) Software Process
More informationUSAF Software Technology Support Center (STSC) STSC SPI Help Desk COM , DSN
This mapping was performed by the For all your Software Improvement (SPI) needs call the USAF Software Technology Support Center (STSC) STSC SPI Help Desk COM 801.777.7214, DSN 777.7214 E-mail: larry.w.smith@hill.af.mil
More informationCMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide
processlabs CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide CMMI-SVC V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAM - Capacity and Availability Management...
More informationHighlights of CMMI and SCAMPI 1.2 Changes
Highlights of CMMI and SCAMPI 1.2 Changes Presented By: Sandra Cepeda March 2007 Material adapted from CMMI Version 1.2 and Beyond by Mike Phillips, SEI and from Sampling Update to the CMMI Steering Group
More informationSoftware Process Assessment
Software Process Assessment A method of determining the effectiveness of the software process with a goal towards improving the process. Software Process Assessment Approaches Capability Maturity Model
More informationCMMI Version 1.2. Model Changes
Pittsburgh, PA 15213-3890 CMMI Version 1.2 Model Changes SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. Capability Maturity Model, Capability Maturity Modeling,
More informationCMMI for Services (CMMI -SVC) Process Areas
CMMI for Services (CMMI -SVC) Process Areas SES CMMI Training Series August27, 2009 Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM
More informationApplying Agile Principles to Project Management. Tyler Monson PMP, CSM Hiren D. Vashi PMP, PMI-ACP, CSM, CSP
Applying Agile Principles to Project Management Tyler Monson PMP, CSM Hiren D. Vashi PMP, PMI-ACP, CSM, CSP Overview/Objective Agile Manifesto Agile Principles Agile/Scrum vs. Waterfall Modified Scrum
More informationEngineering. CMMI for Development V.1.2 Module 3. M03/Engineering/v1.2
Engineering CMMI for Development V.1.2 Module 3 M03/Engineering/v1.2 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process
More informationSoftware technology 3. Process improvement models. BSc Course Dr. Katalin Balla
Software technology 3. Process improvement models BSc Course Dr. Katalin Balla Contents Process improvement models. Popular SPI models: CMM, SPICE, CMMI The Personal Software Process (PSP) and the Team
More informationUsing Lessons Learned from Medical Checklists to Simplify CMMI Processes
Using Lessons Learned from Medical Checklists to Simplify CMMI Processes The Process Group www.processgroup.com neil@processgroup.com Neil Potter SM CMMI is a service mark of Carnegie Mellon University.
More informationWhat s New in V1.3. Judah Mogilensky Process Enhancement Partners, Inc.
What s New in V1.3 Judah Mogilensky Process Enhancement Partners, Inc. 1 Acknowledgements This presentation is based, in part, on the CMMI V1.3 released materials, as well as on several presentations by
More informationCMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print.
CMMI V.0 MODEL AT-A-GLANCE Including the following views: Development Services Supplier Management CMMI V.0 outline BOOKLET FOR print.indd CMMI V.0 An Integrated Product Suite Designed to meet the challenges
More informationMTAT Software Engineering Management
MTAT.03.243 Software Engineering Management Lecture 16: Software Process Assessment Dietmar Pfahl Spring 2013 email: dietmar.pfahl@ut.ee Structure of Lecture 16 Process Assessment Origins: CMM & CMMI Process
More informationUsing Agile Software Development to Create an Operational Testing Tool
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited. ITEA Technology Review July 2011 Using Agile Software Development to Create an Operational Testing Tool 21 Jul 2011 F.T.
More informationChapter 26 Process improvement
Chapter 26 Process improvement 1 Topics covered The process improvement process Process measurement Process analysis Process change The CMMI process improvement framework 2 Process improvement Many software
More informationMaking Processes Really Simple and Effective Using Lessons Learned from Surgical Checklists
Making Processes Really Simple and Effective Using Lessons Learned from Surgical Checklists The Process Group www.processgroup.com neil@processgroup.com Neil Potter SM CMMI is a service mark of Carnegie
More informationA Real-Life Example of Appraising and Interpreting CMMI Services Maturity Level 2
A Real-Life Example of Appraising and Interpreting CMMI Services Maturity Level 2 Neil Potter The Process Group help@processgroup.com www.processgroup.com SM CMM Integration, IDEAL, and SCAMPI are service
More informationAgile QA s Revolutionary Impact on Project Management
Agile QA s Revolutionary Impact on Project Management Introduction & Agenda Mark Layton - Certified Scrum Trainer - PMP and PMI-ACP instructor Agenda A quick overview of agile Current QA practices QA using
More informationCC and CMMI. An Approach to Integrate CC with Development
CC and CMMI An Approach to Integrate CC with Development Wolfgang Peter TÜV Informationstechnik GmbH -TÜViT - Contents 1. Status Quo 2. CMMI for Development 3. Striking Analogies 4. Combining Standards
More informationAgile Program Development. Agile Manifesto 9/3/2013. What is Agile Development? 12 Principles of Agile Development 1 of 4
What is Agile Development? Agile Program Development CSCI 479: Computer Science Design Project Fall 2013 Xiannong Meng Agile software development is a group of software development methods based on iterative
More informationPM Architecture Design as a Critical Success Factor in CMMI Model Implementation
PM Architecture Design as a Critical Success Factor in CMMI Model Implementation November, 2007 Christen M. MacMillan, PMP Implementing CMMI into Your Organization Most CMMI efforts begin with noble intentions
More informationAgile and CMMI : Disciplined Agile with Process Optimization
www.agiledigm.com Agile and CMMI : Disciplined Agile with Process Optimization Kent Aaron Johnson 02 April 2014 Long Beach, California, USA CMMI is registered in the U.S. Patent and Trademark Office by
More informationTwo Branches of Software Engineering
ENTERPRISE SOFTWARE ENGINEERING & SOFTWARE ENGINEERING IN THE ENTERPRISE Two Branches of Software Engineering 1 Crafting Software Resource Input Code Debug Product Test 2 Engineering Software Resource
More informationONE! TEAM! 2010, Nick Athanassiadis. All rights reserved.!
ONE! TEAM! 1! ONE TEAM! ONE MISSION! 2! CLIENTS! 3! WHATʼS IN OUR! BOX?! 4! 5! POST-IT!!!!!!and! 6! using! AGILE & SCRUM! METHODOLOGIES! 7! AGILE MANIFESTO! 8! AGILE MANIFESTO! Our highest priority is
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 7 Agile Methodologies: Scrum 1 Agile Methodologies: Brief History First appeared in 1995. The once-common perception that agile methodologies
More informationUpdate Observations of the Relationships between CMMI and ISO 9001:2000
Update Observations of the Relationships between CMMI and ISO 9001:2000 September September 14, 14, 2005 2005 ASQ Section 509 - ISO 9000 Users Group Page 1 This presentation summaries points made and topics
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationUsing the Equity in AS9100C to Implement CMMI-DEV Maturity Level 3
CMMI Implementations in Small & Medium Organizations Using the Equity in AS9100C to Implement CMMI-DEV Maturity Level 3 Dr. Mary Anne Herndon Sandra Salars MEI Technologies, Inc. 1 Agenda AS9100C Overview
More informationSOFTWARE ENGINEERING SOFTWARE PROCESS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE PROCESS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and provide an example,
More informationScrum Intro What s in it for me?
Scrum Intro What s in it for me? Prepared by Bachan Anand Please dial in to (218) 895-4640 PIN: 3289145 Agenda Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint What s in it for me Please
More informationThe Rational Unified Process and the Capability Maturity Model Integrated Systems/Software Engineering
The Rational Unified Process and the Capability Maturity Model Integrated Systems/Software Engineering Brian Gallagher Lisa Brownsword SM CMMI and CMM Integration are service marks of Carnegie Mellon University.
More informationTANGIBLE STRATEGIES FOR ALIGNING YOUR PROCESSES WITH AGILE
Slide 0 TANGIBLE STRATEGIES FOR // ALIGNING YOUR PROCESSES WITH AGILE 2016 Project Management Symposium Slide 1 Government Guidance and PMI Best Practices / Success? Agile Development Methodology Slide
More informationIntegrated Class C Process Appraisals (ICPA)
Integrated Class C Process Appraisals (ICPA) Kent S. McClurg Raytheon Company Garland, TX 972 205-7415 Kent_S_McClurg@raytheon.com Suzanne N. Delcambre Raytheon Company Garland, TX 972 205-7967 Suzanne_N_Delcambre@raytheon.com
More informationLesson Learned from Cross Constellations and Multi Models Process Improvement Initiatives
Lesson Learned from Cross Constellations and Multi Models Process Improvement Initiatives Kobi Vider Picker K.V.P Consulting Kobi.Vider@hotmail.com +972522946676 Conceptual Structure and Elements Dashboards
More informationUsing CMMI. Type of Work. IT solution development Software development IT solution integration IT solution deployment
Using CMMI Type of Work IT solution support / Help desk / Network support IT solution development Software development IT solution integration IT solution deployment Use COBIT/ITIL Use CMMI Levels 3-5
More informationRelationship between CMMI Maturity Levels and ISO/IEC Processes Capability Profiles
Relationship between CMMI Maturity Levels and ISO/IEC 15504 Processes Capability Profiles Antanas Mitašiūnas, Saulius Ragaišis Faculty of Mathematics and Informatics, Vilnius University, Lithuania Baltic
More informationStrategies for Transitioning to CMMI-SVC
Strategies for Transitioning to CMMI-SVC CMMI Technology Conference and User Group 16-19 November 2009 Rick Hefner, Ph.D. Northrop Grumman Corporation rick.hefner@ngc.com Topics The Business Case for Adopting
More informationCMMI v1.1 for a Service-Oriented Organization. By Steve Hall, Jeff Ricketts, Diane Simpson 16 November 2005
CMMI v1.1 for a Service-Oriented Organization By Steve Hall, Jeff Ricketts, Diane Simpson 16 November 2005 Overview This presentation will describe how CMMI v1.1 was applied to Raytheon Company s Information
More informationRussell Pannone February 10, 2009
Russell Pannone February 10, 2009 webeagile@aol.com About Me 27 years of System/Software Product Development Experience Developer Data Modeler Team Lead Project Manager Certified Scrum Master/Certified
More informationSystem Engineering Process Improvement using the CMMI in Large Space Programs
SYSTEMS MISSILES & SPACE GROUP System Engineering Process Improvement using the CMMI in Large Space Programs Revital Goldberg, Sarit Assaraf Israel Aerospace Industries 13 th Annual System Engineering
More informationTeuvo Suntio. Quality Development Tools. Professor of Power Electronics at University of Oulu. Electronic System Design A TS Rev. 1.
* * * Quality Development Tools Teuvo Suntio Professor of Power Electronics at University of Oulu Slide 1/25 Six Sigma: [1] S. G. Shina, Six Sigma for Electronics Design and Manufacturing, McGraw-Hill,
More informationPatricia A Eglin David Consulting Group
CMMI-SVC: What you need to know before you buy it Patricia A Eglin David Consulting Group Agenda What is a service? Process Areas/Continuous Representation Staged Representation CMMI-DEV versus CMMI-SVC
More informationAgile Mindset (1/17/2019 for the Ocean State PMI)
Get connected with Leapfrog LeapFrog Systems Agile Mindset (1/17/2019 for the Ocean State PMI) Agenda 1. What is Agile? 2. Compare Agile and Traditional SDLC s 3. Agile Delivery Frameworks Scrum, Kanban,
More informationQ.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно)
Partner of: Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно) based on: Software Quality Management Models: Intro to Process Improvement (PI) [SEMP Program course, in collaboration
More informationLean IT Opex in the Clouds August 16, 2017 Sudhagar Raghavan
150 Jahre Lean IT Opex in the Clouds August 16, 2017 Sudhagar Raghavan 8/22/2017 1 150 Jahre 8/22/2017 # 150 Jahre 8/22/2017 # 150 Jahre 8/22/2017 # Software Development Life Cycle - The Waterfall Model
More informationMIS Systems & Infrastructure Lifecycle Management 1. Week 10 March 24, 2016
MIS 5203 Lifecycle Management 1 Week 10 March 24, 2016 Study Objectives Software Development Processes contd. Alternate Software Development Methodologies 2 Alternate Software Development Methodologies
More informationBill Smith, CEO Leading Edge Process Consultants LLC
9 th Annual National Defense Industrial Association CMMI Technology Conference and User Group November 18, 2009 Denver, Colorado, USA Bill Smith, CEO Leading Edge Process Consultants LLC www.cmmitraining.com
More informationAre we Agile Yet? Agile is NOT a Destination
Are we Agile Yet? Agile is NOT a Destination Angela Johnson, PMP, ACP, CST Certified Scrum Trainer & Agile Coach http://www.scrumalliance.org/profiles/32158-angela-d-johnson http://angelajohnsonscrumtrainer.com
More informationExam 2012, Lecture Project Management
Exam 2012, Lecture Project Management Name: Matrikelnummer: Fachbereich: Hints: German text is permitted. Simple calculator is permitted. Dictionary is permitted. No computers. No books. Rather write less.
More informationBeing Agile at a Small Agency How to Apply Agile Principles in a Not-So-Iterative Environment
Being Agile at a Small Agency How to Apply Agile Principles in a Not-So-Iterative Environment Mark Wahl Technical Director, Jake Group @markawahl May 31, 2017 Getting Started A small, growing agency is
More informationINTRO TO AGILE PRESENTED BY. Copyright Davisbase LLC
INTRO TO AGILE PRESENTED BY AGENDA Introduction Agile Overview Why Agile? Agile Principles and Framework Overview Agile Benefits Questions INTRODUCTION Steve Davis 18 years working with software development
More informationThis resource is associated with the following paper: Assessing the maturity of software testing services using CMMI-SVC: an industrial case study
RESOURCE: MATURITY LEVELS OF THE CUSTOMIZED CMMI-SVC FOR TESTING SERVICES AND THEIR PROCESS AREAS This resource is associated with the following paper: Assessing the maturity of software testing services
More informationAgile Certified Professional
Certified Professional Study Guide Take the Certification Online www.scrumprofessionals.org Contents 1. AGILE PRIMER... 1 Roles in... 1 Cross-functional Team... 2 How an Team Plans its Work?... 3 What
More informationHigh Maturity Practices in Quality Assurance Mechanisms for Quantitative Management (QM) and Continuous Process Improvement (CPI)
High Maturity Practices in Quality Assurance Mechanisms for Quantitative Management (QM) and Continuous Process Improvement (CPI) 1 Presentation Outline Mission Solutions Maturity Profile Quality Assurance
More informationThe Quality Paradigm. Quality Paradigm Elements
The Quality Paradigm We shall build good ships here; at a profit if we can, at a loss if we must, but always good ships. motto used at Newport News Shipbuilding Quality Paradigm Elements Defining the nature
More informationSCRUM - LESSONS FROM THE TRENCHES
VOL. 19 NO. 1 HELPING YOU IMPROVE YOUR ENGINEERING PROCESS http://www.processgroup.com/newsletter.html October 2012 SCRUM - LESSONS FROM THE TRENCHES NEIL POTTER AND MARY SAKRY Introduction Agile and Scrum
More informationBuy:
Chapter-1.0 CONTENTS OF CMMI MATURITY LEVEL 3 DOCUMENT KIT (More than 160 document files) A. The Total Editable Document kit has 8 main directories as below in word/excel. CMMI-V1.3 Maturity Level 3 (Dev)
More informationDo s Don ts and Pitfalls: Planning your first CMMI appraisal
Do s Don ts and Pitfalls: Planning your first CMMI appraisal Valerie Cole, SEI-Authorized Lead Appraiser, # 0200208-01 SEI-Authorized CMMI Instructor, SEI-Authorised Class B-C Observer valerie.cole@lamri.com
More informationAgile 101. Brent Hurley Chief Problem Solver Gira Solutions. Values, Principles
Agile 101 Values, Principles and Brent Hurley Chief Problem Solver Gira Solutions @girabrent @GoAgileCamp Core Agile Series Sponsored by For$more$informa+on$on$Agile$Training,$contact:$info@bra6oninc.com$
More informationCMMI SM Mini- Assessments
CMMI SM Mini- Assessments Gary Natwick Harris Corporation Melbourne, Florida SM - CMMI is a service mark of Carnegie Mellon University next level solutions Gary Natwick - 1 Harris Corporation Government
More informationAGILE MYTH BUSTERS- THAT S NOT AGILITY!
AGILE MYTH BUSTERS- http://pmsymposium.umd.edu/pm2017/ THAT S NOT AGILITY! Susan Parente, PMP, PMI-ACP, CSM, PSM I, PMI-RMP, CISSP, ITIL, RESILIA, MS Eng. Mgmt. 2017 Project Management Symposium Agile
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More informationThis chapter illustrates the evolutionary differences between
CHAPTER 6 Contents An integrated approach Two representations CMMI process area contents Process area upgrades and additions Project management concepts process areas Project Monitoring and Control Engineering
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationGenerating Supportive Hypotheses
Generating Supportive Hypotheses in Introducing Formal Methods using a Software Process Improvement Model S. KUSAKABE, H. LIN, Y. OMORI, and K. ARAKI Grad. Sch. of Info. Sci. & Elec. Eng., Kyushu University
More informationCertified Scrum Product Owner Course. Pre-Course Reading and Exercises
Certified Scrum Product Owner Course Pre-Course Reading and Exercises For course preparation, please read the Scrum Guide http://www.scrumguides.org/docs/scrumguide/v2016/2016-scrum- Guide-US.pdf and Pierluigi
More informationAchieving Resiliency with Agile Methods
Achieving Resiliency with Agile Methods Session 11D Supannika Mobasser and Jodene Sasine The Aerospace Corporation Approved for public release. OTR 2018-00352. 2018 The Aerospace Corporation Overview Agile
More informationAgile Software Development in a Regulated Environment. Natalie Custer
Agile Software Development in a Regulated Environment Natalie Custer Disclaimer This presentation represents the understanding of the presenter on the topic addressed. It does not in anyway, form or like
More informationCS314 Software Engineering Project Management
CS314 Software Engineering Project Management Dave Matthews Software process movements Predictive 1970 Waterfall Iterative 1980s, 1990s Spiral, RAD, RUP Adaptive (Agile) late 1990s XP, Scrum, Crystal,
More informationDo s and Don ts of Appraisal Preparation
Do s and Don ts of Appraisal Preparation Pat O Toole PACT September, 2007 PACT - 1 Acknowledgments SCAMPI SM is a service mark of Carnegie Mellon University CMMI is registered in the U.S. Patent & Trademark
More informationStaged Representation Considered Harmful?
Staged Representation Considered Harmful? Terry Rout Software Griffith University Queensland, Australia CMMI Users Group, 2004 1 An Acknowledgement Edsger W. Dijkstra, Go To Statement Considered Harmful
More informationCertified Scrum Developer Program Introduction presented by. Copyright Davisbase LLC
Certified Scrum Developer Program Introduction presented by Agenda Introduction Scrum Overview Team roles Technical Excellence CSD Overview CSD Benefits Questions About Davisbase A leading, national provider
More informationSCAMPI V1.1 Method Overview
Pittsburgh, PA 15213-3890 SCAMPI V1.1 Method Overview Charles J. Ryan Sponsored by the U.S. Department of Defense 2005 by Carnegie Mellon University Objectives Review key characteristics of SCAMPI. Describe
More informationIntroduction to Disciplined Agile Delivery
IBM Software Group Introduction to Disciplined Agile Delivery 2010 IBM Corporation Agenda What is Agile Why are organizations moving to Agile and what challenges do they face How IBM is addressing these
More informationUse of Competency Guidelines to Address CMMI GP 2.5
Use of Competency Guidelines to Address CMMI GP 2.5 Mary E. Howard Raytheon Garland, Texas ALL RIGHTS RESERVED Generic Practice 2.5 Practice Train the people performing or supporting the process as needed.
More informationLet s Talk About Being Agile
Let s Talk About Being Agile Using Agile & Scrum For Project Success 27 August 2018 Agile & Scum 2 Certified Scrum Master Dec 2010 3 Agile Contributors Kent Beck Mike Beedle Arie van Bennekum Alistair
More information2005 PSM Users Group Conference Keystone, CO. Topic Introduction
The High Road to Measurement Maturity subtitled: Applying with Vengeance Speaker: Kevin Domzalski Organizational Process Optimization Lead Topic Introduction!Our Process Improvement Timeline "1989 Achieved
More informationPractical Application of the CMMI for Building a Strong Project Management Infrastructure
Practical Application of the CMMI and PMBOK for Building a Strong Project Management Infrastructure PMI - NAC and DAU 3 rd Annual Professional Development Symposium Von Braun Center Huntsville, Alabama
More informationOrganizational Synthesis - CMMI, The Glue That Binds
Organizational Synthesis - CMMI, The Glue That Binds Synthesizing: Business Process Model, ISO Standards, Life Cycle Management, Program Direction and CMMI into a Business Process Management System Eileen
More informationTraining Catalog. Version
Training Catalog Version 160101 Table of Contents Training by ASK Process, Inc. Training by ASK Process, Inc.... 1 Agile Software Development Series... 3 Executive Workshop: Agile Methods _(1+/- Day)...
More informationHow to Prepare for and Implement a Project Using Scrum
How to Prepare for and Implement a Project Using Scrum 2013 IEEE Software Technology Conference Salt Lake City, UT Dick Carlson Richard.Carlson2@Boeing.com Philip J. Matuzic Philip.J.Matuzic@Boeing.com
More informationBeyond the Manifesto
Presented at the 2017 ICEAA Professional Development & Training Workshop Beyond the Manifesto Once you commit to an Agile Methodology, how do you measure your progress? Gordon Kranz Michael Thompson ICEAA
More informationCapability Maturity Model Integration (CMMI) V1.3 and Architecture-Centric Engineering
Capability Maturity Model Integration (CMMI) V1.3 and Architecture-Centric SATURN Conference May 17, 2011 San Francisco, CA Dr. Lawrence G. Jones Dr. Michael Konrad Software Institute Carnegie Mellon University
More informationHELP!!! THE SCRUM MASTER IS THE IMPEDIMENT!
HELP!!! THE SCRUM MASTER IS THE IMPEDIMENT! @ryanripley PMI-ACP, PSM I, PSM II, PSE, PSPO I, PSD I, CSM, and CSPO SCRUM IN ONE SLIDE ROLES: Scrum Master, Product Owner, Developer ARTIFACTS: Product Backlog,
More informationSoftware Engineering. M Umair.
Software Engineering M Umair www.m-umair.com Activity and Sprint An activity is a general term for any part of a project that takes place over time (also known as a task) Each step in the software development
More informationCMMI SM Model Measurement and Analysis
Carnegie Mellon University Software Engineering Institute CMMI SM Model CMMI SM is a Service Mark of Carnegie Mellon University Carnegie Mellon University Software Engineering Institute CMMI Staged Representation
More information