Using Powerful Questions to Overcome Scrum Retrospective Anti‑Patterns

In Scrum, the retrospective is one of the most important events, offering teams a chance to reflect and improve their collaboration. However, retrospectives are often misused, leading to several anti‑patterns. This article discusses those anti‑patterns and shows how asking powerful questions can resolve them.

Powerful Questions

Powerful questions are open‑ended, cannot be answered with a simple yes/no, and stimulate thinking and emotion. They avoid leading the respondent toward a specific solution and encourage self‑exploration. Key characteristics include:

Open‑ended format, usually starting with “what” or “how”.

Not asked merely to gather information.

Do not suggest a particular solution.

Stimulate exploration.

Concise, typically fewer than seven words.

Examples of powerful questions include:

What makes this important to you?

What will you do, and when?

What else?

What does fun mean to you?

If you could start over, what would you do differently?

What would happen if everything went as you expected?

What is blocking you?

When you successfully made a change, what worked?

How do you handle disappointment or failure?

How important is the start for you?

What is your mission?

What kind of person do you want to become?

What is important to you?

What hinders achieving this goal?

What must you do to achieve your goal?

What can remind you of this?

Retrospective Anti‑Patterns

Management Attending Retrospectives

When managers attend, the team may feel unsafe. Scrum Masters should refuse their presence to uphold the value of courage. Sample powerful questions for managers:

What does the retrospective give you?

What do you hope to achieve by attending?

Besides attending, how else can you help the team?

How can you best use your time to support the team?

How can we create an atmosphere that encourages team participation?

What change are you expecting from the retrospective?

No Follow‑Up After Retrospectives

Without tracking action items, improvements cannot be validated. Powerful follow‑up questions include:

What action items from the last retrospective need follow‑up?

What achievements have we made since the last retrospective?

Which improvements remain unfinished?

How is the progress on each discussed item?

What other options should we consider?

What successes should we celebrate?

What would we do differently this time?

Discussing Non‑Process Issues in Retrospectives

Retrospectives should focus on process, not resource or facility constraints. Prompt the team with questions such as:

What do we need to focus on today?

What do we want to achieve today?

What can we do to improve the process?

How can we create lasting impact?

What attempts have you made so far?

What goal do we want to reach with this retrospective?

How does this relate to the process?

Trying to Solve Everything at Once

Limited resources require focusing on the most important problems. Use questions like:

When and what will we do?

What obstacles stand in our way?

What is our next step?

What is most important right now?

What does postponing this mean?

What other choices do we have?

If you could solve only one thing, which would it be?

Unclear or Unexecutable Action Items

Vague action items hinder execution. Clarify with questions such as:

What is the concrete action plan?

What are the possible approaches?

Why is this important to you?

How will you know it is done?

What does this mean?

From what other perspective can we view this?

What do you really want?

How would you explain this to yourself?

By consistently applying powerful, non‑leading questions, Scrum teams can break these anti‑patterns, foster deeper insight, and continuously improve their processes.