SlideShare ist ein Scribd-Unternehmen logo
1 von 11
Downloaden Sie, um offline zu lesen
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
No time to improve?!




                       2
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
Structure Flow of Conversation




                         From “Agile Coaching” book




              Cloudy Thinking




If team is not clear on what to do then nothing happens




                                                          4
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
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
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
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
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
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
Experiment with your Retrospectives!

  • Retrospectives are
    about learning from
    experience
  • Experiment and adapt
    the format to
    generate new insights




                                       11

Weitere ähnliche Inhalte

Was ist angesagt?

Kanban is not your process
Kanban is not your processKanban is not your process

Was ist angesagt? (19)

Getting Things Done - David Allen
Getting Things Done - David AllenGetting Things Done - David Allen
Getting Things Done - David Allen
 
GTD(R) Workshop
GTD(R) WorkshopGTD(R) Workshop
GTD(R) Workshop
 
Techniques for Effective Retrospectives
Techniques for Effective RetrospectivesTechniques for Effective Retrospectives
Techniques for Effective Retrospectives
 
Avoiding the 2 week waterfall
Avoiding the 2 week waterfallAvoiding the 2 week waterfall
Avoiding the 2 week waterfall
 
Getting Things Done with "Getting Things Done"
Getting Things Done with "Getting Things Done"Getting Things Done with "Getting Things Done"
Getting Things Done with "Getting Things Done"
 
Host Leaders as Good Citizens in Software Development Organisations
Host Leaders as Good Citizens in Software Development OrganisationsHost Leaders as Good Citizens in Software Development Organisations
Host Leaders as Good Citizens in Software Development Organisations
 
Group 10 getting things done by david allen summary
Group 10 getting things done by david allen summaryGroup 10 getting things done by david allen summary
Group 10 getting things done by david allen summary
 
Ian McFarland, Pivotal Labs
Ian McFarland, Pivotal LabsIan McFarland, Pivotal Labs
Ian McFarland, Pivotal Labs
 
AtlasCamp 2015: Bruce Lee and the essence of Agile
AtlasCamp 2015: Bruce Lee and the essence of AgileAtlasCamp 2015: Bruce Lee and the essence of Agile
AtlasCamp 2015: Bruce Lee and the essence of Agile
 
Getting things done - A narrative summary
Getting things done - A narrative summaryGetting things done - A narrative summary
Getting things done - A narrative summary
 
Kanban is not your process
Kanban is not your processKanban is not your process
Kanban is not your process
 
From Clutter to Clear: A Guide to Getting Things Done (Part I)
From Clutter to Clear: A Guide to Getting Things Done (Part I)From Clutter to Clear: A Guide to Getting Things Done (Part I)
From Clutter to Clear: A Guide to Getting Things Done (Part I)
 
Introduction to Getting Things Done (GTD) & Personal Productivity Ninja - The...
Introduction to Getting Things Done (GTD) & Personal Productivity Ninja - The...Introduction to Getting Things Done (GTD) & Personal Productivity Ninja - The...
Introduction to Getting Things Done (GTD) & Personal Productivity Ninja - The...
 
Your Retrospective Format Doesnt Matter
Your Retrospective Format Doesnt MatterYour Retrospective Format Doesnt Matter
Your Retrospective Format Doesnt Matter
 
003 inspired training_leadership 03
003 inspired training_leadership 03003 inspired training_leadership 03
003 inspired training_leadership 03
 
Getting Things Done (GTD) by David Allen
Getting Things Done (GTD) by David AllenGetting Things Done (GTD) by David Allen
Getting Things Done (GTD) by David Allen
 
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
Collaboration is More Than Communication – JIRA Agile - Xavier MoreraCollaboration is More Than Communication – JIRA Agile - Xavier Morera
Collaboration is More Than Communication – JIRA Agile - Xavier Morera
 
Effective Agile Teams
Effective Agile TeamsEffective Agile Teams
Effective Agile Teams
 
GTD 101 - Getting Things Done
GTD 101 - Getting Things DoneGTD 101 - Getting Things Done
GTD 101 - Getting Things Done
 

Ähnlich wie Open ro lightningretrospectives

Agilex retrospectives
Agilex retrospectivesAgilex retrospectives
Agilex retrospectives
Skills Matter
 
Process affordances-workshop
Process affordances-workshopProcess affordances-workshop
Process affordances-workshop
drewz lin
 
Final teacher guide powerpoint
Final teacher guide powerpointFinal teacher guide powerpoint
Final teacher guide powerpoint
roger8803
 
Manager 101
Manager 101Manager 101
Manager 101
OandB
 

Ähnlich wie Open ro lightningretrospectives (20)

Agilex retrospectives
Agilex retrospectivesAgilex retrospectives
Agilex retrospectives
 
Morris Midwest Customer Open House March 2013
Morris Midwest Customer Open House March 2013Morris Midwest Customer Open House March 2013
Morris Midwest Customer Open House March 2013
 
Time Management
Time ManagementTime Management
Time Management
 
Change Management
Change ManagementChange Management
Change Management
 
Process affordances-workshop
Process affordances-workshopProcess affordances-workshop
Process affordances-workshop
 
When anxiety is a good thing on projects
When anxiety is a good thing on projectsWhen anxiety is a good thing on projects
When anxiety is a good thing on projects
 
