Daily scrum meeting

Each day during the sprint, a project team communication meeting occurs. This is called the daily scrum (meeting) (or "stand-up meeting") and has specific guidelines:

· All members of the development team come prepared with the updates for the meeting.

· The meeting starts precisely on time even if some development team members are missing.

· The meeting should happen at the same location and same time every day.

· The meeting length is set (timeboxed) to 15 minutes.

· All are welcome, but normally only the core roles speak.

During the meeting, each team member answers three questions:

· What have you done since yesterday?

· What are you planning to do today?

· Any impediments/stumbling blocks? Any impediment/stumbling block identified in this meeting is documented by the Scrum Master and worked towards resolution outside of this meeting. No detailed discussions shall happen in this meeting.

End meetings (Sprint Review and Sprint Retrospective)[edit]

At the end of a sprint cycle, two meetings are held: the "Sprint Review Meeting" and the "Sprint Retrospective".

At the Sprint Review Meeting:

· Review the work that was completed and the planned work that was not completed

· Present the completed work to the stakeholders (a.k.a. "the demo")

· Incomplete work cannot be demonstrated

· Four-hour time limit

At the Sprint Retrospective:

· All team members reflect on the past sprint

· Make continuous process improvements

· Two main questions are asked in the sprint retrospective: What went well during the sprint? What could be improved in the next sprint?

· Three-hour time limit

· This meeting is facilitated by the Scrum Master

Extensions[edit]

Backlog refinement (grooming)[edit]

Backlog refinement is the ongoing process of reviewing product backlog items and checking that they are appropriately prioritised and prepared in a way that makes them clear and executable for teams once they enter sprints via the sprint planning activity. Product backlog items may be broken into multiple smaller ones, acceptance criteria may be clarified, or new preparatory work such as clarification on client needs or technical spikes may be identified.

Backlog refinement is not a core Scrum practice but has been adopted as a way of managing the quality of backlog items entering a sprint.^[15]

Scrum of Scrums[edit]

The Scrum of Scrums (meeting) is a technique to scale Scrum up to large development groups (over a dozen people), which allows clusters of teams to discuss their work, focusing especially on areas of overlap and integration. Each daily scrum within a sub-team ends by designating one member as an "ambassador" to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums. Depending on the context, ambassadors may be technical contributors, or each team’s Scrum Master.^[16]

The agenda will be like a Daily Scrum, with the following four questions:^{[ citation needed ]}

· What has your team done since we last met?

· What will your team do before we meet again?

· Is anything slowing your team down or getting in their way?

· Are you about to put something in another team's way?

Resolution of impediments is expected to focus on the challenges of coordination between the teams, and may entail agreeing to interfaces between teams, negotiating responsibility boundaries, etc. The Scrum of Scrums will track these working items via a backlog of its own, where each item contributes to improving between-team coordination.^[16]

As Jeff Sutherland commented,^[16]

Since I originally defined the Scrum of Scrums (Ken Schwaber was at IDX working with me), I can definitively say the Scrum of Scrums is not a "meta Scrum". The Scrum of Scrums as I have used it is responsible for delivering the working software of all teams to the Definition of Done at the end of the Sprint, or for releases during the sprint. PatientKeeper delivered to production four times per Sprint. Ancestry.com delivers to production 220 times per two week sprint. Hubspot delivers live software 100-300 times a day. The Scrum of Scrums Master is held accountable for making this work. So the Scrum of Scrums is an operational delivery mechanism.

Дата добавления: 2015-08-27