Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Reducing Risk in Agile Projects

665 views

Published on

Kicking off any new software project is scary. Kicking off an agile software project can be even scarier.

However, rather than being afraid of risk, we can embrace it and learn from it. The lessons we learn will help us guide our teams to an overall stronger product.

  • Be the first to comment

Reducing Risk in Agile Projects

  1. 1. Reducing Risk in Agile Projects Jeremy Jarrell @jeremyjarrell
  2. 2. What is Risk?
  3. 3. Building the wrong thing Not working as a team Festering problems
  4. 4. “This project is too risky for agile.”
  5. 5. Frequent demos to the customer Daily stand ups Regular retrospectives
  6. 6. Iteration Project
  7. 7. Project Risk.
  8. 8. Features Deadline Team
  9. 9. Features Deadline
  10. 10. Iteration Risk.
  11. 11. What could happen? How likely is it?
  12. 12. P×I=E
  13. 13. P×I=E.Mmm,
  14. 14. As a customer, I want to review my transactions, so I can see where I’m spending my money. There’s too many transactions to pull quickly. Some transactions are delayed.
  15. 15. Some transactions are delayed. Probability = 3 Impact = 1 Exposure = Probability × Impact= 3
  16. 16. There’s too many transactions to pull quickly. Probability = 2 Impact = 3 Exposure = Probability × Impact= 6
  17. 17. There’s too many transactions to pull quickly. Invest time in performance tuning. Pre-aggregate the transactions.
  18. 18. As a customer, I want to view how my current spending compare against my budget, so I can see how I’m pacing for the month. The graph doesn’t work in IE6. The ‘UI Guy’ gets sick mid-sprint.
  19. 19. The graph doesn’t work in IE6. Probability = 3 Impact = 1 Exposure = 3
  20. 20. The ‘UI Guy’ gets sick mid-sprint. Probability = 3 Impact = 3 Exposure = 9
  21. 21. The ‘UI Guy’ gets sick mid-sprint. Pair with another developer. Peer code reviews.
  22. 22. P×I=E
  23. 23. What’s next?
  24. 24. Tackle high risk stories first Beware of stories with many risks Look for patterns

×