Agile Transformations, the Good, the Bad and the Ugly
Agile Transformations,  the Good, the Bad and the UglyAgile Transformations,  the Good, the Bad and the Ugly
Agile Transformations, the Good, the Bad and the Ugly
 
Identifying and Managing Waste in Complex Product Development Environments
Identifying and Managing Waste in Complex Product Development EnvironmentsIdentifying and Managing Waste in Complex Product Development Environments
Identifying and Managing Waste in Complex Product Development Environments
 
Retrospective’s retrospective (extended version)
Retrospective’s retrospective (extended version)Retrospective’s retrospective (extended version)
Retrospective’s retrospective (extended version)
 
How to scale product development when you no longer fit in one room
How to scale product development when you no longer fit in one roomHow to scale product development when you no longer fit in one room
How to scale product development when you no longer fit in one room
 
Lean thinking and the agile culture
Lean thinking and the agile cultureLean thinking and the agile culture
Lean thinking and the agile culture
 
Open ro agilecoaching
Open ro agilecoachingOpen ro agilecoaching
Open ro agilecoaching
 
Final teacher guide powerpoint
Final teacher guide powerpointFinal teacher guide powerpoint
Final teacher guide powerpoint
 
Manager 101
Manager 101Manager 101
Manager 101
 
2011 Feb25 Lewis Ieee Time Mgt
2011 Feb25 Lewis Ieee Time Mgt2011 Feb25 Lewis Ieee Time Mgt
2011 Feb25 Lewis Ieee Time Mgt
 
Designing a Process that Works for Your Team
Designing a Process that Works for Your TeamDesigning a Process that Works for Your Team
Designing a Process that Works for Your Team
 
Agile
AgileAgile
Agile
 
I don't do Agile, I AM Agile!
I don't do Agile, I AM Agile!I don't do Agile, I AM Agile!
I don't do Agile, I AM Agile!
 
Facilitating online agile retrospectives
Facilitating online agile retrospectivesFacilitating online agile retrospectives
Facilitating online agile retrospectives
 
Social Media Time Management
Social Media Time Management Social Media Time Management
Social Media Time Management
 

Mehr von OpenAgile Romania

Lessons learned in agile romania
Lessons learned in agile romaniaLessons learned in agile romania
Lessons learned in agile romania
OpenAgile Romania
 
Products andpeopleoverprocessanddogma
Products andpeopleoverprocessanddogmaProducts andpeopleoverprocessanddogma
Products andpeopleoverprocessanddogma
OpenAgile Romania
 
Agile teams as innovation teams
Agile teams as innovation teamsAgile teams as innovation teams
Agile teams as innovation teams
OpenAgile Romania
 
Daniel nicolescu agilepm-final
Daniel nicolescu agilepm-finalDaniel nicolescu agilepm-final
Daniel nicolescu agilepm-final
OpenAgile Romania
 

Mehr von OpenAgile Romania (16)

Lessons learned in agile romania
Lessons learned in agile romaniaLessons learned in agile romania
Lessons learned in agile romania
 
Products andpeopleoverprocessanddogma
Products andpeopleoverprocessanddogmaProducts andpeopleoverprocessanddogma
Products andpeopleoverprocessanddogma
 
Agile teams as innovation teams
Agile teams as innovation teamsAgile teams as innovation teams
Agile teams as innovation teams
 
Openagile
OpenagileOpenagile
Openagile
 
Tdd performance kata
Tdd performance kataTdd performance kata
Tdd performance kata
 
Functional programming
Functional programmingFunctional programming
Functional programming
 
Tdd demo
Tdd demoTdd demo
Tdd demo
 
Daniel nicolescu agilepm-final
Daniel nicolescu agilepm-finalDaniel nicolescu agilepm-final
Daniel nicolescu agilepm-final
 
Survive In Agility Islands
Survive In Agility IslandsSurvive In Agility Islands
Survive In Agility Islands
 
Agile Startup
Agile StartupAgile Startup
Agile Startup
 
Brain & Quality Software
Brain & Quality SoftwareBrain & Quality Software
Brain & Quality Software
 
Uber Vu - Scrum & Startups
Uber Vu - Scrum & StartupsUber Vu - Scrum & Startups
Uber Vu - Scrum & Startups
 
Executive Report Executive Dashboard Report Handout
Executive Report Executive Dashboard Report HandoutExecutive Report Executive Dashboard Report Handout
Executive Report Executive Dashboard Report Handout
 
Executive Dashboard Report For Agile Projects
Executive Dashboard Report For Agile ProjectsExecutive Dashboard Report For Agile Projects
Executive Dashboard Report For Agile Projects
 
The Life Of A Tester In An Agile Team
The Life Of A Tester In An Agile TeamThe Life Of A Tester In An Agile Team
The Life Of A Tester In An Agile Team
 
The Craftsman Developer In An Agile World
The Craftsman Developer In An Agile WorldThe Craftsman Developer In An Agile World
The Craftsman Developer In An Agile World
 

Open ro lightningretrospectives

  • 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. No time to improve?! 2
  • 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. Structure Flow of Conversation From “Agile Coaching” book Cloudy Thinking If team is not clear on what to do then nothing happens 4
  • 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. 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. 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. 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. 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. 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. Experiment with your Retrospectives! • Retrospectives are about learning from experience • Experiment and adapt the format to generate new insights 11