MindMap Gallery Techniques for an Effective Retrospective
This is a mind map talking about Techniques for an Effective Retrospective. You can create a mind map like this effortlessly.
Edited at 2020-09-28 13:54:39Techniques for an Effective Retrospective
Tips
Plan out how much time you'll spend in each step (15)
Find ways to follow up on action items
Achievable actions and owners for each action
The Top 4 Ways To Followup On Agile Retrospectives
Rotate facilitator role
Get someone outside the team to facilitate
Start each retro by reviewing the actions from previous retro
Mix up locations
Use a room without a table
Throw away everything from retro except actions
focus on outcomes, not problems
This Mind Map
http://thesoftwaregardener.com/links/retrospectiveTechniques
Back Side of Handout
http://thesoftwaregardener.com/links/retrospectiveTechniques2
Decide what to do
identify highest priority items to work on
identify actionable items theteam will accomplish
Dot Voting
Everyone gets (X) votes and puts adot on each item
top 1 or 2 items will be the focus ofthe action items
Brainwriting
5 min writing ideas
pass ideas to the left
5 minutes adding to those ideas
repeat
Speed Dating
Put measurable goals on thoseitems so they can be completed
How do we know we are doing itright, or successfully?
Actionable!
Never accept "just do it from now on"
Nor "we'll do it better"
Generate Insights
Brainstorming to identify areas ofimprovement for the team
Continuing to do what is successful
Changing current processes for more valuable outcomes
Add processes or techniques to lead to effectivechange accomplishing team and project goals
Tell and Cluster
Starfish
Start, Stop, Do More, Do Less, and Keep
Lots of Variations
Small Starfish
Keep, More Of, Less Of / Stop
4Ls liked, learned, lacked, longed for
KALM Keep, Add, More, Less
PMI Plus, Minus, Interesting
Open The Box
Remove from box, add to box, recycle in box
Thumbs up, down, new ideas and recognition
Speed Car Abyss
4 categories to writes notes about
Car Engine
What has been pushing us forward,making us fast
Car Parachute
What has been slowing us down
Abyss
What are the dangers ahead
What could take us down this path
Bridge
What could we build to overcome the abyss
Car engine, Car Parachute, Abyss, Bridge
6 thinking hats
Gather Data
create a shared picture of
what happened during the sprint
where the team feels they are onoverall goals and success
Happiness radar
given context have each memberrate their happiness level
Peaks and Valleys Timeline
Each team member draws happy/unhappytimeline over the last itteration
Feelings Gifs
Pick a gif that represents how they felt about the sprint
Explain why
Pillars of Agile Spiderweb
Big Hitter Moments
Acknowledge and reflect the good parts
Set the Stage
get the team ready to engage
This last sprint we accomplished 'X' over 2 weeks. We had 3story peer reviews all at the end. You guys dealt with some bigpager calls and helped add stories to prevent future calls
Now we want to reflect on our successes andwhat we want to work on moving forward.
Prime Directive
‘Regardless of what we discover, we understand and truly believethat everyone did the best job he or she could, given what wasknown at the time, his or her skills and abilities, the resourcesavailable, and the situation at hand.’
Norm Kerth
But first....
warm up activity(ies)
energizers
invigorate participants and make them feel more engaged
Untangle yourselves
everyone grabs each others hands and untangles
Visual Telephone
Write a sentence, pass to right, draw picture,pass to right, write sentence of the picture
Move around the room
This is the time for team building activities
Retrospective Definition
Meeting held by the team to reflect on their process, both the positives and theroom for improvement, to make actionable commitments toward improvement
"Without pursuing improvement as retrospectives require, true agility is simply not achievable."
"Most important part of agile."
It's the key that makes "agile" different and work in so many environments
Continuous improvement.
Kaizen
Entire Team
Development Team, Scrum Master, Product Owner
Close the Retrospective
Reflect on the retrospective and how to improve it
Appreciate accomplishments
The team
Individual interactions
Creative ideas
Stop leaving the retro with a bad taste in everyone's mouth!