Retree

Retro template

Rose, Thorn, Bud

3 lanes that separate what went well from what hurt and from the early ideas worth a push.

Start a Rose, Thorn, Bud retroAll templates

Rose

What bloomed?

  • Pairing shipped the checkout refactor in 3 days
  • The migration smoke test caught the broken index

Thorn

What hurt?

  • Release sat 2 days on a staging restore
  • The payments pull request was 900 lines

Bud

What has potential?

  • The flaky-test dashboard is half built
  • Somebody drafted a one-page RFC template
  • 3 lanesPrefilled the moment you start.
  • Writing timer 10 minSuggested for the preparation stage.
  • Best forTeams that keep hitting the same problem every sprint.
  • OriginComes out of the design thinking community, per the Open Practice Library.

How it runs

  1. Preparation

    Ask for a rose and a thorn each, then buds.

  2. Grouping

    Drop each bud onto the thorn it would fix.

  3. Voting

    Spend votes on thorns and buds, since a rose needs no decision.

  4. Discussion

    For each thorn, ask which bud is the answer.

  5. Finished

    Carry the top roses into planning so they get scheduled again.

Column by column

  • Rose

    What bloomed?

    Things that clearly worked and that you would do again. Name the practice and what it produced.

    • Pairing shipped the checkout refactor in 3 days
    • The migration smoke test caught the broken index

  • Thorn

    What hurt?

    Things that cost the team time, quality or patience. Write what happened and what it cost.

    • Release sat 2 days on a staging restore
    • The payments pull request was 900 lines

  • Bud

    What has potential?

    Early things that could grow with a push: a prototype, a draft or a habit one person started.

    • The flaky-test dashboard is half built
    • Somebody drafted a one-page RFC template

Best for

  • Teams that keep hitting the same problem every sprint.
  • Sprints where people have ideas that never reach the board.
  • Quarter and project reviews where potential is the useful question.
  • Retros right after a launch, with wins and half-done work.

Pick another template when

Tips

  • Name the bud, not the wish: try the RFC template on the search migration.
  • Keep anonymous cards on for the first runs. Thorns are where people hold back.
  • If the bud lane stays empty, give the team 2 quiet minutes for buds.

Questions

  • How is a bud different from a thorn?

    A thorn already happened and cost something. A bud has not happened yet and needs a push.

  • Is Rose Bud Thorn the same board?

    Yes, the same 3 prompts in a different order.

  • How long does this retro take?

    About 45 minutes for a team of 5 to 8.

  • Is this template free on Retree?

    Yes. Every template is free and needs no account.

Related templates