How often should Development Team membership change?
The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that ''development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; development Teams 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.'' Therefore, changing Development Team membership may affect their cross-functionality and self-organization in the short term.
The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take?
A product Increment must be released to production at the end of each Sprint.
The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. The Scrum Guide states that ''at the end of a Sprint, the new Increment must be 'Done,' which means it must be in useable condition and meet the Scrum Team's definition of 'Done'. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.'' Therefore, a product Increment must be potentially releasable, but the decision to release it is up to the Product Owner.
A Product Owner wants advice from the Scrum Master about estimating work in Scrum. Which of these is the guideline that a Scrum Master should give? (Choose the best answer.)
According to the Scrum Guide, estimates are made by the people doing the work, which is the Development Team. The Development Team is responsible for all estimates in the Product Backlog and the Sprint Backlog. The other options are not valid guidelines for estimating work in Scrum, as they are either too prescriptive (such as requiring story points or relative units), incorrect (such as forbidding estimating or having the Product Owner make estimates), or unnecessary (such as checking estimates with the Development Team).