How To Run Retrospective

How To Run Retrospective 

• Opening
• Set the stage
• Nothing kills team morale quite like having the same old junk come up over and over again and doing nothing to fix it
• Rule of Engagement
• To air out feelings, to talk about things that aren’t working, to come up with some things team can try.
• This is about actions and outcomes , not about specific people. 
• Embrace an improvement mindset, away from blame. 
• Talk to each other. Listen to team. Take actions to make changes.
• Backup
• Airing of grievance 
• https://www.youtube.com/watch?v=3CQ1MbRsA2M
• Backup
• https://www.youtube.com/watch?v=WOsYl7GRfuU
• https://www.youtube.com/watch?v=1l8Eag9CAFk
• https://www.youtube.com/watch?v=bR3S690EF2U&t=17s
• https://www.youtube.com/watch?v=HX55AzGku5Y&list=PLj2Sd9DcNi4PCBL4uVw1q9cPoHceLYTrV
•  to air out feelings, to come up with some things your team can try, to talk about things that aren’t working.
• Don’t forget the purpose of retro: to mindfully iterate on process. That means that you need to actually do the action items you wrote down. Nothing kills team morale quite like having the same old junk come up over and over again and doing nothing to fix it. Take action to make changes. Listen to your team. Talk to each other. Be kind. 
• Embrace a positive spirit of continuous improvement and share whatever you think will help the team improve.
• Don't make it personal, don't take it personally.
• Encourage the team to embrace an improvement mindset, away from blame.
• Retrospective
• Key Observation
• :) Happy
• What went well?
• :( Sad
• What not well?
• :$ Wondering
• What would you do differently?
• What needs improvement? 
• what can be improved?
• what can be added/removed to the team's R&R?
• what questions do you have that we should talk about?
• Challenges
• Concerns
• Readout and talk about the post
•  If it’s important enough for someone to have written it on the board, then it’s important enough to talk about. A great retro is one where everyone’s voices are heard equally.
• The best way to keep Retrospectives productive is to continuously challenge the team to think of solutions in new and interesting ways.
• Mapping out 3M Posts with actionable groups
• Continue
• actions we should keep doing and formalize
• items the team would like to continue to emphasize but that are not yet habits. So any of the start or stop items above could go onto the continue list and stay there for a few sprints.
• Stop
• actions we should prevent or remove
• things that someone on the team thinks are inefficient or are wasting time
• Start
• actions we should start taking
• things a team member thinks the team should add to its process
• If there are things on the board in the sad column, focus hard on coming up with actions to address them. If something isn’t working, think about what you can experiment with to try to fix it. Remember, the whole reason you’re here is to iterate on your process and keep getting better, one baby step at a time. That’s only going to happen if you actually make changes.
• Digest/condense/concise to high level summary
• peer reviewing, speed dating with different group
• Panel review and alignment