i ntelligence i nnovation i ntegrity Instituting Kanban on a Time Boxed Program 13 Tips to Take Advantage Of Wade Scherer Michael Byrne The Spitfire Group, LLC

i ntelligence i nnovation i ntegrity Spitfire Group, LLC Beliefs Do projects right Efficiently High business value Teams Modeled on US Army Special Forces Solution Managers Business Analysts Application Architects Developers QA Consulting Practice Areas Technology Strategy Application Security Custom Software Development / Integration

i ntelligence i nnovation i ntegrity The Situation Use Kanban to Respect Team and Enhance Existing Methodology – Scrum previously dropped with this team Create IT Discipline Minimal Methodology Previously in Place Goal: Growth / Acquisitions Existing IT Infrastructure Not Scalable Large Back Office Replacement Program 2 years – 6 major components Complete Back Office replacement Aggressive Schedule Make the Sale! Creativity in Configurations as a Sales Tool Permissive Business Process Environment If the system can’t support, figure out how to make it work Inconsistent data stores, minimal enforced integration History

i ntelligence i nnovation i ntegrity Kanban Aspects of Program Tip 1: Take Advantage of Every Aspect AvailableTip 2: Be Aware of the All the Aspects

i ntelligence i nnovation i ntegrity kanban - Physical Board Tip 3: Visualization is essential to communicating performance

i ntelligence i nnovation i ntegrity Process Explicit and Visible Definitions of DoneConstructed and Valued by TeamObservance fluctuatedTip 4: Provides Team an Anchor to refer to

i ntelligence i nnovation i ntegrity Analysis Added to Board Visibility to Avoid Developer StarvationAnalysis Structure including Explicit PolicyProductive Development Team outpaced Analysis TeamTip 5: Make it VISIBLE!!! Apply Kanban Where Needed

i ntelligence i nnovation i ntegrity WIP Gone Wild! More traffic does NOT Mean Faster!Tip 6: Need a Lean Advocate to Focus on Fewer Tasks

i ntelligence i nnovation i ntegrity Planning – Story Maps Tip 7: Story Maps Provide Context and a Visual Planning Tool Used by Team -> Stopped Using -> Team Wanted Back!

i ntelligence i nnovation i ntegrity Tools Metrics Possible with Weak Tools No Status Change Time Stamp – No Cycle Time?Create Your Own!Tip 8: Work with the Data You Do Have

i ntelligence i nnovation i ntegrity Business Trust is Critical Difficult to get Cooperation without Trust Avoid an Adversarial Relationship Can Severely Impede Progress Why is it Critical? Customer must trust you understand business. Communicate with them! Get their feedback and act on it! Provide a solid quality product Tips 9: Gain the Business Trust

i ntelligence i nnovation i ntegrity Core Values – Quality Matters Meeting Schedule and Budget High Quality Product What’s More Important? Misleading: Lines-of-Code vs. Defects Better: Defect Rate Better: Survey Business Satisfaction Tips 10: How can you observe Quality?

i ntelligence i nnovation i ntegrity Quality vs Throughput Product 3 Release Product 1 Release – 6/12 Product 2 – Mon. Arch. Product 4 Release Quality does not remain flat as throughput increasesTip 11: Maintaining consistent quality requires additional effort

i ntelligence i nnovation i ntegrity What Can We Learn From This Picture? Quality Matters Part 2 No visiblity into bug counts on the burn down until this point. Visibility into Unit Tests - Better Unit Test Success! “If you can not measure it, you can not improve it” – Lord KelvinTip 12: “If you do not see it, you will not improve it” – Wade and Mike

i ntelligence i nnovation i ntegrity Program / Scale Diagram Initial 3x throughput increaseTip 13: Productivity doesn’t scale linearly with team growth

i ntelligence i nnovation i ntegrity Retrospective Capable of Self Management Process Respected and Practiced by Team Incremental Development Practiced Extremely Productive Team Upward Communication Minimal Product Iteration Challenges Weekly Steering Committees Plan for Iteration Continuous User Community Feedback Mitigations

i ntelligence i nnovation i ntegrity Thirteen Helpful Tips Tip 1: Take Advantage of Every Kanban Aspect Available Tip 2: Be Aware of the All the Kanban Aspects Tip 3: Visualization is essential to communicating performance Tip 4: Explicit Process Provides Team an Anchor to refer to Tip 5: Make Your Process VISIBLE!!! Apply Kanban Where Needed Tip 6: Need a Lean Advocate to Focus on Fewer Tasks Tip 7: Story Maps Provide Context and a Visual Planning Tool Tip 8: Work with the Data You Do Have Tips 9: Gain the Business Trust Customer Trust! Communicate! Feedback! Quality! Tips 10: How can you observe Quality? Valid Metrics! Survey Business Satisfaction! Tip 11: Maintaining consistent quality requires additional effort Tip 12: “If you do not see it, you will not improve it” Tip 13: Productivity doesn’t scale linearly with team growth