Value Driven Development Maximum Value, Maximum Speed – Targeted Innovation Trumps Systemic Transformation Dave Thomas www.davethomas.net Chief Scientist, Kx Systems. Chairman YOW! Conferences, Carleton University, Canada Outline • A Brief Message from your CEO • Process Driven Development • Value Driven Development • Techniques for Reduced Time/Cost to Value
Plan ‘everything’ before you do ‘anything’ until… It’s 2 years late, 173% over budget, kinda buggy, & costs $32,345.99… But “it does everything you’d ever want to do!” The ‘Potential’ Agile Pitfall “Planning, shmanning, I need to add 1+1, so let’s just build it!” On time, on budget, and we’re giving it away as a beta. “It’s bug-free, it works, and it adds 1+1!” Darn… now how do we add all the features we never had time to think about? Envisioning gives Agile some breathing room… Allows us to understand enough of the vision of ‘tomorrow’… Low-Fidelity Envisioning Prototype Example Low-fidelity prototype § Initially rough and then later refined drawings § Interactive branching allowed walkthrough § User model, task model, task flows § 3 structure and navigation alternatives § 2 visual form alternatives Concept iterations § 6 iterations (expanding from 8 to 48 screens) § 3 sprints § 3 internal / 2 external customer sessions Detail iterations § 3 iterations (148 screens) § 8 sprints § 3 internal / 1 external customer sessions Investment § Less than 2% of overall effort
L1, L2, L3,L4; Vendor EAP V1, V2,V3,V4,V5; Integration Services I5, I6; Commercial Insurance V1, L1 Personal Insurance L2; Vehicle Insurance V2 Rating Engine L2, L3, V3; Billing System V4 Policy System of Record L4 + I5 + V5 Enterprise Software Bus I6 Solution 1. Outstanding BAs define all products in tables 2. Agile experts generate applications from BA tables 3. SI experts build simple interfaces to ESB + Interface Acceptance Tests 4. All vendors required to deliver acceptance test HR System Bottleneck Challenge • calculations very complex. • analysts capture in Excel. • 100 Devs in COBOL too slow • Agile OO gave only 15% in productivity Solution 1. Retain 2 Agile OO experts 2. Excel rule checker in java 3. Spreadsheet in Java on mainframe 4. Legacy team deployed on other systems