Sustainable Software Development in Agile and CMMI: Apply Lessons Learned today

Transcription

1 Sustainable Software Development in Agile and CMMI: Apply Lessons Learned today 2009

2 What is the CMMI Level 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed 1 Initial Focus Continuous Process Quantitative Management Process Standardization Basic Project Management Process Areas Organizational Innovation and Deployment Causal Analysis and Resolution Organizational Process Performance Quantitative Project Management Requirements Development Technical Solution Product Integration Verification Validation Organizational Process Focus Organizational Process Definition Organizational Training Integrated Project Management for IPPD Risk Management Integrated Teaming Integrated Supplier Management Decision Analysis and Resolution Organizational Environment for Integration Requirements Management Project Planning Project Monitoring and Control Supplier Agreement Management Measurement and Analysis Process and Product Quality Assurance Configuration Management Quality & Risk & Rework Capability Maturity Model Integration (CMMI) is a process improvement approach that provides organizations with the essential elements of effective processes.

3 What is Agile Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing crossfunctional teams. Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of highquality software, and a business approach that aligns development with customer needs and company goals.

4 Agile by Brand Name extremeprogramming (XP) [Beck] Widest known, developer-focused for small teams Crystal methodolgies[coburn] - Set of methodologies conditional on circumstances - Only 2 defined: Crystal Clear, Crystal Orange Feature-Driven Development (FDD) [Palmer] - Agile approach closest to conventional development Scrum [Schwaber] - Focused on management practices Lean Software Development [Poppendieck] -Inspired by Toyota Production System, particularly its product development practices

5 What Can We Change People Technology Process The major determinants to Quality, Time to Market and Cost of software

6 Frameworks, Models and Tools Frameworks CMMI Prince II ITIL What Organization Methods xp Waterfall Tactics Tools Six Sigma Function Points ISO 9000 Agile PSM TSP RUP Balanced Scorecard PIMBOK CMMI SOX EFQM TQM Lean Function Points ITIL Six Sigma CoBIT

7 CMMI and Agile: Strange Bed Fellows Areas of Friction: Empowerment and trust versus micromanagement Solution: Coach as PPQA Organization standards versus project standards Tailoring guidance to allow teams to overrule Intermediate Work Products Solution: Define what is sufficient

8 Uncertainty You start projects knowing very little (as compared to when a project is implemented) Unknowns Cone of Uncertainty Knowledge Budgeting Initiation Implementation Words are the only thing typically known before a project is initiated (usually not very many)

9 Hierarchy Of Models Baldridge ISO9001 CoBIT People CMM ISO CMMI DEV CMMI ACQ CMMI Services escm Overall Organizational Silo Specific Many models...pressing questions: How are models related? What are the synergies? How can implementations of multiple models be harmonized?

10 What can be achieved quickly? Project Name Profile Score Management Definition Design Build Test Environment Accounts Payable Priotity One HR Enhancements Client Accounts ABC Release Screen Redesign Customer Web Whole Life Regional - East Regional - West Cashflow Credit Automation NISE Help Desk Automation Formula One Upgrade Process s: Code Reviews and Inspections Requirements Management Defect Tracking Configuration Management Project Name Profile Score Management Definition Design Build Test Environment Accounts Payable Priotity One HR Enhancements Client Accounts ABC Release Screen Redesign Customer Web Whole Life Regional - East Regional - West Cashflow Credit Automation NISE Help Desk Automation Formula One Upgrade Baseline Average Project Size 133 Average FP/SM 10.7 Average Time-To-Market (Months) 6.9 Average Cost/FP $939 Delivered Defects/FP Performance s: ~ +131% Time to Market ~ -49% Defect Ratio ~ -75% Average Project Size 133 Average FP/SM 24.8 Average Time-To-Market (Months) 3.5 Average Cost/FP $467 Delivered Defects/FP

11 Agile Implementations of Common CMMI Practices PM - SCRUM Requirements Management Backlog Peer review pair programming Quality Control TDD CM Continuous builds What is the impact?

12 Impact Data From Where? DCG Project Data Store Filter for Approximate Project Size Filter for Complexity and Sourcing All data is less than three years old. All data collected and vetted by DCG. Metrics Signature *approximate 12

13 SCRUM v. Classic Project Management 4% 2% 11% 7 % Time-to-Market Total Defects Maintenance Classic Project Management SCRUM 8% 13% 10% 17% Time-to-Market Total Defects Maintenance

14 Peer Review v Collaborative Development 13% 6% 30% 21% Time-to-Market Total Defects Maintenance Peer Review Collaborative Development 18% 10% 37% 17% Time-to-Market Total Defects Maintenance

15 Requirements Management v Backlogs 2-4% - % 5 % 2-3% Time-to-Market Total Defects Maintenance Requirements Management Backlogs 2-4 % 1-2 % 5 % - % Time-to-Market Total Defects Maintenance

16 Classic Testing v TDD 7 % 3% 35% 16% Time-to-Market Total Defects Maintenance Classic Testing Test Driven Development 11% 4 % 61% 32% Time-to-Market Total Defects Maintenance

17 Configuration Management v Continuous Integration 3-4 % - % 2-3 % 1-3 % Time-to-Market Total Defects Maintenance Configuration Management CM with Continuous Integration 5 7% 7 % 5-8 % - % Time-to-Market Total Defects Maintenance

18 Case One Small custom technology organization (internal and external projects), Highly collaborative culture Mixed SCRUM and Plan Based project environment All external projects are bid with fixed caps Internal projects continually scoped to fit internal development budget Estimates had mixed success rate

19 The Answer Internal with Sales acting as proxy customer Postacceptance Develop and Pre-size backlog Application of, Capabilities Bid Development Refinement During Sprint Planning Techniques Used QEFP for sizing backlog Explicit risk and skills evaluation Planning Poker Impact Proposals increased 20% Negative misses nearly eradicated (underbidding on fixed price contract)

20 Case Two Large software development firm, hierarchical culture and one very large project and many smaller Mixed SCRUM/XP (recent addition) and Plan Based project environment Strenuous budgeting process with tax accruals Significant discovery was required to define, design and develop the large project Experienced based estimation based on bottom up task planning questionable on the large project!

21 The Answer Techniques Used QEFP for sizing backlog QEFP for sizing items added during sprint planning Planning Poker Impact Improved product owner satisfaction Increased perception of consistency Reduced number of stories escaping sprints

22 Manifesto Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

23 Your Turn Questions? Thomas Cagley Jr. (440)