Scrum Retrospective Template

Close each sprint with the scrum team: what helped, what slowed you down and which actions go into the next sprint.

Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.

Category

Meetings & CollaborationRetrospectives & Post-Mortems

Columns

Went well → To improve → Ideas → Action items → Done

Sample cards

7

Custom fields

Votes

Request form

Creates cards in Went well

Columns and sample cards

The 5 columns of this board with its 7 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.

  1. Went well

    2
    • Pairing on the payment bug saved two daysPriority: highProcess
      Votes:
      2
    • Daily stand-up ran long most daysPriority: mediumTools
      Votes:
      5
      Checklist 0/3: Agree owner, Try for one sprint, Review at next retro
  2. To improve

    1
    • Story “Bulk export” was too big to finishProcess
      Votes:
      8
  3. Ideas

    2
    • Try WIP limit of 3 in code reviewPriority: lowCustomerProcess
      Votes:
      3
    • CI pipeline is slow (18 min)Priority: urgentTools
      Votes:
      6
      Checklist 2/3: Agree owner, Try for one sprint, Review at next retro
  4. Action items

    1
    • Action: split stories over 8 pointsPriority: mediumProcess
      Votes:
      1
  5. Done

    1 · done stage
    • Action: fix flaky e2e testsTeam
      Votes:
      4

Labels

Process, Tools, Team, Customer

Custom fields

Votes (Number, on card)

Request form: Add a retro note · Scrum Retrospective

Tell us what you need; it lands on the “Went well” column of this board. Asks for Title, Description; each submission becomes a card in Went well.

Scrum Retrospective Template: questions

Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.

Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.

Related templates