Reports - Do you understand the implied contract (promises) between Members of the Scrum Team?
v9.0
Posted at
1/12/2010 1:26 PM by
system
Rule Intro
Member of the Scrum Team should understand their responsibilities and respect the implicit contract (promises) they have made.
Page Content
|
Role
|
Promises
|
|
The Organization
|
- the team that there are stakeholders (including subject matter experts) who will help when needed
- the team that there are stakeholders (including subject matter experts) who will help when needed
- they will help the ScrumMaster in the removal of impediments to the Scrum team’s progress
- the team that they will not change priorities or constraints in the middle of a sprint without team’s consent
- that being on a Scrum team will not hurt the members’ careers
- not to divert team members to other work on a Scrum Day during a sprint
|
|
Product Owner
|
- to supply an initial product backlog
- to prioritize the product backlog when needed
- to be responsive to requests for feedback and clarification
- empowered “voice of the customer” will be provided to answer business domain questions promptly (minutes or hours, not days)
- to attend every Review, Retrospective
- not to change priorities or scope during a sprint
- not to direct team members to do work not agreed and planned at the beginning of the sprint
|
|
ScrumMaster
|
- to keep the team healthy by focusing on the removal of impediments, both internal and external
- to protect the team from external distractions
|
|
The Team
|
- that its work will be transparent, that it will make decisions and solve problems as a group, and that no individual team member will be left behind
- to take prioritization and scope from the product owner on the team driving the team based on stakeholders interests
- to use the stakeholders’ time wisely, by focusing on questions that are relevant to the work being done now
- to do quality work the best way they know how within the constraints set forth by the organization
- to deliver demonstrable product at the end of every sprint for review and validation by the stakeholders
- to endeavor to become multi-skilled by sharing and pairing and not relying on experts on the team for specific functions
|
|
Team Member
|
- to bring issues, problems, impediments and realities encountered to the team
- to be available and working with the team on every defined Scrum Day of a sprint in which they committed and any required absences will be scheduled before the beginning of the sprint
- to attend every Scrum, Review, Retrospective & Planning Meeting
- to refer any external request that will take more than 15 minutes of Scrum Day time to the ScrumMaster
|
Do you like this rule?
Do you follow this rule?