Living Iteratively "Don't drive angry!" American Society for Quality Fall Conference November 3, 2016
Objectives 1. Identify the "right" opportunities to leverage iterative / incremental development (IID) 2. IID Exercise: "Living Iteratively" Time-Boxing Iterative Prototyping / Usability Iterative Stand-Ups
Waterfall Why IID? WHAT? HOW? WHY? IID Hybrid Hardware Installation
Why IID? Why? 100% 11% End-User Adoption Improved scope, less unused, unneeded functionality 10% Quality Lower cost due to less work 4% 125% Time-to-Value Benefits realization pulled from iterative releases rather than one single release at the project s end Traditional Approaches Source: Corporate Executive Board Expected Benefits Using IID
"Spar" with Change Why? Daily Focus Timely Risk / Impact Assessments Real-Time Communication
Conduct Quality Checkpoints Why? Daily Metrics Iterative Incremental Deliverable Sign-Offs
Build Value "One Success at a Time" Why? "Time-to-Value" Incremental Releases
IID Methodology How Iterations (Sprints)
IID Methodology How Incremental Iterative
Time-Boxing Picking a Date Study or Socialize? Student Syndrome wait until the very last minute to start their assignments Parkinson's Law work assigned expands to fill the allotted time
Rube Goldberg TIME-BOXED Exercise
Rube Goldberg "Hands-On" TIME-BOX Objective: 30 minutes: Needs: Pop a balloon! 25 minutes construction 5 minutes at end to showcase with other teams Race Track (10) Dominos (10) Pulley (20) POPPED Balloon! (40) Bonus Points: Mouse Trap (20) TOTAL Points Possible: 100 pts Pulley Examples:
Status JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR Time-Boxing Time-Boxed Baseline 2016 2017 Tax Season NAME Planned Date Hard Date PHASE Product X 4/7 Plan Design/Development Test Plan Planning Requirements Signed off 7/29 8/31 Planning 7/22 8/31 Approval for Execution 7/24 Planning 7/25 Res ources As s igned & Coding Begins 7/29 Planning 7/29 Ris k As s es s ment Complete 8/31 Planning 8/31 Des ign/development Des ign / Dev Test Strategy Complete 8/25 9/16 Des ign / Dev 8/25 9/16 Functional Stream Tes t Strategies Complete 9/30 Des ign / Dev 9/30 Des ign Complete - Edelivery 9/30 9/30 Impl 9/30 Us ability Reviews Complete 10/7 Des ign / Dev 10/7 GUI Prototypes Complete 10/14 Des ign / Dev 10/14 Tes t Plans Complete 10/14 Des ign / Dev 10/14 Coding Complete 10/24 10/24 Des ign / Dev 10/24 Unit / Integration Tes ting Complete 10/21 Des ign / Dev 10/21 Development Complete - Edelivery 11/11 11/11 Impl 11/11 Tes ting Tes ting UAT Begins 10/24 Tes ting 10/24 UAT Complete 1/17 1/26 Tes ting 1/17 Pre-Prod Tes ting (QA Only) Begins 1/20 Tes ting 1/20 Production Ready 2/16 2/16 Tes ting 2/16 Implementation Implementation Plan Complete 3/17 Impl 3/17 Roll-Out Complete 2/24 3/24 Impl 2/24 3/24 Impl Impl.
Prototyping How Working model displaying limited functionality of the product under development. PERFECTION is your enemy! Rapid prototyping helps evolve customer requirements in the early stage of development. Prototypes can have business and technical dimensions.
Iterative Prototyping/Usability Gather Level 1 Requirements Create L1 Wireframe Gather Level 2 Requirements Create L2 Wireframe Conduct Interviews Gather Level 3 Requirements Create Prototypes Conduct End-User Trial Revise Prototypes Develop / Build Deliverables
Prototyping Case Study Seven Existing Screens Combine into One Screen
Prototyping Case Study
Effort Effort Iterative Effort How Waterfall Integration Functional / Performance Bundle Regression Test Strategy / Plans Unit Planning Design Development Verification Implementation IID Time-Block 1 Unit Integration Functional Performance Time-Block 2 Unit Integration Functional Performance Time-Block 3 Unit Integration Functional Performance Time-Block 4 Unit Integration Functional Performance Time-Block 5 Unit Integration Functional Performance Time-Block 6 Bundle Regression Test Strategy / Plans Planning Design Development / Verification Implementation
Effort Effort Iterative Test Planning How Waterfall Test Script BLITZ! > 80% Test Scripts Integration Functional / Performance Bundle Regression Test Strategy / Scripts Unit Planning Design Development Verification Implementation IID Requirements PRIORITIZATION Critical! Time-Block 1 Test Scripts 1 Time-Block 2 Test Scripts 1-2 Time-Block 3 Test Scripts 1-3 Time-Block 4 Test Scripts 1-4 Time-Block 5 Test Scripts 1-5 Time-Block 6 Bundle Regression Test Strategy / Scripts Planning Design Development / Verification Implementation
The Right Mindset How DEFEND DISCOVER!
Stand-Ups PURPOSE: Team alignment, focus, momentum, commitment Each team member answers three questions: 1. What did you do yesterday? 2. What will you do today? 3. Are there any obstacles in your way? Key Decisions Scope Alignment Resource Contentions Technology
Stand-Up Cadence Daily Stand-Ups 24 H 1-4 WEEKS Review Requirements Prioritized Chunking Master Schedule Deliverables time-boxed Tasks identified by team Team commitment Lessons-Learned
Stand-Ups - TIPS Standing promotes engagement Co-Location is critical Team visualization breeds accountability and collaboration Start and end ON TIME
Living Iteratively Iterative / Incremental approach promotes: High team interaction / creativity Heightened communication Alignment of expectations Early value realization Constant learning / improvement Product QUALITY + VALUE
Thank you for thinking outside the box!