With over a decade of experience in product development, I've worked with numerous teams and organizations. Through these experiences, I've learned one invaluable lesson:

Culture Eats Strategy for Breakfast.

This well-known saying may seem vague at first, so let's break it down:

  • Culture: The collective behaviors and attitudes of every person in your product team, both individually and as a team.
  • Strategy: Your long-term goals and objectives for the product.

Without a team that exhibits the right behaviors, both individually and collectively, your product will struggle to meet its goals. The best Scrum ritual to address and improve team behavior is the retrospective, making it the most crucial Scrum ritual. At the end of every sprint, you have the opportunity to address and improve upon both individual and team behaviors.

Building Trust in the Retrospective

For a retrospective to be effective, there must be enough trust within the team to share thoughts openly. Here are some tips to foster that trust:

  1. Consistency: Schedule retrospectives at the end of every sprint. Regularity helps the team get used to the ritual.
  2. Set the Stage: Begin each retrospective by stating the ground rules, such as:
    • Share any thoughts freely.
    • Be sensitive to others' feelings and avoid accusatory language.
    • Ensure everyone participates.
    • Allow time for explanation and understanding of all inputs.

Tools for a Good Retrospective

Offline

  • Whiteboard and Sticky Notes: The only thing you need is a whiteboard to share the format on. And preferably make sure to have different colored sticky notes to identify who posted what.

Online

  • Retro Tools: Various online tools can facilitate retrospectives. The tool I recommend is Retro Tool.

How to Run a Retrospective

Facilitator

  • Ideally, different team members should lead each retrospective to foster ownership. However, if the team is new to this ritual, it's best to have someone experienced lead it initially.
  • The facilitator decides on the format of the retrospective. Personally, I love the format where team members have the opportunity to express appreciation for what is going well, identify areas for improvement, and suggest new ideas. An excellent example of this is the Start-Stop-Continue format. Other effective formats include:
    • Mad-Sad-Glad
    • 4Ls (Liked, Learned, Lacked, Longed for)
    • Sailboat Retrospective (Sailboat, Island, Wind, Anchor, Rocks)
    • Starfish Retrospective (Keep, Start, Stop, Less, More)

Duration

  • Allocate at least two hours for the retrospective to ensure ample time for discussion.

Schedule for a Successful Retrospective

  1. Start (10 minutes): Set the stage to stimulate trust during the retrospective.
  2. Action Points & Decisions (15 minutes): Review the action points from the previous retrospective. Discuss any that weren't completed and why. Reflect on past decisions to ensure they are still supported.
  3. Sticky Time (15 minutes): Give everyone at least 15 minutes to create sticky notes with their input. Ensure everyone participates.
  4. Share the Stickies (20 minutes): Each person shares their sticky notes on the board. This ensures everyone understands the context. Keep explanations and questions brief, avoiding discussions at this stage.
  5. Voting (10 minutes): Vote on the sticky notes. Decide how many votes each person can cast based on the retrospective format.
  6. Discussion (40–60 minutes): Discuss the most voted items (typically 3–5 per topic). Maintain a respectful and constructive tone, especially when addressing sensitive topics related to individual behaviors. The facilitator should ensure balanced participation and keep the discussion on track.
  7. Wrap-up (10 minutes): Write down all actions and decisions. Confirm with the team that they agree with the outcomes to ensure ownership.

Conclusion

Regular retrospectives can significantly improve your product team's culture. This improvement happens incrementally, so persistence is key. In the beginning, you might even discuss how to improve the retrospective itself.

Ultimately, building a team that trusts each other enough to speak openly will make achieving your strategic goals much easier. A motivated and cohesive team is the key to product success.

In this article, I've discussed the importance of the right behaviors. In a future article, I will delve deeper into what these behaviors are and how to cultivate them within your team.

Back to journal