Free Scrum PSM-II Exam Practice Questions & Explanations

Last updated on: Aug 29, 2026
Prepared & Reviewed by the ValidExamDumps Editorial Team

At ValidExamDumps, we consistently monitor updates to the Scrum PSM-II exam questions by Scrum. Whenever our team identifies changes in the exam questions, objectives, focus areas or requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these up to date and 100% exam domain coverage questions, our customers can successfully pass the Scrum Professional Scrum Master II exam on their first attempt without needing additional materials or study guides.

Other certification materials providers often include outdated or removed questions by Scrum in their PSM-II exam. These outdated questions lead to customers failing their Scrum Professional Scrum Master II exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions. Our main priority is your success in the Scrum PSM-II exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.

 

Question 1

Marian is a product Owner working on a Scrum Team on a new release for her product. Based on the average velocity of the previous release Marian estimated the project to take seven Sprints. Average velocity In the previous release was thirteen completed units of work per Sprint Development is three Sprints underway, with tour more Sprints to go until the release.

Product Backlog has been stable.

Over the first three Sprints, the Developers report their average velocity is nine, while not having fully tested all the delivered functionality. The Developers estimate that the unfinished testing would have required of a Sprints time. The Developers believe that the required

velocity of thirteen is within their reach. What is the most effective way to recover?

(choose the best answer)

A. The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. up to one release Sprint per three development Sprints may be required, It is Marian's responsibility to inform users and stakeholders Of the impact on the release date.

B. Transparency needs to be restored by addng the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master's duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team Or cancels the project. The Scrum Master will have to inform Product Owner and the stakeholders.

Answer Options
Correct Answer: D
Explanation

The most effective way to recover is to restore transparency and trust by informing the Product Owner that the progress she has perceived to date is not correct.The Increment is not releasable because it does not meet the Definition of Done12, which is a shared understanding of what it means for work to be complete12. The Developers should give the Product Owner their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features.This way, the Developers can ensure that they deliver a valuable, useful, and potentially releasable Increment every Sprint12. The Developers should also re-estimate the effort to complete the remaining backlog, including all testing, and communicate any changes or risks to the Product Owner.In the end, it is the Product Owner's call to continue the project or to cancel it, based on the value and feasibility of the product12.

Some reasons why the other options are not correct are:

A: The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. This option is not correct because it violates the Scrum framework and the Scrum values.The Scrum framework does not prescribe any release Sprints or separate phases for testing or integration12.The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not postpone or hide their undone work. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not mislead or deceive the Product Owner.The Developers should respect the Product Owner's authority and accountability for maximizing the value of the product and the work of the Developers12, not shift the responsibility or blame to them. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.

B: Transparency needs to be restored by adding the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master's duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team or cancels the project. The Scrum Master will have to inform Product Owner and the stakeholders. This option is not correct because it violates the Scrum framework and the Scrum roles.The Scrum framework does not prescribe any velocity or points as measures of progress or success12.The Scrum roles include Product Owner, Scrum Master, and Developers12.The Product Owner is accountable for maximizing the value of the product and the work of the Developers12, not for tracking or controlling their velocity or points.The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide1, causing change that increases the productivity of the Scrum Team1, and working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization1, not for assessing or judging the performance of the Developers or initiating a restart or cancellation of the project.The Developers are accountable for creating a valuable, useful, and potentially releasable Increment every Sprint12, not for meeting a predetermined velocity or points target.

C: In the next Sprints, the Developers keep making sure that all of the selected scope per Sprint is as done as possible, at least at the past level of 90%. In every Sprint the undone work of the previous Sprint is estimated and added to the Sprint Backlog. It comes on top of the expected forecast of 13 units, so it does not mess up progress on the product Backlog. This option is not correct because it violates the Scrum framework and the Scrum values.The Scrum framework requires that each Sprint delivers a potentially releasable Increment that meets the Definition of Done12, not a partially done or incomplete product that accumulates technical debt or quality issues.The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not compromise on quality or value. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not hide or ignore their undone work.The Developers should respect the Product Owner's authority and accountability for maximizing the value of the product and the work of the Developers12, not burden them with additional work or risk. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.


What is an Increment? | Scrum.org

What is a Product Increment? | Scrum.org

Question 2

