A team retrospective is a great way for a team to reflect, inspect, adapt and improve. A common format for a team retrospective is for a facilitator to lead the team through a set of questions meant to help everyone think about the accomplishments to date as well as how to improve going forward. Everyone will individually answer the questions and then the team will walk through the replies as a group, reflect upon those, and come up with actions.
The notion of a retrospective is rooted in the belief that any team, even a well-performing one, should take time to examine itself and find ways to become as effective as possible. A retrospective is very much NOT about assigning blame or scapegoating.
Mingle can help you facilitate. In the following example, the team's set of questions are "what should we start doing?", "what should we stop doing?", "what should we continue doing?", "what should we do more of?", "what should we do less of?" and "what puzzles us?".
- Work with your team and define a set of questions
- Create a card type called "Retrospective Topics"
Create a card property called "Retrospective Categories"
- The "managed text list" property type works well
- Create a value for every question, e.g. "what should we start doing?"
- Add (or reuse) card properties that make sense for your team, e.g. "Priority" or "Status" or "Owner"
- Create a grid view that shows all the retrospective categories and topics
- Ask your team to create cards on their own before the team retrospective
- Display the grid view in the area you have the team retrospective
- Sometimes there is not enough time to cover every topic. Before the team retrospective, you can create a card property called "Votes" (number) and have your team vote by having each person increment the value. You can then sort the grid view by "Votes" to ensure the team addresses the most popular topics.
- If your team decided to assign owners to certain action items at the end of the retrospective you can update the "Retrospective Topic" cards and set the owner. This way your team can easily see who is assigned an action and what actions they are responsible for.