Menu
Tomek's blog
  • Contact & About
Tomek's blog
Photo by Andrik Langfield on Unsplash

Retrospective Tool: Improv Cards

Posted on July 12, 2016November 8, 2022 by Tomek Kaczanowski

I like to start a retrospective with a warm-up exercise. Something light and even funny but at the same time aimed at helping participants to start thinking about the last sprint.

There are many exercises like this (visit the fun retrospectives or Agile retrospectives resource wiki to find some). Recently I have used the Improv Cards from Management 3.0 and I am very pleased with the result.

The idea is very simple. The people should describe the last sprint using pictures on the cards. Ideally, it should be a story, but sometimes the result will be rather a set of not really connected statements – but this is also OK.

How To Use Improv Cards During Retrospective?

Sit the people around a small table. Shuffle the cards and give each participant a few cards from the deck. Ask someone to start by putting down the first card on the table and telling his description. Then go around the table – each team member will add one of his cards and tell his part of the story. Each consecutive piece of the story should be related to the picture on the card but also somehow connected with what the predecessor said. The difficulty level gets higher with each round because some cards are definitely harder to use. People tend to keep them, and during the last round, you can expect some weird stories to emerge.

This exercise should result in a long line of cards, some interesting remarks and a lot of laughter – the associations some people makeare really surprising & funny!

improv_game

Tips on Using Improv Cards

  • Make it short – give ~20 cards in total. This means 5 cards for each of 4 participants, or 3 in case of 7 people attending, etc.
  • Make it short – one or two sentences per person is enough.
  • Make it short – keep the ball rolling. Ask the participants to answer quickly.
  • Use a small table (smaller than the one on the picture above).

The time required for the exercise: 5 minutes.

I have run it 3 times so far, and it always worked well.

If you run this exercise (or some variant of this) I will be happy to hear about your experiences!

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to email a link to a friend (Opens in new window) Email
  • Click to print (Opens in new window) Print

Like this:

Like Loading...

Related Posts

  • continuous improvement
  • retrospective
  • scrum
  • team
  • Leave a ReplyCancel reply

    Follow me on Twitter

    My Tweets

    Subscribe to Blog

    My Books

    Practical Unit Testing - JUnit Practical Unit Testing - TestNG Bad Tests, Good Tests kanban for your team 1,2,3 kanban Złe testy, dobre testy

    Tags

    4dx agile book review capacity planning conference constraints continuous improvement daily scrum decision taking discussion effectiveness review estimation experiment facilitation feedback funny getting things done goals interview kanban leadership management management 3.0 meetings notes organisational culture procrastination productivity psychological safety rant remote work retrospective scrum scrum sprint sociocracy sociocracy 3.0 team testing tips & tricks tools transparency visualization wip work in process work in progress

    There is no Planet B. Act Now!

    There is no Planet B. Act Now!
    There is no Planet B. Act Now!

    Follow me on LinkedIn

    Tomasz Kaczanowski

    Top Posts & Pages

    • Team feedback - retrospective with goReflect
      Team feedback - retrospective with goReflect
    • How to Make Your Geeky Presentation Worse
      How to Make Your Geeky Presentation Worse
    • 1 Week Sprint Hurts. But in a Valuable Way.
      1 Week Sprint Hurts. But in a Valuable Way.
    • Taking Over a Project
      Taking Over a Project
    • What Could We Learn From Developers?
      What Could We Learn From Developers?

    Categories

    • agile (32)
    • book (7)
    • event (2)
    • facilitation (2)
    • organization (11)
    • productivity (32)
    • sociocracy (10)
    • team (5)
    • testing (2)
    • tools (16)
    • Uncategorized (9)
    • varia (30)
      • remote work (2)
      • ux (2)

    No Business On A Dead Planet

    No Business On Dead Planet
    No Business On Dead Planet
    ©2025 Tomek's blog | WordPress Theme by Superb Themes
    %d