During the Sprint Review the Product Owner introduces the functionality that is likely to be done over the next Sprints. The Chief Security Officer reminds everyone that through the envisioned functionality, sensitive personal user data will be stored. This might be the subject of external security audits. He reminds everyone of important non-functional requirements with regards to security. These were not applicable and not considered previously What are two effective ways the Scrum Team can manage these high-security concerns?

(choose the best two answers)

Answer Options
Correct Answer: C, D
Explanation

C) They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.

This is a good way because it is consistent with the Scrum principle ofempiricism, which means that the Scrum Team learns and adapts based on the actual outcomes and feedback, rather than following a predefined plan12. By adding these security concerns to the Product Backlog, the Product Owner can prioritize and refine them according to the value and urgency, and communicate them to the stakeholders.By addressing them throughout the next Sprints, the Scrum Team can deliver valuable and functional increments that also meet the security requirements34. D. During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements

This is another good way because it is consistent with the Scrum value ofopenness, which means that the Scrum Team and the stakeholders have a clear and common understanding of the product vision, goals, progress, and risks12. By adding these expectations to the Definition of Done, the Scrum Team can ensure that every future Increment meets the quality standards and satisfies the stakeholder needs.By working with external specialists, the Scrum Team can also leverage their expertise and experience to better understand and implement the security requirements34.

Question 3

Which two of these situations best demonstrate that a Scrum Team is self-managing?

(choose the best two answers)

Answer Options
Correct Answer: A, C
Explanation

A) Developers collaboratively select and re-plan their work during the Sprint. This situation demonstrates that the Scrum Team is self-managing, as it shows that the Developers have the autonomy and authority to decide how to best accomplish their work, without being directed by others outside the team. The Developers can also adapt their plan based on new insights, feedback, or impediments that arise during the Sprint.

C) The Developers create their own Sprint Backlog, reflecting all work that is part of the Definition of Done. This situation also demonstrates that the Scrum Team is self-managing, as it shows that the Developers have the responsibility and accountability to create a realistic and achievable plan for the Sprint, based on their understanding of the Sprint Goal and the Product Backlog items. The Developers also ensure that their work meets the quality standards defined by the Definition of Done.


The Scrum Guide, section 2.3 (The Scrum Team), page 7

The Scrum Guide, section 3.2 (The Daily Scrum), page 9

The Scrum Guide, section 3.5 (The Sprint Planning), page 10

The Scrum Guide, section 3.6 (The Sprint Review), page 11

The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 2 (The Sprint), lesson 3 (The Sprint Goal), lesson 4 (Sprint Planning) and lesson 5 (The Sprint Review)

The Professional Scrum Master II (PSM II) Assessment, question 39

Question 4

Towards the end of Sprint Planning, the Product Owner and the Developers have not been able to reach a clear, mutual understanding about the highest order Product Backlog items. Because of this, the Developers could not figure out how many Product Backlog items they could forecast for the upcoming Sprint. The Product Owner did make it clear what business objective he is hoping to achieve with this Sprint. Which of the following two actions would you support?

(choose the best two answers)

Answer Options
Correct Answer: A, D
Explanation

A) They discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur. This is a good action to take, as it shows that the Scrum Team is willing to inspect and adapt their process and improve their collaboration and communication. The Sprint Retrospective is an opportunity for the Scrum Team to identify the root causes of the problem and create a plan for implementing improvements in the next Sprint.

D) The Developers forecast 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 timebox for the Sprint Planning event is over, they start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint. This is also a good action to take, as it shows that the Scrum Team is flexible and adaptive, and does not let uncertainty or ambiguity prevent them from delivering value. The Developers can use the Sprint Goal as a guide to select and refine the Product Backlog items during the Sprint, and collaborate with the Product Owner to ensure that they are meeting the expectations and needs of the stakeholders.


The Scrum Guide, section 3.1 (The Sprint), page 8

The Scrum Guide, section 3.3 (The Sprint Goal), page 9

The Scrum Guide, section 3.5 (The Sprint Planning), page 10

The Scrum Guide, section 3.7 (The Sprint Retrospective), page 12

The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 2 (The Sprint), lesson 3 (The Sprint Goal), lesson 4 (Sprint Planning) and lesson 6 (The Sprint Retrospective)