Run An Effective Agile Retrospective

Set up an agile retrospective with ease and invite your team by link or password. Each person in your team can now add their ideas honestly, free from edit wars and group think.

Everyone can instantly see the results which you can now use to facilitate conversation, capture comments and vote for key actions going forward.

Want more? Choose between anonymous and collaborative settings for a different experience. Change your headings to suit your own style.  Each agile retrospective template can be customised to satisfy the savvy scrum master.

The result? A visually weighted agile retrospective with improved insight so you know exactly where to go  based on the input of each individual and the views of the group.

A Quick Refresher

An Agile Retrospective is a short but frequently held team meeting which allows you to get insight, feedback and lessons learnt during the life cycle of your project.

This leads to improved team communications, informing everyone of what the current challenges and goals of people in the group are and to easily decide on what actions need to happen going forward.   This focuses on 4 key questions.

  • What went well? – What were your proud of, pleased with, or produced good outcomes?
  • What could have gone better? – What went wrong, or what areas do you see for improvement?
  • What do we want to try next? – What innovative ideas or alternative approaches would you like to try?
  • What puzzles us? – What unanswered questions do you still have?

Using your Agile Retrospective Template

Allow ~20-30 minutes

  • Step 1 – Customise your GroupMap Agile Retrospective template with the name of your project. The default setting allows for individual brainstorming, but you can change this to be collaborative. (Where ideas are seen as you go.) You can also add instructions or change headings.
  • Step 2 – Invite  your team in by password, link or email via laptop, PC, Mac or tablet. Each team member can now respond to each heading.
  • Step 3 – Use the review stage to debrief the group, capturing comments as needed. Note that the map creator can also block or pin ideas. Blocking ideas for future stages is useful to remove duplicates.
  • Step 4 – Use the Voting stage to ask the team to allocate dot votes ( you can set the number of votes) against ideas they think are important for the next phase going forward. You can choose between single or multiple dot votes per idea.
  • Step 5 -The results now show the combined results and tallied votes. Choose to display the results weighted by votes to highlight the key action points going forward. Print off a PDF or export as needed.

Think better together with GroupMap