How to Keep Going Fast - Agile Velocity - Product Camp Austin

Download How to Keep Going Fast - Agile Velocity - Product Camp Austin

Post on 22-Jan-2015

241 views

Category:

Technology

1 download

Embed Size (px)

DESCRIPTION

Features often get delivered quickly on new software projects and slow to an exponentially slower pace over time. Teams are usually on their own to discover, implement, and even get buy-in for improving the technical capability to deliver. In this session we'll discuss how technical debt accrues and impacts the flow of features over time as well as how Product Owners can encourage and support teams to improve. We will run a simulation of a software project that demonstrates the impact of employing technical practices and addressing other technical debt.

TRANSCRIPT

<ul><li> 1. As you come in, find someone in the room and discuss what you know about Technical Debt </li></ul> <p> 2. HOW TO KEEP YOUR PRODUCT DEVELOPMENT TEAMS GOING FAST Product Camp Austin 11 3. Wed prefer a fast, steady stream of new features 4. But sometimes it feels more like this 5. Long Delivery Times Mounting Defects Rising Development Costs Poor Customer Responsiveness Late Deliveries Frustrated and Poor Performing Teams 6. Intentional Debt Temporary Code Business Pressure Delayed Testing Other Conscious Tradeoffs 7. Unintentional Debt Poor Code or Design Business Pressure Poor Practices Inflexible Software Lack of understanding Poor design/architecture Unintended Complexity Poor design 8. A Vicious Cycle Time Pressure Poorly Implemented Features Late Delivery 9. Continuous Integration 10. Test (and other) Automation 11. Refactoring - would you trust delivery of your products over this road? 12. Peer Review 13. http://jimhighsmith.com/the-financial-implications-of-technical-debt/ Jim Highsmiths Technical Debt Graph Rewrite! 14. Lets do an exercise to understand the concept further. Form into Teams of at least 4 people. 15. Feature Cost: 15 Feature Cost: 10 Feature Cost: 5 Technical Debt Cost 15 Impact -10 Technical Debt Cost 15 Impact -10 Technical Debt Cost 10 Impact -5 Technical Debt Cost 5 Impact -5 Technical Debt Cost 5 Impact -5 Iteration Card Setup your board as follows 16. Feature Cost: 15 Feature Cost: 10 Feature Cost: 5 Technical Debt Cost 15 Impact -10 Technical Debt Cost 15 Impact -10 Technical Debt Cost 10 Impact -5 Technical Debt Cost 5 Impact -5 Technical Debt Cost 5 Impact -5 Iteration Card Add up the total impact of all technical debt items -35 17. 0" 10" 20" 30" 40" 50" 60" 70" Itera/ on"1" Itera/ on"2" Itera/ on"3" Itera/ on"4" Itera/ on"5" Theori/ cal"Capacity" Technical"Debt"Impact" -35 25 X 18. 0" 10" 20" 30" 40" 50" 60" 70" Itera/ on"1" Itera/ on"2" Itera/ on"3" Itera/ on"4" Itera/ on"5" Theori/ cal"Capacity" Technical"Debt"Impact" 19. Feature Cost: 10 Feature Cost: 15 Feature Cost: 10 Technical Debt Cost 15 Impact -10 Technical Debt Cost 15 Impact -10 Technical Debt Cost 10 Impact -5 Technical Debt Cost 5 Impact -5 Technical Debt Cost 5 Impact -5 Iteration Card You have 25 Points to Spend Select the cards you want to spend your points on. No partially done work. Feature Cost: 5 Feature Cost: 5 20. 0" 10" 20" 30" 40" 50" 60" 70" Itera/ on"1" Itera/ on"2" Itera/ on"3" Itera/ on"4" Itera/ on"5" Theori/ cal"Capacity" Technical"Debt"Impact" -35 25 10 15 15 X 21. The goal is to complete as many feature points at the end of 5 iterations. Go! 22. The goal is to complete as many feature points at the end of 5 iterations. Stop! 23. Theoretical Capacity Technical Debt Productivity Time 24. In order to go fast we need a focus on Craftsmanship 25. Capture your debt 26. Visualize and estimate 27. Need to invest time, team needs slack 28. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 29. Discuss how you could apply theses concepts to help your teams go fast. </p>