1

Agree Meeting Time

• The lead developer should gain an agreement from the team regarding the best time to schedule the daily meeting.
• It is recommended that this time be the earliest available that permits all team members to attend. Flexible working hours in many organizations mean that this will not necessarily be the start of the day. However, a time slot in the morning is referable, so that the team can plan activities for the rest of the day.

2

Hold Meeting

• The lead developer should hold the meeting each day at the agreed time. The meeting should start on time regardless of attendance.
• Team members should adopt a project norm of attending the meeting and be promptly on time for the start of the meeting.
• The meeting should ideally be not longer than 15 minutes.
• The meeting should be held in a mutually convenient location. Often this location will be informal such as a corridor or open space. A formal meeting room and reservation should not be necessary.
• The lead developer should chair the meeting and invite each team member in turn to present.

3

Present Status

• Each team member should announce what they are working on, what work items they have completed since the last meeting, and whether they expect their current work-in-progress to complete before the next meeting. If so, new work from the iteration backlog should be assigned or accepted.
• If any work items are blocked, this should be recorded and the reason for the blockage recorded in the issue log.
• Any foreseen future blocking issues should be raised and recorded for resolution before they affect work-in-progress.

4

Report Issue Log Update

• The  lead developer should inform the team of any significant issue resolution since the last meeting. Work items which have been unblocked should be identified and reassigned to team members for active work.

Updated list of work items in the iteration backlog.

Any issues raised in the meeting.