Skip to content

Good – better – actions

Rate this post

Easy and simple retrospective that takes the team through three central retrospective questions.

  1. What was good?
  2. What could be better?
  3. What actions should we do?

Having answered these questions the team will have an understanding on what positive (good) and negative experiences (could be better) that they need to learn from, and what to do about it (actions).

Materials

Pros

  • Easy and requires little introduction.
  • Ensures that you remember both good and less good experiences, while maintain a focus on what actions to do for next sprint.

Cons

  • Since there is no build in system on how to follow-up on actions, it is important that the scrum master pays attention if actions are actually carried out afterwards. Consider assigning responsible people for each retrospective.
  • It is also important to notice the quality of actions. Are they vague and impossible to carry out within a sprint? A tip is to refer to S.M.A.R.T. goals: Specific, measurable, achievable, realistic, time-related.

Duration

30 minutes to 90 minutes depending on team size and needs. Remember to add extra time if the team doesn’t know a retrospective.

Preparation

Share screen or copy the image below to a place where everyone can write on it. Alternatively you can make you own columns with questions in e.g. Microsoft word.

Also prepare some way to take notes of actions that needs to be done.

Step by step

Each team member must contribute to each column with one of the three topics (good, better, actions). This can be done in one of three ways:

  1. Copy the picture to somewhere everyone can edit and add their own suggestions (e.g. Microsoft Sharepoint, Microsoft teams, Google Drive, Miro).
  2. Share your screen and ask one team member at a time, while you take notes.
  3. Have team members write notes on their own computer and send them to you. You share your screen and they explain why they wrote as they did, while you add their text to the image in correct columns.

    Examples of follow-up questions:
  4. How does this sprint differ from the sprint before?
  5. What can we do to make sure we succeed in our actions?
  6. Are we over-ambitious?
  7. What can we do to improve it?
  8. Is there anything we need to ask someone outside the team?
  9. Is there anyone outside the team that we should inform?
  10. What will you do yourself?
  11. What can I, as a scrum master, do for you?