Open ro lightningretrospectives

607 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
607
On SlideShare
0
From Embeds
0
Number of Embeds
117
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Open ro lightningretrospectives

  1. 1. Learn from Experience with Retrospectives Rachel Davies rachel@agilexp.com Sankofa bird - “go back + fetch it” What is a Retrospective? A meeting where a team looks back on a past period of work so that they can learn from their experience and apply this learning to future projects Pioneered by Norm Kerth 1
  2. 2. No time to improve?! 2
  3. 3. Groundhog Day “Without retrospectives you will find that the team keeps making the same mistakes over and over again.” Henrik Kniberg Bridge Model What happened? What to change? Past Future 3
  4. 4. Structure Flow of Conversation From “Agile Coaching” book Cloudy Thinking If team is not clear on what to do then nothing happens 4
  5. 5. Unconnected Ideas Ideas must connect to experience and translate to action. Slow Down! • People will not talk if you do not listen to them • Invite everyone to share what happened • Take time to gather the whole story • Involve each member of the team 5
  6. 6. Living in the past Look back but also take time to look forward. Forget about making lists of what went well, etc. Thinking too big! Be realistic! How much can you really take on? 6
  7. 7. Incomplete Actions Before creating any new actions, see if old actions are Done. Take time to understand why actions are not finished. Blaming Don’t waste time blaming! Take a systems view to look for improvements. 7
  8. 8. Make Time for Ideas Encourage ideas from your team Consider more than one solution! Action Plans What steps will be taken towards solving the problem? Who will check up to make sure the action is implemented? Make actions visible: – Allow time in plan – Review progress – Care if no change happens 8
  9. 9. Beware of Invisible Actions Actions from retrospective need to be visible to team and management. No owner When no one on team champions a change, it gets forgotten 9
  10. 10. Always the Same Owner One person takes on actions for the team rather than supporting team to do actions themselves. Summary of Retrospective Smells • Same set of actions come up but not done – Vague, no owner, too big • Not touching real issues • If this continues then you waste time of participants! 10
  11. 11. Experiment with your Retrospectives! • Retrospectives are about learning from experience • Experiment and adapt the format to generate new insights 11

×