Five new Scrum Teams have been created to build one product. A few of the Developers ask the Scrum Master who will coordinate the work between the different Scrum Teams. What should the Scrum Master do?
Answer(s): B
Development Teams are structured and empowered by the organization to organize and manage their own work. This includes deciding how to form teams when multiple teams are needed. The resulting synergy optimizes the Development Team's overall efficiency and effectiveness. 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.
Which statements are true about the Sprint Goal? (Choose two.)
Answer(s): B,C
The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team.Only the Development Team can assess what it can accomplish over the upcoming Sprint.The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.
If there are multiple Scrum Teams working on the same product, all of the Scrum Teams must mutually define a Definition of Ready (DoR). The DoR is a checklist that the Product Owner must fulfill before a Product Backlog item can be presented at the Sprint Planning. This protects the Development Team from interruptions and disruptions during the Sprint.
Product Backlog items should be clear enough and have enough information for the Product Owner and Development to understand the work that needs to be done and to create a forecast of Product Backlog items to implement the Sprint Goal. Nothing stops the flow of Sprints, for example, we do not delay the Sprint because the items are not ready. In such cases, the "unready" items would be selected for the Sprint anyway and refined during the Sprint.In the case that the Product Backlog items are not clear enough, the Development Team forecasts the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint. At the end of the Sprint, the Scrum Team can discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
How should a Scrum Master coordinate the work when more than one Scrum Team is working on one product?
Answer(s): A
One of the benefits of self-organized teams is the ability to decide how best to work together to produce a shippable Increment.
What would be typical Scrum Master activities during the Sprint?
Post your Comments and Discuss Scrum PSM II exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PSM II content, but please register or login to continue.