Please enable JavaScript.
Coggle requires JavaScript to display documents.
SCRUM ROLLEN (THE SCRUM TEAM (Consist of DevTeam, PO and SM.
PO and SM…
SCRUM ROLLEN
THE SCRUM TEAM
Consist of DevTeam, PO and SM.
PO and SM can simultaneously also be in the DevTeam.
SELF-ORGANIZING
Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
CROSS-FUNCTIONAL
Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team
SCRUM TEAMS ARE DESIGNED TO
to optimize
- flexibility,
- creativity, and
- productivity.
proven itself to be effective for any complex work
APPROACH
- Scrum Teams deliver products iteratively and incrementally,
- maximizing opportunities for feedback.
- Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available.
DEVELOPMENT TEAM
SELF-ORGANIZED
Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.
CREATING THE INCREMENT
- The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.
- A “Done” increment is required at the Sprint Review.
- Only members of the Development Team create the Increment.
CHARACTERISTICS
• They are self-organizing.
- No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
• Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;
• Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
• Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and,
• Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
TEAM SIZE
Optimal Development Team size
- Between 3 and 9 Team Members
- cross-functional = must have all the expertise necessary to do the work without outside help
- The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
MINIMUM 3 MEMBERS - small enough to remain nimble
- Fewer than three Development Team members decrease interaction and results in smaller productivity gains.
- Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment.
MAXIMUM 9 MEMBERS - large enough to complete significant work within a Sprint
- Having more than nine members requires too much coordination.
- Large Development Teams generate too much complexity for an empirical process to be useful.
PRODUCT OWNER
ROLE FUNCTION
The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team
- How this is done may vary widely across organizations, Scrum Teams, and individuals.
SOLELY RESPONSIBLE FOR
PRODUCT BACKLOG MANAGEMENT
- The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.
Clearly expressing Product Backlog items
- Specifications
- all information needed to develop functionality
-
-
ENSURING PRODUCT BACKLOG IS
- VISIBLE
- TRANSPARENT
- CLEAR TO ALL
and shows what Scrum Team will work on next
-
relations
-
For the Product Owner to succeed, the entire organization must respect his or her decisions.
-
-
SCRUM MASTER
RESPONSIBLE FOR
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
SERVANT-LEADER
The Scrum Master is a servant-leader for the Scrum Team.
- The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t.
- The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
-