Role: Scrum Team
The Scrum Team builds the product that the customer is going to consume: the software or website, for example. The team in Scrum is "cross-functional" - it includes all the expertise necessary to deliver the potentially shippable product each Sprint - and it is "self-organizing", with a very high degree of autonomy and accountability.
Role Sets: Scrum Roles
Relationships

Estimating the Product BacklogRelease PlanningSprint Planning MeetingSprint RetrospectiveSprint Review MeetingThe Daily ScrumPotentially Shippable Product IncremementRelease Burndown ChartSprint BacklogScrum_Team
Modifies
    Main Description

    The Team:

    • Is cross-functional, with seven (plus/minus two) members;
    • Selects the Sprint goal and specifies work results;
    • Has the right to do everything within the boundaries of the project guidelines to reach the Sprint goal;
    • Organizes itself and its work; and
    • Demos work results to the Product Owner.

    Scrum teams do not include any of the traditional software engineering roles such as programmer, designer, tester, or architect. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint. Scrum teams develop a deep form of camaraderie and a feeling that "we're all in this together."

    A typical Scrum team is 5-9 people but can be scaled using a Scrum of Scrums.

    Staffing
    Assignment Approaches

    Members should be full-time but there may be exceptions (e.g. database administrator)

    Members should change only between sprints

    This program and the accompanying materials are made available under the
    Eclipse Public License v1.0 which accompanies this distribution.

    Copyright © 1998--2008 Mountain Goat Software. All rights reserved.
    Copyright © 2008 ATSC. All rights reserved.