Real World Retrospectives
•Download as PPTX, PDF•
1 like•900 views
Slide deck from the talk Sean Yo (@seanyo) and I gave at the Agile Peer2Peer session in Kitchener, Ontario on January 28, 2014. Notes from the presentation available at https://github.com/BeardedCoder/RealWorldRetros
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Real World Retrospectives
- 1. Real World Retrospectives Sean Yo @SeanYo Matthew Campbell @BeardedCoder
- 2. Goals
- 4. Retros by the Book
- 5. Why Retro?
- 7. Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
- 8. How To Retro
- 10. Dominant Speaker
- 12. Quiet People
- 13. Negative Retro
- 14. Too Many Ideas!
- 15. New People Don’t Talk
- 16. Story Time Retro
- 17. An Awesome Retro
- 18. What’s Next?
- 19. Real World Retrospectives Notes available at: sean.ly/RWR Sean Yo @SeanYo Matthew Campbell @BeardedCoder
Editor's Notes
- Why RetroBe Able To RetroTake a concrete action to make your work better though Retros
- At the end of this presentation you will have an action to take with you to do at your workWe will be respectful, not talk when others are talking and not be jerksWe will all participate and be present in this presentationIf anyone has a question, just ask.
- Ask the question – What is a Retro?“a special meeting where the team gathers after completing an increment of work to inspect and adapt their methods and teamwork.”Methods: Process, Technical Issues, Teamwork: How we work with each other. What is our culture?Inspect-Adapt
- Textbook AnswersImprove ProductivityImprove CapabilityImprove QualityImprove CapacityBest answer: Be More AwesomeRetros are the heart of AgileSean: I think if you have iterations and retros – you’re agile. This is my Minimum defn of Agile. Everything else is decoration and needs to prove itself to be speed holes for your work and not introduce project dragIterative, Incremental Process Improvements Validate, Validate, ValidateExperience-Driven Team CultureThe team learns how to improve themselvesSupports High-Performing TeamsOpportunity to share – Cultivates an honest and open cultureBecause you get to ask the question – What did we just do and how can we do it better?
- Just do itTalkSchedule TimeFacilitatorRole descOver time - facilitator can move to the back of the room
- Retros rarely go the way they do in the booksWe have found a lot of different tools to help make RetrosBettererWe’ll take a problem-centric approach to sharing these toolsWe’ll talk about a series of problems and share tools that can help you solve these problems.
- ProblemOne person in your group talks – a lot. The result of this is that overall participation in the retro is low.SolutionsDot VotingSmall Group Work - Actionable Item
- ProblemA team lead – such as a Dev Manager – doesn’t give enough room during Retros for others to speak. Answers ALL THE THINGS: Ok – I’ll take care of that, That isn’t a problem is it? I think that? What we should do is…Solutionsleadership-free zonehave scrum master mirror feedbackTough conversation…but essential
- ProblemCrickets – no one wants to talk. Solutionspost its - get contributions from everyoneWhat to do with the post-its?Ask audienceRank from awesome-to-suckAffinity Mapstart of retro - everyone describes the sprint with one wordOnce people speak they are more likely to speak againGet everyone to put their toe in the water right awayDevice-Free Zones – working agreementNo laptopsNo phonesNo pagers
- ProblemRetros aren’t sufficiently positive – turns into group therapy complainingSolutionsWhat worked this RetroWhat do we want to keep doingWhat didn’t work – and we’ll stop doingask the question “what can we do to change this situation” 3 circles - solo effort, dependent effort, the soup
- Problem – so many ideas…can’t decide what to do…SolutionDump & SortPut all ideas on stickies (10 or so?)Take 5 minutes – and sort into more valuable and less valuableSwitch and validate Decision Matrix 2 x 2Effort vs PayoffLow Effort – Low Payoff – is it worth it?Low Effort – High Payoff – low hanging fruitHigh Effort – Low Payoff – you’re going to have a bad timeHigh Effort – High Payoff – talk to stakeholders
- Problemnew people (new hires, transfers, co-ops) don’t contribute to RetrosSenior devs have lots to saySolutionCall out all opinions are valid at beginningDirectly Ask People Post-Its, Small GroupsStorming, Forming, Norming, Performing
- Problem All talk…no walkRetros aren’t resulting in incremental change and sustained team improvementSolutionSet the expectation to leave with 1 action to test next sprintPost the action at the top of your sprint boardPlan points for doing that action during sprint planningStart the following retro with a review of that action
- An Awesome RetroList + Dot VotingWhat Worked, What didn’t Work, What to keep, What to changeLean Coffee8/4/2 time boxingScrum Master listens and intervenes to identify actions and call Thumb VotesUp, Down or sidewaysUp – YesDown – NoSideways – Agree, but with an amendmentDown and sideways explain what it would take for them to change to a yes
- Don’t Retro?Set up a retro and try it outHave a Retro?Try a new techniqueHave problems with your Retro?Try a mitigation techniqueWe want you to have an action to take with youPost Its – the universal currency of agile