What are three benefits of self-managing Scrum Teams?
(choose the best three answers)
Increased rule compliance.
Increased self-accountability.
Increased creativity.
Increased commitment.
Increased accuracy of estimates.
The Answer Is:
B, C, DExplanation:
Self-managing Scrum Teams are teams that internally decide who does what, when, and how, rather than being directed by others outside the team 11. Self-managing Scrum Teams have the following benefits:
Increased self-accountability: Self-managing Scrum Teams are accountable for delivering a potentially releasable product Increment every Sprint that meets the Definition of Done and the Product Goal 22. They are also accountable for following the Scrum values and principles, and for inspecting and adapting their work and process 33. By being accountable for their own decisions and actions, self-managing Scrum Teams are more responsible, transparent, and quality-oriented.
Increased creativity: Self-managing Scrum Teams have the autonomy and the empowerment to choose how best to accomplish their work, rather than being constrained by predefined methods or instructions 44. They also have the opportunity to experiment, learn, and innovate, as they are encouraged to try new ideas and approaches to solve complex problems [5]. By having the freedom and the support to be creative, self-managing Scrum Teams are more productive, adaptive, and valuable.
Increased commitment: Self-managing Scrum Teams have the ownership and the involvement in their work, as they are part of the planning, execution, and review of the product development [6]. They also have the trust and the collaboration among the team members, as they share a common goal and vision, and respect each other’s skills and abilities [7]. By having the sense of belonging and the teamwork, self-managing Scrum Teams are more motivated, engaged, and satisfied.
The purpose of Nexus Sprint Planning is to:
(choose the best two answers)
Coordinate the activities of all the Scrum Teams in a Nexus.
Discover all the dependencies between Product Backlog items.
Ensure all teams are committing to the right work.
Create a plan for the Sprint.
The Answer Is:
A, DExplanation:
The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 11. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 11. One of the key events in the Nexus framework is the Nexus Sprint Planning, which is used to coordinate the activities of all teams in the Nexus for a single Sprint 11.
The purpose of Nexus Sprint Planning is to:
Coordinate the activities of all the Scrum Teams in a Nexus. This is answer A. This is a valid answer because the Nexus Sprint Planning is an event where the Nexus, consisting of the Product Owner and appropriate representatives from each team, meet to plan the Sprint 11. The purpose of Nexus Sprint Planning is to coordinate the activities of all teams in the Nexus for a single Sprint 11. The Nexus Sprint Planning helps the teams to align their work with the Product Goal, identify and resolve dependencies, and create a common understanding of the Sprint 11.
Create a plan for the Sprint. This is answer D. This is a valid answer because the Nexus Sprint Planning is an event where the Nexus creates a plan for the Sprint 11. The result of Nexus Sprint Planning is a Nexus Sprint Goal that aligns with the Product Goal and a Nexus Sprint Backlog that contains the work to be done by the teams to achieve the Nexus Sprint Goal 11. The Nexus Sprint Backlog is a visualization of the work across the Nexus that has dependencies 11. The Nexus Sprint Goal and the Nexus Sprint Backlog guide the teams throughout the Sprint 11.
The other two answers are not correct because:
Discover all the dependencies between Product Backlog items. This is answer B. This is not a valid answer because the Nexus Sprint Planning is not the only time to discover all the dependencies between Product Backlog items. Dependencies are the relationships between the work items that affect the order, timing, or outcome of the work 22. Dependencies can cause delays, rework, waste, and lower quality 22. Therefore, it is important to identify and resolve dependencies as early and as often as possible 22. The Nexus Sprint Planning is a time to coordinate the activities of the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog 11. The discovery of dependencies should be done continuously throughout the Sprint, not only during the Nexus Sprint Planning 11. One of the activities that can help the teams to discover dependencies before the Nexus Sprint Planning is the Cross-Team Refinement, where representatives from each team in the Nexus meet to decompose and refine the Product Backlog items into smaller pieces of work that can be delivered by a single team or multiple teams 1[1][6].
Ensure all teams are committing to the right work. This is answer C. This is not a valid answer because the Nexus Sprint Planning is not a time to ensure all teams are committing to the right work. The Nexus Sprint Planning is a time to coordinate the activities of the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog 11. The Nexus Sprint Planning is not a time to impose or dictate the work to the teams, but rather to collaborate and align the work with the Product Goal 11. The teams are self-organizing and autonomous, which means they decide how to do their work and what work to do 1[1][7]. The teams do not commit to the work, but rather forecast the work based on their capacity and understanding 1[1][7].