Scrum PSM I Practice Test - Questions Answers, Page 22

According to the Scrum Guide, a high-performance Scrum Team does not run a Release Sprint, as this is not a Scrum event. A Release Sprint is a term used to describe a Sprint that is dedicated to finalizing the product for release, such as fixing bugs, polishing features, or integrating components.

This is contrary to the Scrum principle of delivering a potentially releasable Increment at the end of each Sprint, regardless of whether it is actually released or not. Therefore, the answer is false.

According to the Scrum Guide, the Sprint Backlog may include any items that are a decomposition of the selected Product Backlog items, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is the Developers' plan for the Sprint, and it contains all the work that they forecast they can do to achieve the Sprint Goal and create a "Done" Increment. The other options are not valid, as they are either too specific (such as user stories or tasks) or too vague (such as tests).

According to the Scrum Guide, the Scrum Team is responsible for removing a Developer from the Scrum Team if necessary, as they are self-managing and accountable for creating valuable Increments. The other options are not valid, as they imply that someone else outside the Scrum Team has the authority to remove a Developer (such as the Scrum Master, the Product Owner, or the hiring manager), which is not consistent with Scrum values and principles.

According to the Scrum Guide, a Scrum Team must release each Increment when it makes sense to do so, based on the value and feedback obtained from stakeholders. The decision to release an Increment is made by the Product Owner, who is responsible for maximizing the value of the product and the work of the Development Team. The other options are not valid, as they imply that releasing an Increment is either mandatory (such as after every Sprint), conditional (such as when the product is free of defects), or irrelevant (such as when the Scrum Team finishes their work).

According to the Scrum Guide, Developers are self-managing, which means that they manage their own Sprint Backlog. They decide how to organize their work and collaborate effectively to deliver a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that Developers manage things that are either determined by the Scrum framework (such as Sprint length), by collaboration with other roles (such as when to release or stakeholders for the Sprint Review), or by the Product Owner (such as Product Backlog ordering).

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.

According to the Scrum Guide, the Scrum Team should make sure that everyone on the team does their tasks for the Sprint, as they are collectively accountable for creating valuable Increments that meet stakeholder needs and expectations. The other options are not valid, as they imply that someone else outside the Scrum Team (such as a project manager) or another role on the Scrum Team (such as the Product Owner or the Scrum Master) is responsible for making sure that everyone does their tasks for the Sprint.

According to the Scrum Guide, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other options are not valid, as they are either too long (such as monthly), too vague (such as whenever it's done), or too short (such as 4 hours for a one-month Sprint).

According to the Scrum Guide, the Product Owner must participate in the Daily Scrum when he or she is actively working on items on the Sprint Backlog; however, they participate as a Developer, not as an authority figure. This means that the Product Owner can share progress, plans, and impediments with the other Developers and collaborate with them on delivering value. The other options are not valid reasons for the Product Owner to participate in the Daily Scrum, as they are either irrelevant (such as representing stakeholders or discussing impediments) or inappropriate (such as being asked by the Scrum Master).