3 Sprint Retrospectives Ideas To Build High-performing Team.

How to build successful Scrum Teams by facilitating Sprint Retrospectives in a different way than others.

Having a high-performing, well-integrated teams is important for creating successful products and organizations. You can find below my favourite Sprint Retrospective formats that can support building a strong culture of teamwork and turn group of strangers into a team.

What can you get from it? The same understanding of what makes an effective team-work; Alignment on the most important aspects of working together; Creating list of items that can help your team to work in an effective way; Sharing knowledge, examples and good practices from other companies.

Effective Team — Retrospective

The structure of the workshop consists of fours main parts:

  1. Collecting Data: Ask participants what from their perspective, previous experience are the most important factors that makes effective teams.
  2. Prioritization: Prioritize the list of factors created in the first part, so participants can choose the most important attributes.
  3. Lessons Learned: Discuss together the results and share examples from other companies and teams.
  4. Reminders: Visualise items that were created by participants and review them together regularly i.e. during every second retrospective session to see if there any areas that your team can improve on.

What would you get from it? Defining roles and responsibilities in your team; Having similar understanding of what different people expect from other roles ; Assigning specific activities to roles in your team.

Roles and Responsibility- Retrospective

The retrospective consists of 3 steps:

  1. Roles Definition: Define roles in your team i.e. Product Owner, Dev Team Member, Scrum Master.
  2. Expectations: Ask each of a team member to define what he’s expecting from people having those roles? How should they act, so the team can work in a effective way?
  3. Discussion and Agreements: Discuss each role separately and decide if particular activity should stay within the chosen bucket, should be assigned to a different role or is not needed at all in your team.

What can you get from it? Basic understanding of what team-work means, and how people interact in groups; Learning how an individual behaves in a team environment.

Number of Possible Interactions in Teams vs Team Size.

The format is mostly focused on the learning aspects, and teaching participants about different models describing interactions between team members and identifing behaviours that can have impact on others.

  1. Education: Present briefly chosen topic that is important for building high-performing teams i.e. 5 Dysfunctions of a Team; Scrum Values; Tuckman’s stages of group development; Re:work Google; Belbin Team Roles.
  2. Discussion: Ask participants to rate how their team is doing in particular areas, and where is possible room for improvement.

Building healthy teams is an ongoing activity, but especially during the forming stage when the first norms are being created, focusing on soft-aspects of collaboration is really important and can have significant impact on building strong culture of a team-work in your organizations.

My other posts related to the topic: Top 13 Tips to become great Product Owner; 5 Myths of Scrum; How to get the PSPO II?

If you enjoyed reading the article, please don’t forget to applaud it 👏.

Many Thanks!

Scrum Master | PSM III

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store