Pass the Scrum Professional Scrum Master PSM-I Questions and answers with CertsForce

The correct answer is C because the Daily Scrum is specifically an event for the Developers of the Scrum Team. According to the Scrum Guide, the Daily Scrum is held by the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. This makes the Developers the only people who must attend.

The Scrum Master’s responsibility is to ensure that the event takes place and that attendees understand its purpose, but the Scrum Master is not required to attend unless they are actively helping the Developers or are also participating as part of the team’s work. The Product Owner is also not required to attend. While either the Scrum Master or Product Owner may be present, the Daily Scrum remains a Developers’ event.

Options A, B, D, and E are incorrect because they include roles that are not mandatory participants. Scrum is careful about this distinction to preserve self-management and ensure the Developers own daily planning. The Daily Scrum is not a status meeting for management or other roles. It is a focused inspection-and-adaptation event for the Developers.

The correct answers are A and B. When multiple Scrum Teams work on the same product, Scrum calls for one Product Owner and one Product Backlog for that product. This ensures a single source of prioritization, clear accountability for maximizing value, and consistent product direction. One Product Owner helps avoid conflicting priorities across teams and provides one clear voice for product decisions.

One Product Backlog is equally important because it creates transparency for all work needed to develop the product. If each team had its own separate Product Backlog, the organization would risk fragmentation, duplicate work, inconsistent ordering, and confusion about the overall product direction. A single Product Backlog supports coordinated planning and alignment across all teams contributing to the same product.

Options C, D, and E are incorrect because they divide product accountability across multiple backlogs or multiple Product Owners. Scrum does not define a Chief Product Owner structure. For one product, there should be one Product Owner and one Product Backlog, even when multiple Scrum Teams are involved. This setup best supports focus, transparency, and value optimization.

The correct answer is A, because if two Scrum Teams are added to the development of a product that previously had only one Scrum Team, the immediate impact on the productivity of the original Scrum Team is likely to decrease. This is because adding more teams may introduce some challenges and trade-offs, such as increased communication and coordination overhead, reduced alignment and cohesion, and potential conflicts or dependencies.

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 Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.

The correct answer is C because the Product Owner is a full member of the Scrum Team and participates in the Sprint Retrospective along with the Developers and Scrum Master. The Sprint Retrospective is not a meeting only for Developers or only for process specialists. It is an event for the Scrum Team to inspect how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done, and then identify improvements for the future.

The Product Owner’s role in this event is not to act as an external observer or a stakeholder representative. Instead, the Product Owner contributes as a Scrum Team member by sharing observations, listening to concerns, and collaborating on ways to improve effectiveness and value delivery. This shared participation supports transparency and continuous improvement.

Option A is incorrect because the Retrospective is an internal Scrum Team event, not a stakeholder reporting session. Option B is incorrect because the Product Owner absolutely should participate. Option D is incorrect because capturing backlog requirements is not the purpose of the Retrospective. The main purpose is improvement of how the team works together.

The correct answers are A, B, and D, because these techniques would be most helpful in this situation. Consulting with the Development Team may help identify the root causes of the impediments and possible solutions. Prioritizing the list and working on them in order may help reduce the backlog and focus on the most important or urgent issues. Alerting management to the impediments and their impact may help escalate the problems and get support from the organization.

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).

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 backlogs 1 .  NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release 1 . 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.

The Scrum Team consists of three roles: the Scrum Master, who coaches and facilitates the team; the Product Owner, who manages and prioritizes the Product Backlog; and the Development Team, who delivers a potentially releasable Increment at the end of each Sprint. A project manager is not part of the Scrum Team, as Scrum does not recognize titles or sub-teams. None of the above is also not a correct answer, as it implies that there is no Scrum Team at all.