…in various ways<br />Retrospective<br />©ScrumDesk, 2011<br />
RetrospectARE<br />…take a look back at events that already taken place<br />
Maybe you heard that<br />“<br />“<br />Ohhh no, another survey…<br />This is going to take forever.<br />Let’s make it sh...
How is it different?<br />Not a survey<br />Team activity<br />Ask and check<br />
Why is retrospective necessary?<br />Opportunity to identify needs from inside<br />Catalysts for change                  ...
Who is in the retrospective?<br />For all team members<br />Everyone is equal<br />Facilitated by Scrum Master<br />Produc...
When?<br />
We used to do<br />Good | Better | Ideas<br />Voting<br />Next steps<br />
There are better approaches<br />... how to identify problems according the current situation<br />
Set stage<br />Gather data<br />Generate insights<br />Retrospective activities<br />1<br />2<br />3<br />4<br />Decide wh...
Set stage<br />Retrospective activities<br />1<br />
Check-In<br /> 5-10 min<br />Iteration<br />Set the stage<br />Help people put aside other concerns and focus on the retr...
Focus On/Off<br /> 8-12 min<br />Communication<br />Working agreement<br />Set the stage<br />Help establish a mind-set f...
Explorer, Shopper, Vacationer, Prisoner<br /> 10-15 min<br />Collaboration<br />Attitude<br />Set the stage<br />Focus pe...
Working agreement<br /> 10-30 min<br />Collaboration<br />Set the stage<br />Establish a set of behaviors that will suppo...
Set stage<br />Retrospective activities<br />1<br />
Set stage<br />Summary<br />1<br />
Credentials<br />Agile Retrospective Wiki<br />Agile Retrospectives: Making Good Teams Great, Esther Derby, Diana Larsen<b...
Upcoming SlideShare
Loading in...5
×

Agile Retrospective - part I

7,581

Published on

Retrospective is probably the most important ceremony as it helps to improve the team.

There are great sources how to do retrospective.

Published in: Business
1 Comment
10 Likes
Statistics
Notes
No Downloads
Views
Total Views
7,581
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
4
Comments
1
Likes
10
Embeds 0
No embeds

No notes for slide
  • Start with a simple welcome and appreciation for people’s investment of time. Restate the purpose of the retrospective and the goal for the session. Remind people of how long you’ll meetSince the point of the retrospective is to help the group think and learn together, you need everyone’s participation. Ask everyone in the room to speak.Outline approach
  • You can use many different metaphors with this question - type of animal, hardware, flavor. Be careful not to use a metaphor that will seem frivolous or silly to your team.I pass answer is okGather answers – words and make them visible (happy, angry, sad,….)
  • Group of 4 ppl Leader describes productive and non-productive communication patterns Then all discuss what they mean for the retrospectiveDraw attention to the Focus On/Focus Off posterBriefly read through it.Form small groups, with no more than four people per group. Ask each group to take one pair of words to define and describe. If there are more than four pairs/groups, it’s OK if more than one group has the same pair of words.Ask each group to discuss what their two words mean and what behaviors they represent. Have them describe the impact each would have on the team and the retrospective.Each group reports on their discussion to the whole team.Ask people whether they are willing to stay in the left column (Focus On descriptions).Many teams carry forward the Focus On behaviors as working agreements to improve dayto-day communication.
  • Explorers - eager for new ideasShoppers - happy to go home with 1 new ideaVacationers - not interested in, happy be away of daily jobPrisoners - fell they are forced to attendAnonymouslyLeaders collect data and draw histogramIf the majority of the people in the room are Vacationers, that’s interesting information about how people feel about their work environment. You may want turn on a dime and make that the major topic of discussion for the retrospective!If you do have Prisoners in the room, suggest that they can choose how they will spend their time... they can engage or not. Prisoners can stay, but leave on a break if they wish
  • Set Standard – Select 3 to 7 agreementsEstablish that team members are responsible for monitoring their interactions.Team members work together to generate ideas for effective behaviors at work Choose 5 – 7 agreements to guide team interactions or processes.Each group reports their most important proposed working agreement.When all the unique proposed working agreements are collected, the retrospective leader helps the group make needed amendments and select three to seven working agreements that will set the standard for behavior during the retrospective
  • Start with a simple welcome and appreciation for people’s investment of time. Restate the purpose of the retrospective and the goal for the session. Remind people of how long you’ll meetSince the point of the retrospective is to help the group think and learn together, you need everyone’s participation. Ask everyone in the room to speak.Outline approach
  • Agile Retrospective - part I

    1. 1. …in various ways<br />Retrospective<br />©ScrumDesk, 2011<br />
    2. 2. RetrospectARE<br />…take a look back at events that already taken place<br />
    3. 3. Maybe you heard that<br />“<br />“<br />Ohhh no, another survey…<br />This is going to take forever.<br />Let’s make it short & efficient.<br />“<br />“<br />“<br />“<br />
    4. 4. How is it different?<br />Not a survey<br />Team activity<br />Ask and check<br />
    5. 5. Why is retrospective necessary?<br />Opportunity to identify needs from inside<br />Catalysts for change <br />Generate actions<br />Repeated process = continuous improvement<br />
    6. 6. Who is in the retrospective?<br />For all team members<br />Everyone is equal<br />Facilitated by Scrum Master<br />Product Owner <br />is not necessary<br />Management should <br />not attend<br />
    7. 7. When?<br />
    8. 8. We used to do<br />Good | Better | Ideas<br />Voting<br />Next steps<br />
    9. 9. There are better approaches<br />... how to identify problems according the current situation<br />
    10. 10. Set stage<br />Gather data<br />Generate insights<br />Retrospective activities<br />1<br />2<br />3<br />4<br />Decide what to do<br />5<br />Close<br />
    11. 11. Set stage<br />Retrospective activities<br />1<br />
    12. 12. Check-In<br /> 5-10 min<br />Iteration<br />Set the stage<br />Help people put aside other concerns and focus on the retrospective.<br />What people want?<br />Get all people to say one or two words and they will be like to contribute later<br />1<br />2<br />In one word, what are your hopes for this retrospective?<br />What is one thing that’s on your mind?<br />Coming into this retrospective, if you were a car, what kind of car would you be?<br />
    13. 13. Focus On/Off<br /> 8-12 min<br />Communication<br />Working agreement<br />Set the stage<br />Help establish a mind-set for productive communication<br />1<br />2<br />3<br />4<br />5<br />
    14. 14. Explorer, Shopper, Vacationer, Prisoner<br /> 10-15 min<br />Collaboration<br />Attitude<br />Set the stage<br />Focus people on the work of the retrospective. Understand people’s attitudes<br />1<br />2<br />3<br />4<br />5<br />E<br />S<br />V<br />P<br />
    15. 15. Working agreement<br /> 10-30 min<br />Collaboration<br />Set the stage<br />Establish a set of behaviors that will support the team in having productive discussion<br />1<br />2<br />3<br />4<br />5<br />> 7 agreements<br />
    16. 16. Set stage<br />Retrospective activities<br />1<br />
    17. 17. Set stage<br />Summary<br />1<br />
    18. 18. Credentials<br />Agile Retrospective Wiki<br />Agile Retrospectives: Making Good Teams Great, Esther Derby, Diana Larsen<br />

    ×