• Participants:
    • Scrum master
    • Team members
    • Optional: Product owner, other stakeholders
  • Taskboard is visible for everyone
  • Standup meeting means that everyone stands up!
  • Duration: 15 minutes


  • Starts (as every meeting) right in time
  • 15 Minutes time to clarify:
    • 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)?
  • Issues are not solved during the daily scrum – those can be discussed after the meeting
  • If someone is missing – another team member substitutes him
  • Add impediments to the impediments backlog
  • Goal: Everyone is aware whats happening, impediments are clear and written down, new backlog items are created

Additional information

  • Focus on the time frame! if there are long discussions – discuss it after the daily scrum or organize a separate meeting
  • The team does not report the scrum master!
    • it’s a discussion, not a reporting
    • members are talking to each others, not to the product owner or scrum master
  • Think about: What to do when a member is too late? (e.g. one coin into the piggy bank which will be donated. remark: going out for some drinks with that money could be  amotivation for the people to come too late)
  • Team members do the work – it’s not the scrum master who is updating tasks, burndown charts or whatever

3 Responses

  1. Harry says:

    is it compulsory Scrum master required to attend retrospective meeting

  2. Dhon Gorgonia says:

    last day of sprint, should we conduct daily stand up or just the sprint retro?

  3. Andreas Trautner says:

    It still amazes me that it is necessary to use stuff like this. After all, this is just business as usual for the supplier organization. Why on earth have the IT-organizations not long, loooong ago, like from the 70ies have clearly established ways of supplying IT??? What did you do before in the IT organization??

    It is all about understanding what is required, plan what you will do in which order, and make sure that you follow up on progress so that you can monitor if you are on the right track. Every baker in town is doing this every day.

    This is of course not project management – it is delivery management.

Comments are closed.