PSM-I Exam Dumps and Practice Questions

Scrum promotes self-management by empowering the Scrum Team to take ownership of their work and processes. The best three answers are:

A . By having the Scrum Master protect the Scrum Team: The Scrum Master plays a key role in shielding the team from external distractions and impediments, allowing the team to focus on self-management and delivering value.

B . By the Scrum Team deciding what work to do in a Sprint: During Sprint Planning, the Scrum Team collaboratively selects and commits to the work they can accomplish within the Sprint, fostering self-organization and decision-making.

C . By being a lightweight framework: Scrum's simplicity and minimal structure provide the team with the flexibility to adapt and manage their work, encouraging self-management without imposing rigid controls.

Three statements that are true about Scrum are:

Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products.

Scrum is a framework for developing and sustaining complex products.

Scrum is based on empiricism and lean thinking.

These statements are supported by [6]: ''Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. ... Each component within the framework serves a specific purpose and is essential to Scrum's success and usage. ... The rules of Scrum bind together events, roles, artifacts, and rules governing their relationships. ... The three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.''

The best answer is C. Ensure every Increment meets them.Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs1.NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release1. The Scrum Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.

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 Guide1, only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, the Scrum Master should allow the Development Team to self-manage and determine for itself what to do regarding the logistical challenges of meeting in different locations.