PSM-I Exam Dumps - Scrum Professional Scrum Master Questions and Answers

The correct answer is C because Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. This timebox is defined in the Scrum Guide and helps ensure that planning is focused, efficient, and proportionate to the length of the Sprint.

Sprint Planning starts the Sprint by setting a clear direction for the work ahead. During this event, the Scrum Team discusses why the Sprint is valuable, what can be done during the Sprint, and how the chosen work will be accomplished. The outcome is the Sprint Goal, the selected Product Backlog items, and the initial Sprint Backlog plan.

Option A is incorrect because four hours is not the Scrum Guide’s timebox for a one-month Sprint. Option B is incorrect because “monthly” is not a valid timebox length for the event itself. Option D is incorrect because Scrum events are always timeboxed to promote discipline and effectiveness.

This timebox matters because Scrum encourages enough planning to begin effectively, but not so much that excessive discussion delays value delivery. The purpose is to create clarity and alignment while still preserving agility and adaptability.

If the Development Team cannot complete its work by the end of the Sprint, then the Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length, as stated in [7]: “If a Development Team determines it has overcommitted itself for a Sprint, one option is to collaborate with the Product Owner to negotiate removing or reducing scope. Another option is to simply work hard and do its best, without cutting quality or pressuring individuals. In either case, the Development Team learns from its experience and uses this learning when planning future Sprints.”

The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event for the Development Team, and the Product Owner can attend only if invited by the Development Team.

According to the Scrum Guide, every Scrum Team should have the competencies and skills needed to deliver an Increment in a 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 what every Scrum Team should have, as they either imply that the Developers work in silos or rely on external people (such as a lead developer or representatives from different departments).

 The Scrum Master should be concerned about the ability of the Development Teams to produce integrated Increments, as this is one of the goals of Scrum. The Scrum Master should also encourage the Development Teams to figure out a solution for themselves, as this fosters self-management and collaboration. The other options are not relevant or important for the Scrum Master in this situation.

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.

A Product Owner releases each Increment when it makes sense, as stated in [2]: “The Product Owner decides when to release an Increment. This can be done at any time during or after a Sprint. The Product Owner may choose to release an Increment when it delivers enough value to customers or users, when it meets a market opportunity, when it reduces risk or uncertainty, or when it aligns with other business goals.”

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 in Scrum, Developers are collectively accountable for creating a usable Increment every Sprint, and they share accountability for the Sprint Backlog. Scrum emphasizes self-management and collective ownership rather than assigning individual accountability for separate backlog items in the traditional sense. The Developers decide how to turn selected Product Backlog items into an Increment and how to organize their work, but the responsibility remains shared across the team.

This shared accountability supports collaboration, flexibility, and focus on the Sprint Goal. It prevents siloed behavior where individuals protect only their own tasks instead of working together to achieve the Sprint outcome. The Sprint Backlog is created by and for the Developers, and they adapt it throughout the Sprint as more is learned.

Option A is incorrect because accountability does not begin during the Daily Scrum. Option C is incorrect because capacity does not create individual ownership in Scrum. Option D is incorrect because Scrum does not require even task splitting or pre-assigned ownership at Sprint Planning. The Developers remain collectively accountable throughout the Sprint.