Free PSM II Exam Braindumps
Professional Scrum Master II Questions 46–50 (page: 11)

Updated On: 10-Feb-2026

During a Sprint Review, the Product Owner determines that she is going to release the current Increment to production. The stakeholders ask to stop the Sprint to react more quickly to the user feedback that is expected after this release. The Product Owner prefers to continue the Sprint to make progress with the next release. You facilitate a discussion on how to proceed.
What are two acceptable results of this discussion? (Choose two.)

  1. Continue sprinting and include the customer feedback in the Product Backlog.
  2. Stop sprinting and let the Developers work on new customer requests as they arise.
  3. Continue sprinting but shorten the Sprint length to allow for shorter feedback loops.
  4. Continue sprinting but allow customer feedback to change the Sprint Goal within the Sprint.

Answer(s): A,C

Explanation:

A new Sprint starts immediately after the conclusion of the previous Sprint. Delaying the start of the next Sprint interrupts progress and can reduce the Time-to-Market. Shortening the Sprint length allows the team to respond quicker to changes outside of the Sprint plan and while still allowing delivery of business value. Adding user feedback to the Product Backlog helps the Product Owner with ordering the backlog to maximize the flow of value.
During the Sprint no changes are made that would endanger the Sprint Goal.



At the Sprint Planning, the Development Team is not able to forecast the number of Product Backlog items it can do in the upcoming Sprint due to unclear requirements. The Product Owner, however, was able to clearly define the business objective he hopes to achieve in the Sprint.

Which of the following two actions would you support? (Choose two.)

  1. The Development Team forecasts the most likely Product Backlog items to meet the business objective and create a Sprint Backlog based on a likely initial design and plan. Once the time- box for the Sprint Planning meeting is over, they start implementation and continue to analyze, decompose, and create additional functionality during the Sprint.
  2. If all agree they can extend the Sprint Planning until the Development Team can forecast enough Product Backlog items before starting the implementation.
  3. Allow the Development Team members as much time as needed to review the Product Backlog items and reconvene with the Product Owner when they are confident enough to make a forecast for the Sprint.
  4. They discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to occur again.

Answer(s): A,D

Explanation:

All events are time-boxed events, such that every event has a maximum duration. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.



Steven is a Scrum Master on a new Scrum Team.

What would be the best way for him to determine if the Product Owner is interacting enough with the Development Team during a Sprint?

  1. Check whether the Product Owner is actively engaged at the Daily Scrums.
  2. Check whether the Increment presented at the Sprint Review meets the Product Owner's expectations.
  3. See whether the Product Owner has provided enough information at the Sprint Planning to make his/her presence optional during the Sprint. The level of autonomy within Development Team can be the result of having the right presence from the Product Owner.
  4. The Product Owner must always be present with the Development Team. Unavailability of the Product Owner is prohibited in Scrum.

Answer(s): C

Explanation:

Outcomes of the Scrum Team are affected by the Product Owner's participation and availability. During a Sprint he/she is responsible for answering questions from the Development Team about items in the current Sprint and optimizing the value of the work the Development Team does.



What are two ways in which technical debt relates to velocity? (Choose two.)

  1. They are not related, technical debt should be resolved by the support or operations department, not by the Developers.
  2. Velocity may unexpectedly drop when the Developers run into technical debt while attempting to complete new Product Backlog items.
  3. Developers can artificially increase velocity by incurring technical debt.
  4. Adding technical debt items to the Product Backlog to get estimated and added to your velocity forecasts can guarantee predictability.

Answer(s): B,C

Explanation:

Technical debt is a natural occurrence when developing complex products. It is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer. And how it is managed will depend on the team AND context of the situation.



A Scrum Team has been working together for nine Sprints. A new Product Owner comes in, unsure about his responsibilities. As the Scrum Master you have observed how the functional and business insights of the Developers have grown over the past Sprints. The Product Owner however is relatively new to the company and to the product.
What are two activities you would direct the new Product Owner towards focusing on? (Choose two.)

  1. You advise the Product Owner to start building a good relationship with the stakeholders of the product. On- going interaction with them is important to regularly align with changing organizational or market expectations. The Product Owner is also expected to invite the appropriate stakeholders to the Sprint Review.
  2. You inform the Product Owner that, in today's highly competitive markets, it is important that the Developers are updated on changing business priorities on a daily basis. It is why Scrum has this daily meeting. At this Daily Scrum the Developers can adapt to the changes in scope without delay.
  3. You tell the Product Owner to make sure that there are no ambiguities or possible misunderstandings in the items on the Product Backlog when they are handed over to the Scrum Team. This is best done by capturing the functional requirements during an analysis phase, resulting in documents that are considered as the working product of such analysis Sprints.
  4. You advise the Product Owner to rely on others in the Scrum Team and the stakeholders to formulate the Product Backlog, as they are the ones that are up to speed. By questioning them and working with them the Product Owner will quickly become more productive.

Answer(s): A,D

Explanation:

The ones that are closest to the work are the best ones to understand and explain what the work is and what the needs of the users and product are.



Viewing page 11 of 46
Viewing questions 51 - 55 out of 221 questions


Post your Comments and Discuss Scrum PSM II exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!