The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Retrospective using Appreciative Inquiry

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Simon Baker

Posts: 1022
Nickname: sjb140470
Registered: Jan, 2006

Simon Baker is an independent consultant, agile coach and scrum master
Retrospective using Appreciative Inquiry Posted: Dec 15, 2007 3:24 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Simon Baker.
Original Post: Retrospective using Appreciative Inquiry
Feed Title: Agile In Action
Feed URL: http://feeds.feedburner.com/AgileInAction
Feed Description: Energized Work's blog.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Simon Baker
Latest Posts From Agile In Action

Advertisement
The iteration after looping the loop has been the best yet. Everyone enjoyed it immensely. The team were buzzing and the Product Owner, Product Sponsor and Customer were ecstatic. I really wanted to tap into the positivity and leverage the energy to consolidate our gains in teamwork so I decided to facilitate an appreciative retrospective.

I introduced the retrospective by stating the following affirmative goal:
During this retrospective, we'll find ways to amplify our strengths in process and teamwork.
Here's the agenda:

1. Prime Directive

2. Check-in (5 min)

To get each person talking, ask every person to check-in by showing their appreciation for someone else on the team. They should say something like:
I would like to thank so and so for doing x.
3. Brainstorming (5 min)

Gather data by asking the team to brainstorm enjoyable events, team strengths, and successes. Have them write each one on a colour-coded post-it note.

4. Futurespective brainstorming (10 min)

To begin generating insights ask the team the following question:
Imagine we could time travel to the end of the next iteration/release. When we arrive there and converse with our future selves, we hear that it was the most productive, most satisfying effort we've ever worked on. What do you see and hear in that future time?
Have them write on a different colour post-it notes.

5. Affinity mapping (15 min)

Ask the team to group related post-it notes and assign each group a name.

6. Dot voting (5 min)

Tell the team to examine the groups again and to think about the things they identified in the future, and then ask:
Building on our successes to date and given our team strengths what do we really want to sustain?
When they've taken a minute to think ask them to dot-vote to identify what (group) they want to sustain going forward.

7. Identify the take-away actions (20 min)

Now the team needs to decide what to do. Ask the question:
What actions should we take to amplify our strengths in process and teamwork that will help us build towards the successes we have foreseen?
Facilitate a discussion to identify one or two actions, note them on index cards and take them into the next iteration's planning game.

The format above worked well. It generated the following actions to carry forward:
  • Strive for slices
  • Ask for help and offer help to others
  • Pair promiscuously
There was lots fun and smiling faces, it relaxed everyone and put them in a positive frame of mind, which helped the planning game (that follows our retrospective) go more smoothly.

Tags: ,

Read: Retrospective using Appreciative Inquiry

Topic: Ruby, Rails, CSS, Tools, HTML Previous Topic   Next Topic Topic: A-Rod stays with NY

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use