SCRUM IN PRACTICE“Retrospective, Impediments List, A3 andVelocity: how we aggressively get better”
Caveat: Business ValueTo be honest, a Scrum team can usually make thebiggest improvement by doing Business ValueEngineerin...
Not well enough yet... We need: Better Retrospectives Better Impediment Lists Better Business Case for removing impediment...
We need...Three things (in general):A more aggressive attitude. I call it the Michael Phelpsattitude: Even though I have b...
Questions or CommentsI would like, and you all need, questions and commentsaround:Why haven’t we done this already?How do ...
Why aren’t Retrospectivesbetter?Too many “pluses and deltas”More focus on removing impedimentsMake progress visible (veloc...
Velocity Definition: Story points of stories that the Team gets to ‘done’ in the Sprint. A decent metric of productivity A...
Better impediment lists Make the list public All contribute to prioritizing Rank mainly by: what is slowing the team down ...
Removal requires effort,money, etc. Removing larger impediments requires approval We must get management involved Lean’s ‘...
A3We strongly recommend an A3 format (to getmanagement approval)We like the A3 “approach” or methodYou must make the case ...
Velocity Use an X% velocity improvement to justify the change Show later that you were conservative (and right). Build tru...
Virtuous CombinationPublic impediment listVelocityUseful retrospectiveAggressive identification of ‘best’ impedimentA3Mana...
So, can we take action?What more do you need to double your velocity in 6months?
The EndHope this helps you!Please feel free to contact me atjhlittle@kittyhawkconsulting.comWe provide agile courses (see ...
Upcoming SlideShare
Loading in …5
×

Getting better (Rigor in improving velocity)

1,345 views

Published on

As a coach, we see implementations of Scrum that could be improved, so that velocity increases (and fun increases) without anyone working longer hours. (And not with more stress either.)

Published in: Business, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,345
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Getting better (Rigor in improving velocity)

    1. 1. SCRUM IN PRACTICE“Retrospective, Impediments List, A3 andVelocity: how we aggressively get better”
    2. 2. Caveat: Business ValueTo be honest, a Scrum team can usually make thebiggest improvement by doing Business ValueEngineering better. This means: giving them exactly what they want (when they get it) and doing less (eg, per release).This talk is NOT about Business Value Engineering.This talk is about increasing velocity: getting more workdone in a Sprint (but not by working longer hours).
    3. 3. Not well enough yet... We need: Better Retrospectives Better Impediment Lists Better Business Case for removing impediments (A3) Better use of velocity (eg, to make the business case)
    4. 4. We need...Three things (in general):A more aggressive attitude. I call it the Michael Phelpsattitude: Even though I have broken the world record inthis event several times, I can still get better.A better sense of how all the Scrum values, principlesand practices support each other in getting better.It’s NOT about working more hours.
    5. 5. Questions or CommentsI would like, and you all need, questions and commentsaround:Why haven’t we done this already?How do we do it starting tomorrow?Send the questions and comments to Tom and James.Starting now. I will try to address them some for 15mins.
    6. 6. Why aren’t Retrospectivesbetter?Too many “pluses and deltas”More focus on removing impedimentsMake progress visible (velocity)Make a better business caseCreate a better action planThe team must aggressively identify improvements
    7. 7. Velocity Definition: Story points of stories that the Team gets to ‘done’ in the Sprint. A decent metric of productivity A way to quantify improvements, beforehand and to measure afterward And, a way to protect the team!
    8. 8. Better impediment lists Make the list public All contribute to prioritizing Rank mainly by: what is slowing the team down the most Use cost-benefit analysis Get more creative about impediments (need a challenge)
    9. 9. Removal requires effort,money, etc. Removing larger impediments requires approval We must get management involved Lean’s ‘A3’ format/approach is a well-known method for doing kaizen with management. A standard A3 format: Problem, Solution, Benefits, Costs, Next steps, Measurements
    10. 10. A3We strongly recommend an A3 format (to getmanagement approval)We like the A3 “approach” or methodYou must make the case in personYou must measure afterward
    11. 11. Velocity Use an X% velocity improvement to justify the change Show later that you were conservative (and right). Build trust. Use velocity as a measure over history of changes, improvements. Motivates the team. Allow us to see when we (occasionally) make mistakes (bad ‘improvements’)
    12. 12. Virtuous CombinationPublic impediment listVelocityUseful retrospectiveAggressive identification of ‘best’ impedimentA3Management support via the Impediment RemovalTeam (IRT)
    13. 13. So, can we take action?What more do you need to double your velocity in 6months?
    14. 14. The EndHope this helps you!Please feel free to contact me atjhlittle@kittyhawkconsulting.comWe provide agile courses (see LeanAgileTraining.com),coaching, and consulting.

    ×