Rose, Bud, Thorn Retrospective

Celebrate what is flourishing, notice promising opportunities, and address the challenges standing in your team's way.

What Is a Rose, Bud, Thorn Retrospective?

Rose, Bud, Thorn is a balanced Sprint Retrospective technique. Roses are successes worth recognizing, buds are promising opportunities that could grow, and thorns are challenges that need attention.

Teams use the format when they want an optimistic but honest review. It works especially well after a release, a period of change, or a sprint containing both meaningful progress and unresolved friction. Looking at all three categories prevents problems from overshadowing achievements and keeps future possibilities visible.

Rose, Bud, Thorn Examples

Rose

Achievements and practices the team values and wants to protect.

A successful feature delivery.
Excellent teamwork across roles.
Positive customer feedback.
Improved sprint planning.
A faster deployment process.

Bud

Early ideas and opportunities with the potential to improve future work.

A new automation opportunity.
A promising architectural improvement.
A recently adopted development practice.
Expanding automated test coverage.
Cross-training opportunities.

Thorn

Obstacles and pain points the team should understand and address constructively.

Growing technical debt.
Delayed code reviews.
Unclear requirements.
Unresolved external dependencies.
Communication breakdowns.

Use specific What Went Well examples to describe roses and constructive What Didn't Go Well examples to discuss thorns without assigning blame.

How to Facilitate the Exercise

Prepare the board. Create clearly labeled Rose, Bud, and Thorn areas and review previous commitments.
Explain each category. Clarify that buds are emerging opportunities, not action items that are already guaranteed.
Encourage balanced participation. Give everyone quiet writing time before discussion starts.
Group similar responses. Combine related cards and identify themes across the three categories.
Prioritize discussion. Celebrate important roses, choose a promising bud, and address the thorn with the greatest impact.
Create action items. Select achievable improvements, assign owners, and decide when progress will be reviewed.

Follow BugNBrag's Sprint Retrospective best practices to support psychological safety and follow-through. These retrospective examples can help participants write specific cards.

Discussion Tips

Celebrate successes before moving into challenges.
Encourage constructive, specific feedback from every participant.
Give future opportunities as much attention as current problems.
Focus on processes and conditions instead of assigning blame.
End with a small number of achievable action items.

A retrospective icebreaker can establish a positive tone. Distributed groups can apply the participation guidance for remote Sprint Retrospectives.

Choosing the Right Format

Choose Rose, Bud, Thorn for a simple, forward-looking conversation. Use Start, Stop, Continue for direct process decisions, Mad, Sad, Glad for emotional impact, Sailboat for goals and risks, Starfish for finer adjustments, or the 4Ls Retrospective when learning and unmet needs deserve special attention.

Grow what works and address what gets in the way

Free. No account. No setup. Just balanced reflection and practical action.

Create Free Session