Method wall › Roles
Roles
Method cards filed under Roles.
Roles
The Scrum Master Removes Obstacles Rather Than Assigning Tasks
CeremonySprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and Backlog Refinement; each has a time-box and a defined purpose.
RolesProduct Owner (value and backlog), Scrum Master (process and obstacle removal), Developers (delivery); no task-assigning manager.
ArtifactsProduct Backlog, Sprint Backlog, Increment; the Sprint Goal is a commitment, not a task list.
CadenceFixed-length Sprints, usually two to four weeks, with a consistent rhythm of planning, daily inspection, review, and retrospective.
The Scrum Master is often described as a servant-leader, but the practical heart of the role is obstacle removal.
Roles
The Product Owner Owns the Order of the Backlog
CeremonySprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, plus ongoing Product Backlog refinement
RolesProduct Owner (orders the backlog and maximizes value), Scrum Master (servant-leader and process coach), Developers (cross-functional delivery team)
ArtifactsProduct Backlog, Sprint Backlog, Increment, Definition of Done, Sprint Goal
CadenceTime-boxed Sprints, commonly one to four weeks, with a consistent length
The Product Owner owns the order of the backlog.
Roles
What a Development Team Actually Decides on Its Own
CeremonyDaily coordination meetings where the team inspects progress and adapts the plan; a planning session to choose work for the next cycle; a review to show the result to stakeholders; and a retrospective to improve how the team works.
RolesThe team holds the delivery work and the decisions about how to do it; a product-focused role orders the work by value; a coaching role helps the team apply the method and remove obstacles.
ArtifactsAn ordered list of work items, a visible board showing what is in progress, a definition of done, and a working increment that meets that definition.
CadenceA short, fixed cycle, often one to four weeks, that ends with a review and a retrospective before the next cycle begins.
A development team does not decide everything.