Scrum PSM-I - Professional Scrum Master I

The best answer is B. The Developers on the Scrum Team should write the user documentation. According to the Scrum Guide, the Definition of Done creates transparency and ensures that the product Increment meets the quality standards required for the product 1 . If user documentation is part of the Definition of Done, then it should be completed within the Sprint by the Scrum Team 1 . The Scrum Team should have all the skills needed to deliver the product, and if user documentation is part of the product, then that skill should be on the team as well 2 . The Developers on the Scrum Team are responsible for creating a plan for delivering the Increment, which includes user documentation 1 . They can also ask for help from other more experienced writers outside the team, or learn the skill through training or workshops 2 . The other options are not consistent with the Scrum values and principles, as they would create dependencies, delays, and waste in the product development process.

According to the Scrum Guide 1 , there are five values that guide decisions within Scrum teams:

Commitment

Focus

Openness

Respect

Courage

By not building Product Backlog items that have low business value, Scrum teams exhibit respect for their stakeholders and customers, as they deliver what is most valuable and relevant for them. They also exhibit focus, as they concentrate on what matters most for achieving their Product Goal and Sprint Goal. They also exhibit courage, as they are willing to say no to low-value work and face possible conflicts or disagreements.

According to the Scrum Guide 1 , the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The length of a Sprint should be short enough to keep the business risk acceptable to the Product Owner, short enough to be able to synchronize the development work with other business events, and no more than one calendar month.

According to the Scrum Guide, management external to the Scrum Team is not involved in the Daily Scrum at all. The Daily Scrum is an internal event for the Development Team to inspect their progress toward the Sprint Goal and plan their work for the next 24 hours. The other options are not valid ways for management to be involved in the Daily Scrum, as they are either intrusive (such as giving an update or speaking on behalf of others) or unnecessary (such as being represented by the Product Owner or the Scrum Master).

According to the Scrum Guide 1 , the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

According to the Scrum Guide, a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint at the Sprint Planning event. This is when the Developers select items from the Product Backlog that they can commit to complete within a Sprint. The Developers are then responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they either imply that Developers are not accountable for value (such as never or whenever), or that they become accountable at a different time (such as during the Daily Scrum).

The correct answer is B because cross-functional teams in Scrum are not optimized to work on only one component or one technical layer of a system. A cross-functional Scrum Team has all the skills necessary to create value each Sprint and deliver a usable Increment. This means the team should be capable of working across the different skills and disciplines needed to complete Product Backlog items according to the Definition of Done.

If a team is organized around only one component or specialty, it creates handoffs, dependencies, and silos. Those conditions reduce agility and make it harder to deliver a complete Increment each Sprint. Scrum instead favors teams that can collaborate across analysis, design, development, testing, and other needed capabilities so they can produce finished product value rather than partial technical output.

Cross-functionality supports self-management and reduces delays caused by waiting on other specialists or teams. It helps the Scrum Team focus on outcomes instead of isolated activities. In Scrum, the goal is not local optimization of a single layer or function. The goal is delivering complete, useful, high-value Increments frequently and transparently.

The correct answer is B, because the guideline that a Scrum Master should give is that estimates are made by the Development Team. The Scrum Guide states that “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.” Therefore, the Development Team should estimate the work in Scrum, using any method or unit they prefer.

The correct answer is B. The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint. According to the Scrum Guide 1 , “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint.” This does not mean that every individual has all the skills, but rather that the team as a whole does. Cross-functionality enables the Scrum Team to deliver a potentially releasable Increment of “Done” product at the end of each Sprint, without depending on others outside the team.

The correct answer is D because Scrum Teams are self-managing. That means the Scrum Team, and especially the Developers with respect to Sprint Backlog execution, manages its own work rather than relying on a project manager, Product Owner, or Scrum Master to make sure individuals complete assigned tasks. Scrum does not operate through command-and-control task enforcement. Instead, the team collaborates to achieve the Sprint Goal and holds itself collectively accountable.

Option A is incorrect because Scrum does not define a Project Manager role responsible for directing daily task completion. Option B is incorrect because the Product Owner is accountable for maximizing value, not managing the team’s day-to-day task execution. Option C is incorrect because the Scrum Master coaches and facilitates Scrum but does not supervise or police whether each person does their tasks. Option E is incorrect because the roles listed do not all share this responsibility.

A key Scrum principle is collective accountability. The Scrum Team organizes its own work, inspects progress, and adapts as needed. Rather than focusing on whether each individual completes personal assignments, Scrum emphasizes whether the team is progressing toward the Sprint Goal and delivering a Done Increment.