Start free trial

Product Goal Team Radar

Inspired by the updates to the Scrum Guide, the Product Goal Retrospective Template helps your team use data to evaluate if the goal you have created is designed to help the team work and collaborate as productively as possible.

Setting The Stage

To start this retrospective, the facilitator establishes categories that participants will be able to vote on.
For this template, participants will be asked how much they agree with the following statements.
The proposed product goal...  

  • is clearly communicated
  • is maintained
  • is created collaboratively
  • is reflected by the backlog
  • is achievable
  • guided product value

It is important that everyone understands and agrees to the same definition for each of the labels on the radar before you begin.

Gathering Data

Each team member can then add their responses to the spokes on the radar. For each spoke, a team member will indicate (on a scale of 1-5, where 1 is the lowest rating and 5 is the highest) how they feel about the idea or issue on that spoke of the radar.

When conducting a Team Radar retrospective, it is important to choose your tools wisely. Flip charts and markers are okay for drawing a team radar, but an online retrospective tool like Retrium allows team members' responses to be collected anonymously and simultaneously. This prevents groupthink and regression to the mean, which can be common when responses are drawn one at a time often with your teammates watching your contribution. And unless you love spending time in meetings doing math, find a tool (we know a great one, ahem 😉) that takes care of data analysis to save the facilitator time and allow the team to focus on discussions that generate insights and action.

Exploring The Results

Once everyone has shared their feedback, the team moves on to the analysis phase to see and discuss the results.

In order to save time crunching numbers, Retrium provides easy data visualizations that analyze the group’s responses. So teams can easily analyze multiple response values, including

  • Average
  • Median
  • Range
  • Standard Deviation
  • Outliers
  • Histogram
  • Individual Responses

Leading The Discussion

Once everyone has shared their feedback, the team moves on to the analysis phase to see and discuss the results. From there, the facilitator can lead a discussion on the results with questions like:

Closing The Retro

By the end of this retrospective, you will have received opinions from everyone on the team and gained valuable insight into the product goal and if any revisions need to be made now instead of halfway through the sprint.

Ready to run a Team Radar retrospective?

Get started with Retrium

Try all retrospective templates for 30 days

Start free trial

Learn more about Retrium

Get to know Retrium with a customized walk through

Schedule demo