Coaching and Leading Agility: A Discussion of Agile Tuning


Published on

Are you an agile practitioner wanting to take your agility to the next level? Are you looking to gain real value from agile instead of simply more talk? Even though many are using agile methods, not all are seeing big returns from their investment. David Hussman shares his experiences and describes a short assessment that identifies both strengths and weaknesses in your use of agile methods. Creating an assessment helps you examine the processes you are using, why you are using them, and if they are providing real value. This assessment guides you through the remainder of the tutorial, helping you tune your current processes and embrace new tools—product thinking, product delivery, team building, technical excellence, program level agility, and more. Leave with an actionable coaching plan that is measurable and contextually significant to your organization. If you want to promote real agility—or lead others to do so—come ready to think, challenge, question, listen, and learn.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Coaching and Leading Agility: A Discussion of Agile Tuning

  1. 1. TJ AM Half day Tutorial 11/12/2013 8:30 AM "Coaching and Leading Agility: A Discussion of Agile Tuning" Presented by: David Hussman DevJam Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888 268 8770 904 278 0524
  2. 2. David Hussman DevJam Working with companies of all sizes worldwide, David Hussman teaches and coaches the adoption of agile methods as powerful delivery tools. Sometimes he pairs with developers and testers; other times he helps plan and create product roadmaps. David often works with leadership groups to pragmatically use agile methods to foster innovation and a competitive business advantage. Prior to working as a full-time coach, he spent years building software in the audio, biometrics, medical, financial, retail, and education sectors. David now leads DevJam, a company composed of agile collaborators. As mentors and practitioners, DevJam ( focuses on agility as a tool to help people and companies improve their software production skills.
  3. 3. 10/20/2013 Coaching and Leading Agility: A Discussion of Agile Tuning David Hussman - DevJam DevJam coaches and produce products Design Deliver Learn DevJam Tunings Vary 1
  4. 4. 10/20/2013 Today’s Session Introductions and Expectations Getting Ready Getting Productive Staying Productive What are your expectations? Getting Ready Getting Productive Staying Productive 2
  5. 5. 10/20/2013 Getting Ready Getting Productive Staying Productive Interviews and Assessments How do you work today? What do you do well? What are your challenges? What are your goals for change? What constraints can you foresee? Outcome Based Selections Challenging the value of change 3
  6. 6. 10/20/2013 Planning to Coach Suggested Changes Suggested Teams and Locations Suggested Timeframe(s) Product Thinking Discovery and Delivery How much up front? How much over time? 4
  7. 7. 10/20/2013 Discovery looks like this When are you ready … … to start building and learning? Setting the Stage 5
  8. 8. 10/20/2013 The Band and The Players The Instruments and Rehearsal Space The tools The visualizations The techniques The design spaces How ready is the team? How ready are their tools? 6
  9. 9. 10/20/2013 Getting Ready Getting Productive Staying Productive What is commonly working? What is commonly not working? Planning to Discover and Learning from Delivery 7
  10. 10. 10/20/2013 Planning to Discover and Learning from Delivery Planning to Discover When are you done? Planning to Deliver When are you ready to build? 8
  11. 11. 10/20/2013 How much planning is enough? What’s your MVP? (minimum viable planning) Planning to Discover and Learning from Delivery What are trying to accomplish? What could you change? 9
  12. 12. 10/20/2013 Does this start good discussion? Why or why not? How much testing is enough? Expected Outcome Adaptive System Working Code Where is your best investment? What does this picture tell you? What’s missing? 10
  13. 13. 10/20/2013 Do your metrics spark discussion? Release Burnup Chart 160 140 Total Points 120 100 80 60 40 20 0 1.1 1.2 1.3 2.1 2.2 2.3 3.1 3.2 3.3 4.1 4.2 4.3 5.1 5.2 5.3 Iteration (Sprint) End How do they help you learn? What questions do you need to ask? What data do you need? Do people value your retrospective? How do you know it is helpful? 11
  14. 14. 10/20/2013 What solutions did you hear? What was not addressed? Alternative Thinking Renaissance and Reformation Minimum Viable Planning 12
  15. 15. 10/20/2013 Visualization and Collaborative Learning Certainty and Uncertainty Challenging your “product arrogance” Measures and Pivots 13
  16. 16. 10/20/2013 Getting Ready Getting Productive Staying Productive What two things would you change to improve your current team’s agility? Who thought of removing something? Subtractionists promote antifragility 14
  17. 17. 10/20/2013 What is the “evidence of success?” Why iterate? Why sprint? What are the real measures? From Cycles to Flow What’s a meaningful learning cycle? What’s a meaningful product cycle? 15
  18. 18. 10/20/2013 From continuous integration … … to continuous delivery and learning Who cares? Who doesn’t? What are your integration and deploy challenges? What are your automated testing challenges? How would you sell a move to continuous delivery (or learning)? 16
  19. 19. 10/20/2013 From measuring story points … … to measuring value delivered From story templates … .. to customer journeys How often do you engage users? How often are you wrong? How well do you learn? 17
  20. 20. 10/20/2013 Parting Thoughts for Your Journey Avoiding Epistemic Arrogance “The difference between what you know and what you think you know” – Nassim Taleb Don’t miss unnamed evolutions (from) Last Millennia (to) This Millennia What’s required? How many hours? How much cost? What’s needed? How much product? How much opportunity? How big? Learning to estimate Completing work Too big? Learning from estimates Validating value delivered Building for the future Talking about code Late integration Building to adapt Talking about tests Continuous Deployment 18
  21. 21. 10/20/2013 Be an “epistemocrat” “… someone of epistemic humility, one who holds her/ his own knowledge in greatest suspicion.” Learning is the New Currency © 2013 DevJam - All rights reserved. 19