We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byPaige Schultz
Modified over 3 years ago
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 1 Science Applications International Corporation An Employee-Owned Company ® Richard D. Stutzke Science Applications International Corp. 6725 Odyssey Drive Huntsville, AL 35806-3301 (256) 864-8383 (office) (256) 864-8200 (facsimile) (256) 864-8397 (asst) Richard.D.Stutzke@saic.com Agile Methods and Process Maturity
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 2 Science Applications International Corporation An Employee-Owned Company ® Different Goals Disciplined Methods (CMMI processes) –Consistency –Stability –Predictability Agile Methods –Respond to rapid change –Promotes innovation –WYSIWYG
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 3 Science Applications International Corporation An Employee-Owned Company ® Comparison of Characteristics AreaCharacteristicDisciplinedAgile Product Requirements Specifications Emphasis for Acceptability Deliveries Operational Life Knowable and stable Formal document(s) High assurance (risk adverse) One or a few Multiple years or decades Unprecedented and emergent Prioritized list of features Rapid capability (fast benefit) Often (monthly or less) One year or less Process Definition of activities Cost of rework Control Customer Liaison Plan revisions Explicit documents and plans Increases with time Quantitative, directed Periodic reviews (fire and forget) Yearly (quarterly) Informal plans Remains fairly constant Qualitative, consensus Collocated with development team Weekly (daily) People Team SizeFew to hundredsLess than 35 Project Constraints Contract Types Functions, Cost, Schedule, and Quality FFP, Cost Plus Cost or Schedule, Quality, Functions T&M, Cost Plus
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 4 Science Applications International Corporation An Employee-Owned Company ® Comparison of Activities RA … PD DD CUT IT Start V1 V2 V3 V4 VN (IOC) (FOC) Activities Milestones: Waterfall RAPDDDCUTIT Start SDRPDR CDRUTC TRR IOC (SRR) Activities Milestones: Agile
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 5 Science Applications International Corporation An Employee-Owned Company ® Comparison by CMMI Level
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 6 Science Applications International Corporation An Employee-Owned Company ® Comparison by CMMI Discipline
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 7 Science Applications International Corporation An Employee-Owned Company ® Our Changing World* The PastThe Future (Now?) Standalone systems Highly interconnected systems Stable requirements Rapidly changing requirements Requirements drive custom, complete solution COTS capabilities drive affordable, adequate solution Buyer controls product evolution Vendor controls COTS evolution Enough time to keep stableEver-decreasing cycle times Repeatable process (maturity models) Adaptive process models * Based on a presentation by Barry Boehm on 11/13/2002.
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 8 Science Applications International Corporation An Employee-Owned Company ® CMMI Supports Agility All stakeholders collaborate on requirements (RD/SG1, IPM/SG2) Recursion of engineering PAs (e.g. RD, TS) Product Integration PA can support continuous integration Engineering and Support PAs (e.g. VAL, CM) are compatible with test-driven design and automated tools Alternative practices provide an entry point for innovative approaches Scope allows multiple disciplines and approaches for different components
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 9 Science Applications International Corporation An Employee-Owned Company ® The Need for Balance Project success requires both agility and discipline –Different parts of a project can use different approaches –Agile for emerging or rapidly evolving components –Plan-driven for well-understood or regulated component –Use risk to decide Important Process Areas –Risk management (involve all stakeholders) –Integrated Project Management (tailoring, involve stakeholders) –Integrated Teaming (skills, roles, organization) –Decision Analysis and Resolution (streamlined, simple techniques)
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 10 Science Applications International Corporation An Employee-Owned Company ® Tool to Select the Appropriate Process* *from [Boehm, 2004]. Used with permission.
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 11 Science Applications International Corporation An Employee-Owned Company ® Questions to Ponder How measure defects: –Old: Team peer review finished work product (change defect) –New: Team reviews and fixes immediately (refactor) How measure progress? –Artifacts accumulate detail –Process activities continuously improve –Milestone content (process anchors) How estimate? –CAIV, SAIV, or Time Boxing –SouthernSCOPE (SCUD) How specify, procure, and sustain systems? –Contract law –Program management (milestones, work products) –Deliverables (Technical Data Package) –COTS refresh and obsolescence
©2004 by Richard D. StutzkeAgile Methods and Process Maturity.ppt 12 Science Applications International Corporation An Employee-Owned Company ® References [Chrissis, 2003]CMMI – Guidelines for Process Integration and Product Improvement, Mary Beth Chrissis, Mike Conrad, and Sandy Shrum, Addison-Wesley, 2003, ISBN 0-321-15496-7 [Boehm, 2004]Balancing Agility and Discipline: A Guide for the Perplexed, Barry Boehm and Richard Turner, Addison-Wesley, 2004, ISBN 0-321- 18612-5. A web site with many links for agile methods is: http://www.iturls.com/English/SoftwareEngineering/SE_Agile.asp The web site for southernSCOPE is: http:// www.mmv.vic.gov.au/southernscope
CMMI Course Summary CMMI course Module 9..
University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
Dean Cox Naval Undersea Warfare Center, Keyport Capability maturity model integration CMMI FOR Washington state university 16 September 2009.
COMP3001 Technology Management & Professional Issues: Project Management Agile and Iterative Planning Lecture 7 Graham Collins, UCL
1 Discipline vs. Agility. 2 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors.
Agile Center of Excellence. Richard K Cheng Agile is just a high level concept.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13 Checkpoints of the Process (from Chapter 9 of Royce’ book)
Integrated Project Management IPM (Without IPPD) Intermediate Concepts of CMMI Project meets the organization Author: Kiril Karaatanasov
Chapter 2- Software Development Process Product Components Software Project Staff Software Development Lifecycle Models.
Chapter : Software Process. Chapter - Topic Covered Layered Technology Software Process Framework Generic Process Framework Activities Umbrella.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome Introductions What is your experience with RUP What is.
Software Life Cycles ECE 417/617: Elements of Software Engineering Stan Birchfield Clemson University.
CSE 470 : Software Engineering The Software Process.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Application of the CMMI SM to Plan and Control Life Cycle Costs Dr. Mary Anne Herndon Science Applications International Corporation (SAIC) November, 2003.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CPTE 209 Software Engineering Summary and Review.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
Dr. Ralph R. Young Director of Software Engineering Systems and Process Engineering Defense Enterprise Solutions Northrop Grumman Information Technology.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
13-January-2003cse LifeCycle © 2003 University of Washington1 Lifecycle CSE 403, Winter 2003 Software Engineering
Chapter 4 Software Process Models. What is a Process Model ? It is a description of i) what tasks need to be performed in ii) what sequence under iii)
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Lecture 5: Requirements Engineering Dr Valentina Plekhanova University of Sunderland, UK
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Engineering Process - II 5.1 Unit 5: Alternate Software Development Methodologies Software Engineering Process - II.
Organizational Project Management Maturity: Roadmap to Success Project Management Institute Washington, DC Chapter Knowledge Exchange Forum October 26,
Pfleeger and Atlee, Software Engineering: Theory and Practice CS499 Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4 th.
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
14% of the exam 24 questions 1 Carol Pattyn 6/18/13.
Agile Software Development. Traditional Software Development 1.Initiation (RFP) 2.Feasibility study Technical – can we build it? Economic – should we.
SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
CS 360 Lecture 3. The software process is a structured set of activities required to develop a software system. Fundamental Assumption: Good software.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Software Engineering (CSI 321) Software Process: A Generic View 1.
The Project Plan Plan Your Work, then Work Your Plan Will Brimberry, Program Manager Project Management Office Office of the Chief Information Officer.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS The Speculate Phase (Ch. 6)
CMMI Overview Dr. Korson Software Engineering. 2 Immature organizations can be successful on occasion, but ultimately run into difficulties because –Success.
Christophe Fiessinger Senior Technical Product Manager Microsoft Corporation.
© 2017 SlidePlayer.com Inc. All rights reserved.