Scrum is a great methodology and there is a great guide to scrum available. This guide should be read by every scrum master and product owner at least once a year. The guide is available at:

However – besides the general scrum knowledge and guide, as organizer (scrum master) of the scrum meetings, it’s useful to have a template or an agenda for the meetings that can be used in the outlook appointment (or others). Please find below some simple templates.

Daily Scrum/Daily Standup

  • What have I done since the last scrum meeting (yesterday)?
  • What will I do till the next meeting (tomorrow)?
  • Are there any impediments (that prevent the stories getting done today)?
  • Goal: Everyone is aware whats happening, impediments are clear and written down, new backlog items are created

more detailed daily scrum meeting template

Estimation meeting

  • Product owner describes the backlog items
  • Team gets information about the backlog items
  • Team estimates the backlog items…
  • …till the time is running out or the whole backlog is estimated
  • Goal: Team has a better understanding of the backlog items, splitted them into smaller ones and estimated them, open questions are noted

more detailed estimation meeting template

Sprint planning 1

  • Check capacity, absences, vacations … (should be prepared before the meeting!)
  • Product owner presents his product vision to the team
  • Team gets all information about the backlog items that they need
    • Not estimated backlog items will be estimated
  • Team estimates what can be done in that sprint and defines the sprint goal with the product owner
  • Items will be selected and team commits to the sprint goal
  • Goal: The next sprint is planned, vision/goal is clear and the team knows what to do

more detailed sprint planning 1 template

Sprint planning 2

  • Tasks will be created by the members (and estimated)
    • Consider: Documentation, Deployment, Coding, Testing, Code Review, learning phase (new technologies, …), Testsystems, …
  • Discuss how to implement the tasks (architecture etc.)
  • Split big tasks into smaller ones
  • Commitment to the sprint goal
  • Goal: Team knows how to implement the backlog items, how to solve the issues, …

more detailed sprint planning 2 template

Sprint review

  • Product owner opens the meeting and remembers the team of the sprint goal
  • Team presents the finalized backlog items (on a real system – no PowerPoint, screenshots etc.)
  • Product owner and end users are allowed to test the functionality on their own
  • Create new backlog items when:
    • changes are required for a feature
    • new ideas come up
    • bugs are identified
  • Goal: see a working solution, share the knowledge, check the backlog items (if it is what was expected), create new backlog items

more detailed sprint review template

Sprint retrospective

  • What went well in this sprint?
  • What was bad in this sprint?
  • Are there any ideas? (for the next sprint, improvements, …)
  • What happened in this sprint that could be improved?
  • Goal: find improvements, identify team’s strengths and weaknesses, collect ideas

more detailed sprint retrospective template