ScrumMaster is baking the daily bread on the daily stand-up.

During these meetings his abilities and knowledge are uncovered. There is a possibility to pick up some useful information about the Scrum Mastership during the certification or specialized trainings but only trough real experience can you gain the deeper insight into the nature of things.

Good ScrumMaster is able to turn straw for gold. There aren’t any inbound problems in his team, such as self-organizing, communication, task status…  Moreover, in such teams t here are high degree of self-discipline and responsibility.

‘To do’ of ScrumMaster before the daily meeting:

  1. Status review of reported problems, update their list or part of the whiteboard with problems
  2. Check the status of tasks’ implementation on Kanban board
  3. Check whether the tasks are updated to the remaining time of implementation
  4. Check the task flow
  5. Are the team members able to close user stories instead of opening the new ones?
  6. Identify newly added tasks that could change the commitment set at the begging of a sprint
  7. Examine the utilization of the team members to ensure their self-organizing
  8. Examine the set WIP limits
  9. In cooperation with the product owner  examines if there are any necessary changes in sprint backlog
  10. In cooperation with the ScrumMasters he verifies the status of dependent tasks and needs of other teams
  11. Check the managerial importance from organizational viewpoint
  12. Check the burn-down chart progress and identify the ambiguous values that should be discussed
  13. Meeting room preparation
  14. Tools preparation (example: Kanban table preview)
  15. And last, but not least, he has to think of creating a positive mood of the team members from the beginning of the meeting

What are you supposed to change on your Scrum Mastership tomorrow?