Saving Daily Scrum Meeting

The main objective of the daily scrum meeting is to synchronize team work. Each member of the team should know than the other people on the team are engaged in the tasks allocated to them. What is the benefit of such knowledge? First of all — it reduces the amount of time wasted because of not enough information transfer between team members.

By Andrew Mospan
Scrum Master of ConceptDraw Teams'.

The Scrum meeting is not intended to make decisions on problems that are related to a project. All questions demanding decision making should be a separate discussion taken outside of the scrum.

Sometimes a Scrum meeting will take on issues that are part of the normal working process of the project, or even sit outside of the project entirely. Examples of these potential productivity wasters are:

  • A few individuals drill down into the problem details and begin to resolve the issue during the meeting
  • During the scrum meeting two participants discuss yesterday's football match
  • Everybody asks the project manager “What is new?”
  • The scrum turns into a meeting where everyone is reporting results to the project manager
  • And, yes at times participants are late for the meeting.

When this happens, meetings can then take much longer than expected. They turn into a major daily meeting trying to resolve project problems. Interest in attending the meetings falls at once, the benefit of the Scrum meeting disappears quickly.

Here are a few tricks that can help to remove issues during daily scrum meeting:

Problem Decision
Meeting turns to report of team members to scrum master or manager instead of team conversation.
  • Explain that the goal of the daily scrum is only to share information to the team.
  • Scrum master should sit out of the line of sight, and not be the focus of the meeting.
Delays.
  • Establish small (symbolic) penalties for meeting delays (“Thank you for being late today. You can get us all coffee after the meeting.” Or “Please tell us your excellent excuse on why you made all of us wait for you.”)
  • Move scrum to a later time.
Discussions are prolonged.
  • Schedule no more than two minutes for each participant.
  • Create a special Action Item table. As soon as any issue causes discussion, The Scrum master will put it to the action item table in the format: “What Who When”

For Example:
What: Discuss problem with controls.
Who: Tom, Jerry.
When: Right after scrum meeting.

During the daily scrum meeting, participants depart from theme.
  • Once more — the daily scrum meeting should be short.
  • The place for the daily scrum meeting should be away from emails, Internet and other amusements.
  • Scrum master should manage the scrum meeting properly.

The Scrum meeting is an integral part of the Agile Method of project management. From a very high-level view the definition of Agile Method for project management is a collection of fitting situational best practices that encourages stakeholder participation and communication. The Agile Method in conjunction with the appropriate tools is a good way to manage a project and takes into consideration the individual's perspective on the processes of teamwork, communication and development. Read more about the creative technology that can be used in conjunction with Agile Method in the article “Agile Development with ConceptDraw MINDMAP”.

Was this Information Useful?