How often should Scrum Team membership change?
Answer : A
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.
What is the accountability of the Product Owner during Sprint 0? (Choose the best answer.)
Answer : A
There is no such thing as Sprint 0 in Scrum, as stated in [7]: ''Sprint 0 is a term used by some people who use Scrum to describe an initial period before starting Sprints where they do some upfront planning or analysis. However, this is not part of Scrum and contradicts its principles of empirical process control, iterative delivery, and responding to change.''
True or False: The Product Owner makes sure the Developers select enough from the Product
Backlog tor a Sprint to satisfy the stakeholders.
Answer : B
According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.
What activities would a Product Owner typically undertake in the phase between the end of the current Sprint and the start of the next Sprint?
Answer : A
There are no activities that a Product Owner would typically undertake in the phase between the end of the current Sprint and the start of the next Sprint, because there is no such phase. The next Sprint starts immediately after the current Sprint, without any gaps or breaks. The other options are either activities that occur during a Sprint (such as refining the Product Backlog) or activities that are not consistent with Scrum (such as working with Quality Assurance departments or updating project plans).
True or False: Multiple scrum Teams working on the same product must have the same Sprint start date.
Answer : B
According to the Scrum Guide, multiple Scrum Teams working on the same product do not have to have the same Sprint start date. They may start their Sprints at different times, as long as they synchronize their work and integrate their Increments at least by the end of each Sprint. The other option is not valid, as it implies that having the same Sprint start date is mandatory for multiple Scrum Teams.
What is the timebox for the sprint Review? (choose the best answer)
Answer : B
The timebox for the Sprint Review is four hours for a one-month Sprint, as stated in [4]: ''The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been ''Done'' and what has not been ''Done''; additionally, they discuss any changes to scope or budget or potential value. The entire group then collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is a working session and attendees should inspect based on facts. A Sprint Review is held at the end of every Sprint for a maximum duration of four hours for a one-month Sprint.''
What does n mean tor a scrum Team to be cross-function at? (choose the best answer)
Answer : A
According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).