Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Story Points: Gaining understanding through games
Similaire à Story Points: Gaining understanding through games (20)
Dernier
Dernier (20)
Story Points: Gaining understanding through games
- 1. Story Points Gaining Understanding Through Games! Raechel Mansfield – Iteration Manager, Suncorp.
- 2. Understanding Story Points The Problem: Getting the team to understand the value of story points How it can be applied to their work Common Misconceptions: It’s a measure of time Everyone in the team has a different understanding of it Only thinks of their effort involved, not the whole team
- 3. Understanding Story Points What is it then? An estimation of the effort involved in getting the story card from “Ready” to “Done” Can be used with T-Shirt sizing or Fibonacci (and other forms!) Relative estimation can be used to provide input from the whole team to gain a shared understanding of the effort involved Sometimes people still don’t get it! How else can we approach this topic?
- 4. Throw the cat! http://tastycupcakes.org/2016/05/throw-the-cat-and-other-objects/ What you need: 30 minutes – 60 minutes (5 mins set up, 15 mins activity, 10 mins reflect) Whiteboard, pens, list of 10 objects How to play: If possible, split up into 2 teams – 1 uses Fibonacci, the other T-Shirts Set the scene: estimate the effort it would take to throw these objects if you were standing 10m from the wall Some objects will require assumptions – does a bat mean an animal or a cricket bat? Ask these questions during the exercise – does it change their estimation? Optional: After the first round of estimation is done, ask the team to use relative estimation – are the results different?
- 5. Lessons Learned Always timebox the activity, there might be some passionate debating going on! Always leave time at the end of the game to seek feedback, what the lessons learned are – how this can be applied to future estimation sessions
- 6. Estimation and Planning Sessions Common problems: Not the whole team is engaged When one person voices an opinion (lead developer/tech lead), everyone listens to them as they are seen to have the “most” knowledge Quiet people How do we address this?
- 7. Planning Poker https://dzone.com/articles/introduction-planning-poker Made popular through Mike Cohn’s book for “Agile Estimating and Planning” What you need: Set of cards per person in the team (use the right scale!) Online - https://www.planitpoker.com How to play: Bring up a card from backlog to discuss Each person in the teams puts forward their estimate When everyone has given their estimate, compare amongst the team If there are similar answers, assign the estimate and move on If there are big differences, discuss and re-estimate. Is there a problem with the scope, information or value of the card? Is it ready for estimation?
- 8. Lessons Learned Whole team gets their say No more dominating opinions from leads (hopefully!) Stops the influencing of opinions Shared understanding of the effort involved Make sure you timebox – use a phone timer if needed
- 9. Other games Work breakdown/sprint planning Elephant Carpaccio - http://alistair.cockburn.us/Elephant+Carpaccio+exercise Scrumdoku - http://www.codeandcompost.com/post/scrumdoku!
- 10. Thanks for listening! Linkedin: www.linkedin.com/in/raechel-mansfield Email: raechel@live.com.au