TSP*-Agile Blend: The Gun Smoke Clears Alan Padula TSP Symposium September 21-24, 2009 New Orleans, Louisiana 2009 Intuit Inc. All rights reserved. * SM TSP Team Software Process and TSP are service marks of Carnegie Mellon University.
Outcomes Understand Intuit s TSP-Agile Blend (TAB) process to see if it is applicable to your organization including: Iteration 0 Meetings Measures Understand some of the perceptions of the commonalities and differences between TSP, Agile, and TAB Understand some of the challenges, risks, benefits, and mitigation strategies of adopting TAB 2 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
Agenda TSP-Agile Blend What are we solving for TSP is a framework The Agile Mindset About TAB Adoption Challenges Qualitative Project Data Summary About TAB TAB Fundamentals TAB Agile in a TSP Framework Heart of the TAB Model Iteration 0 Recurring Iterations (Scrum) Meeting Driven Conceptual Model Measures 3 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
TSP-Agile Blend What we are solving for? A Software Development Lifecycle that leverages the best of the TSP and Agile development models in order to create high-quality products in a predictable and repeatable fashion including projects with rapidly changing or unknown customer or technology requirements. 4 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
TSP is a Framework Misperception TSP Agile Reality TSP Framework Agile Mindset/Principles Agile Practice Agile Practice Agile Practice Agile Practice Agile Practice TSP & Agile are much more closely aligned than many TSP or Agile advocates might think! 5 Intuit Proprietary & Confidential
The Agile Mindset Individuals & Interactions Agile Manifesto processes and tools Working Software comprehensive documentation Customer Collaboration contract negotiation Responding to Change Stephen Coburn While there is value in the items on the right, we value the items on the left more. following a plan The difference that makes the difference is the Agile mindset shift 6 - apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
Agenda TSP-Agile Blend What are we solving for TSP is a Framework The Agile Mindset We are here About TAB Adoption Challenges Qualitative Project Data Summary About TAB TAB Fundamentals TAB Agile in a TSP Framework Heart of the TAB Model Iteration 0 Recurring Iterations (Scrum) Meeting Driven Conceptual Model Measures 7 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
TSP-Agile Blend (TAB) Heart of The Model R Recurring Iterations Process 7 Team Meetings Iteration 0 Process 6 Team Meetings 6+ One-on-Ones 0 Release Planning Launch Meeting The heart of TAB is Iteration 0 + Recurring Iterations Iteration 0 consists of Architecture, Requirements, UI, Dev Infrastructure, & Launch 8 - padula Intuit Confidential
TSP Agile-Blend Model Detail 0 R Vision, ROI, Business requirements Iteration 0 Architectural Design SPIKE High level Architecture/System Design, Technology Prototypes Release Launch Iteration 1 Iteration 2 Release Train (See Upcoming Slides) Maintenance User-Centered Design SPIKE Qualitative & Quantitative Research, Secondary Research, End-to-End Conceptual Models, High-Level Process Flows, Use Cases, Personas, Scenarios Iteration n Release Train User Story Design SPIKE Product Owner: Customer needs research, partnership recruitment, story & acceptance test creation, prioritized backlog, optimal rollout plan and timeline Release Train Infrastructure/Planning Prep Engineering/QA infrastructure: Unit test harnesses, automated test setup, process design, daily/continuous builds, Quality & test Plans, development & planning tools, functional milestones Typically 2-4 Weeks (not to scale) 2-6 Weeks 6 Weeks Ongoing * Special thanks to Glynis Hively for her User-Centered Design contributions.
TSP-Agile Blend Release Launch Driven more by agile thinking Driven more by TSP thinking Product & Business Goals Roles & Team Goals Development Strategy --- Conceptual Design --- Sizing Top Down & Next-Phase Plans Bottom-up & Balanced Plans Quality Plan Risk Assessment Briefing & Launch Report Management Review Reduced Set of Roles StoryPoint Estimation Agile Processes & Practices StoryPoint-Based End-to-End Release Plan without a detailed WBS WBS for next cycle only with Tasks, Hours, & Assignments Estimates based on Stories not Design Definition of Done Less emphasis on defect analysis Significant differences from a typical Waterfall Project in the TSP Framework Iteration 0 Architecture & High-Level Design More rigor with metrics Significant differences from a typical Agile Project TSP & Agile have different emphasis or methods for Roles, Design, Estimation, & Measures 10 Intuit Proprietary & Confidential
Iteration 0 Meetings IM Overview & Selection Kickoff Sponsor Meeting-Driven Process Model Internet 0 PM XD Process Customization QA Quality & Done Definition User Stories Story Point Estimates Release Launch ScrumMaster War Room Timel line Prep Instructions Meeting Materials Agenda Checklists TAB Repository Recurring Meetings Iteration Planning R Daily Standup Mid-Iteration Pre-Planning Demo & Review Retrospective 11 - apadula Eliminate Process-speak; everybody gets Meetings Coaches Toolkit simplifies execution Intuit Confidential 2009 Intuit Inc. All rights reserved.
Scrum Process & Some Coaching Tips Vision: ROI, Scrum Releases, Process Milestones Sized in Story Points R Sized in Task Hours Product Owner Emerging, prioritized requirements Cross Functional Scrum Team Daily Standup Meetings Product Release Backlog Iteration Backlog 3 Weeks of Development New learnings, Unfinished stories, Defects TAB adds just enough extra structure to the standard Scrum Processto make it more viable at Intuit Demo & Retrospective New functionality is demonstrated at end of Sprint 12 - apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
ADR Recurring Meetings Iteration Backlog Meeting Iteration Task Definition Meeting C o m m I t Intuit Best Practices Safety Net for Common Missteps Iteration Demo & Review Meeting Iteration Retrospective Meeting Team Health Survey Schedule Confidence Quality Confidence Workload Comfort Motivation Teaming Iteration Planning Week 1 Week 2 Week 3 Every Week Daily 15 Min Standup Daily 15 Min Standup Mid Iteration Reflection Progress Analysis Quality Analysis Process Analysis Risk Analysis Daily 15 Min Standup Daily 15 Min Standup Pre-Planning Meeting Daily 15 Min Standup Next Iteration Story Refinement & Highlevel Technical Analysis Support for XD work for next 2 iterations New story estimation Expand Epic Backlog Prioritization Update Release Plan Intuit Best Practices & Lessons Learned are weaved into a Scrum Process customized for Intuit needs Intuit Proprietary & Confidential *** Intuit Confidential *** apadula
Definition of Done Metrics Only* Iteration Burndown Task Hours Release Burndown Earned Value (EV) or Story Points Task Hours Planned (P)/Actual (A) Hours Story Points or EV P/A Scope EV Growth/Time or Story Point Count 1 R e v i e w s Working, ready-to-ship software that meets or exceeds customer expectations Quality is everyone s job & is continuously built-in Two customers must be served: 1. End-user 2. Funding organization Reviews: Time, Defects Found Design : Review Time Code : Review Time Test : Test Review Time Design : Code Time 2 Optional 4 Defect Type Defect Phase Insertion Defect Phase Detection Productivity LOC/Hour or Story Points/Iteration (Velocity) Task Hours/Week 1 2 3 4 For planning only never used in performance reviews! - Reviews may include collaborative design or pair programming time which are common agile practices. - Planned (P) measures for Quality are desirable but optional. - Significant (non-cosmetic) defects only Test Code Coverage includes unit & black box testing A valuable empirical method to help determine the most important areas for improvement is lost T e s t B u g s Test Code Coverage % 3 Feature/Story Coverage % Test Execution Results Test Automation % #/KLOC *There is other criteria besides these type of metrics that go into defining done for agile projects Intuit Proprietary & Confidential # Incoming, Open, Closed # Open by Impact & Severity # Post-release defects Still Derivable Cost of Quality Review Rates Yield Defect Cost Defect Predict Size Time Bugs apadula
Agenda TSP-Agile Blend What are we solving for TSP is a framework The Agile Mindset About TAB Adoption Challenges Qualitative Project Data Summary About TAB TAB Fundamentals TAB Agile in a TSP Framework Heart of the TAB Model Iteration 0 Recurring Iterations (Scrum) Meeting Driven Conceptual Model Measures We are here 15 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
Qualitative Data Schedule Confidence WORSE SAME BETTER Quality Confidence WORSE SAME BETTER 12% 50% 50% 88% Workload WORSE SAME BETTER Net Promoter Score 4 4 4 75% 25% # Votes 3 2 1 0 1 1 2 3 4 5 6 7 8 9 10 1 = Worst 10 = Best 16 apadula Intuit Proprietary & Confidential
Tales from the Dark Side "I can't code to this!" "I need a detailed schedule now!" "I can't prioritize this... we need everything!" There are way more meetings now! "Nope... it's impossible to do in a single iteration" Why hasn t throughput increased? "What? We won't get all the features? We don t need to collect metrics just deliver Working SW Sergey Rusakov "Look at how many hours I worked" OR "I'm 80% done"
WRAPUP Understand Intuit s TSP-Agile Blend (TAB) process to see if it is applicable to your organization including: Iteration 0 Meetings Measures Understand some of the perceptions of the commonalities and differences between TSP, Agile, and TAB Understand some of the challenges, risks, benefits, and mitigation strategies of adopting TAB 18 apadula 2009 Intuit Intuit Proprietary Inc. All & rights Confidential reserved.
Contact Information Paper and presentation available online via Conference Alan Padula alan_padula@intuit.com 19 apadula Intuit Proprietary & Confidential