Guideline: Daily Meetings |  |
This guideline describes how the team can synchronize their work and progress by meeting every day for a quick status update and report on impediments.
Relationships
Related Elements | [Collaboration Guidance]
Main Description
### Practices Daily meetings are also kown as scrum meetings [SCH04]. These meetings help measure the heartbeat of the project. All team members are required to attend it. The meetings are held in the same place at the same time every work day and should not last for more than 15 minutes. Usually, teams do the meetings standing up to keep them short. Anyone who is directly involved can also attend the meeting as an observer, but care should be taken because too many people in the meeting may cause disruption or cause people to be uncomfortable in sharing information. Typical daily meetings should have at most 10 people. During the daily meeting, each team member updates their peers with answers to the following three questions [SCH04]: What did I do yesterday? What will I do today? What is impeding my work? These 3 questions have a specific purpose [SUT06]: The first question tests the focus of the team - anything done that was not work planned for the iteration is questioned. Answering the second question revises project strategy on a daily basis by reorienting the team due to dependency changes that were revealed by the previous question. The third question will create issues that may result in new tasks in the work items list. The most important effect of this question is to create a list of issues that are assigned to the team or to managers. The team should expect management to help eliminating bottlenecks. These are the minimum number of questions that satisfy the goals of daily meetings. Experienced practitioners tend to add an additional question for improving collaboration among team members: "What have I learned or decided of relevance to the team?" [LAR03]. “What might help or hinder others in meeting their commitments?” [YIP]. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. ### Value For self-directed teams, the daily meeting is a mechanism to quickly inform the team about the state of the project and people. It supports openness and allows resolution of dependencies and conflicts in real-time. It builds a team - effective teams are built by regularly communicating, sharing commitments and helping each other. [LAR03] ### What a daily meeting is not The daily meeting is not a status update meeting in which the project manager is collecting information about who is behind schedule. Rather, it is a meeting in which team members make commitments to each other. Neither is it a problem-solving or issue resolution meeting. Issues that are raised are registered and usually dealt with by the relevant team members immediately afterwards. It is the project manager's responsibility to resolve them as quickly as possible or to make sure that someone on the team does so.
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.