Page: 1
/
15
Total 75 questions
Curious about Actual Scrum Professional Scrum Master (PSM-II) Exam Questions?
Here are sample Scrum Professional Scrum Master II (PSM-II) Exam questions from real exam. You can get more Scrum Professional Scrum Master (PSM-II) Exam premium practice questions at TestInsights.
Question 1
Respect is one of the five Scrum values. Which statements demonstrate respectful behavior in the Scrum Team?
(choose the best two answers)
Correct : A, C
Respect is one of the Scrum values that means recognizing the value of each individual and their contribution, trusting them to fulfill their tasks, listening to and considering their ideas, and acknowledging their accomplishments. Respect also means honoring the diversity of people, their experiences, and their opinions. Respect facilitates collaboration, learning, and creativity in the Scrum Team.
Some statements that demonstrate respectful behavior in the Scrum Team are:
Respect the accountabilities of the Scrum Team members. This means that each role in the Scrum Team has a clear set of responsibilities and expectations, and that other team members respect those boundaries and do not interfere with or undermine them. For example, the Product Owner is accountable for maximizing the value of the product and the work of the Developers, and the Developers respect that by following the Product Owner's guidance on what to work on and what not to work on. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, causing change that increases the productivity of the Scrum Team, and working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization. The Developers respect that by adhering to the Scrum framework, being open to feedback and improvement, and collaborating with other Scrum Teams when needed.
Respect people, their experience, diversity, and difference in opinion. This means that each person in the Scrum Team is valued as a skilled professional who brings unique perspectives and insights to the team. The team members respect each other's expertise, skills, and ideas, and are willing to learn from each other and from their stakeholders. They also respect that people may have different opinions or preferences on how to approach a problem or a solution, and they seek to understand those differences rather than dismiss or ignore them. They engage in constructive dialogue and respectful disagreement when necessary, and they support team decisions even if they are not their personal choices.
Some statements that do not demonstrate respectful behavior in the Scrum Team are:
Respect the Product Owner by letting them change the Sprint Goal during the Sprint. This is not respectful because it violates the Scrum framework and undermines the Developers' autonomy and commitment. The Sprint Goal is a shared objective that provides guidance to the Developers on why they are building an Increment. It is crafted by the Product Owner in collaboration with the Developers during Sprint Planning, and it remains fixed for the duration of the Sprint unless a significant change occurs that invalidates it. Allowing the Product Owner to change the Sprint Goal during the Sprint would disrupt the focus and alignment of the Developers, introduce uncertainty and confusion, and reduce transparency and accountability.
Respect stakeholder expectations that Scrum Teams will meet their forecast. This is not respectful because it implies that stakeholders have unrealistic or unreasonable expectations that are not based on empirical evidence or feedback. The forecast is a plan for what functionality will be delivered in an Increment by the end of a Sprint. It is based on what is known at Sprint Planning, but it is not a guarantee or a commitment. The forecast may change during the Sprint as new information emerges or as unforeseen challenges arise. The Scrum Team respects stakeholders by being transparent about their progress and any changes to their forecast, by delivering a valuable Increment at least by the end of every Sprint, by seeking feedback from stakeholders during Sprint Review, and by incorporating that feedback into future Sprints.
Start a Discussions
Submit Your Answer:
Question 2
In the Sprint Retrospective, there is discussion that the quality of the Increment is not sufficient tor going to production In response, a Scrum Team member points out the high velocity reached by the team. What are the two best actions tor the Scrum Master to take?
(choose the best two answers)
Correct : B, D
Some actions that the Scrum Master can take in this situation are:
Facilitate a discussion on how to improve the quality to a level sufficient for production, even if the measured velocity will drop in the next Sprint. This action will help the Scrum Team to identify and address the root causes of the quality issues, and to plan actions for improvement. The Scrum Master should encourage the Scrum Team to inspect their Definition of Done, their testing and quality assurance practices, their technical debt, and their collaboration with stakeholders. The Scrum Master should also help the Scrum Team to prioritize quality over quantity, and to understand that delivering a potentially releasable Increment at the end of every Sprint is one of the goals of Scrum.
Stress the value of working product over measured velocity. This action will help the Scrum Team to align their work with the Agile values and principles, and to focus on delivering value to the customers and users. The Scrum Master should remind the Scrum Team that velocity is not a goal or a measure of success, but a tool for planning and forecasting. The Scrum Master should also help the Scrum Team to avoid falling into the trap of velocity-driven development, where they sacrifice quality, sustainability, and customer satisfaction for higher numbers.
Some actions that the Scrum Master should not take in this situation are:
Agree and praise the Developers for their hard work, so they are motivated to do even more in the next Sprint. This action will not help the Scrum Team to improve their quality or effectiveness, but rather reinforce a false sense of achievement based on velocity. The Scrum Master should acknowledge and appreciate the Developers' efforts, but also challenge them to inspect and adapt their work processes and outcomes. The Scrum Master should also help the Developers to balance their motivation with realism, and to avoid overcommitting or overestimating their capacity.
Acknowledge the hard work, but remind the Developers that they need to improve to do even more in the next Sprint. This action will not help the Scrum Team to improve their quality or effectiveness, but rather put pressure on them to increase their velocity. The Scrum Master should not imply that doing more work is equivalent to doing better work, or that higher velocity is expected or desired. The Scrum Master should also help the Developers to avoid burnout, stress, and fatigue caused by unrealistic or unsustainable expectations.
The Sprint Retrospective - What It Is & Tips for Making the Most of Your Meeting | Scrum Alliance
How to Measure Sprint Velocity in Agile | Parabol
What is a Sprint Retrospective? - Zeolearn
What Is the Goal of Sprint Retrospective Meeting? | Wrike
What is a Sprint Retrospective? | Scrum.org
[Principles behind the Agile Manifesto]
[What is a Product Increment? | Scrum.org]
[Velocity-driven development: A trap waiting for you | Agile Alliance]
Start a Discussions
Submit Your Answer:
Question 3
You are the Scrum Master for four teams working from the same Product Backlog. Several of the Developers come to you complaining that work identified for the upcoming two Sprints will require full time commitment from Phil, an external specialist. As the Scrum Master what should you do to solve this upcoming problem?
(choose the best answer)
Correct : C
As the Scrum Master, your role is to serve the Scrum Team by helping them to work effectively and deliver value. You are not responsible for managing the work or assigning tasks to the Developers. You should respect the self-organization and autonomy of the Developers, and support them in finding their own solutions to the problem. You should also facilitate collaboration and communication among the Developers and with other stakeholders, such as Phil and the Product Owner.
Some reasons why the other options are not correct are:
A: Preparing the Sprint Backlogs each day for the teams so Phil can spend some time in each team. This option is not correct because it violates the Scrum framework and the Scrum Master role. The Sprint Backlog is owned and managed by the Developers, not by the Scrum Master. The Scrum Master should not interfere with or dictate how the Developers plan and execute their work. The Scrum Master should also not impose a solution that may not be optimal or feasible for the teams or for Phil.
B: Allocate Phil to one team per Sprint, so that over four Sprints every team will have had the support it requires. This option is not correct because it violates the Scrum framework and the Scrum Master role. The Scrum Master should not allocate resources or assign tasks to the teams or to Phil. The Scrum Master should also not impose a solution that may not be aligned with the Product Owner's priorities or the teams' needs.
D: Ask Phil for a plan to hire and train additional people in his domain, and in the meantime work with the Product Owner and Developers to re-prioritize the work so that tasks not depending on Phil can be done first. This option is not correct because it violates the Scrum framework and the Scrum Master role. The Scrum Master should not ask Phil to do something that may be beyond his authority or responsibility. The Scrum Master should also not work with the Product Owner and Developers to re-prioritize the work, as this is the Product Owner's accountability. The Scrum Master should respect the Product Owner's decisions on what is valuable and what is not, and support the Developers in delivering that value.
What is a Scrum Master? | Scrum.org
What is a Sprint Backlog? | Scrum.org
Who is responsible for dependency management? | Scrum.org
[Managing Dependencies in Scrum - Scrum Alliance]
Start a Discussions
Submit Your Answer:
Question 4
A Developer from the Scrum Team is always missing the Daily Scrum. She feels that if she is doing her job well, it does not matter whether she attends or not. The other Developers on the team have not done anything about it. As the Scrum Master how should you respond to this situation?
(choose the best answer)
Correct : B
As the Scrum Master, your role is to serve the Scrum Team by helping them to work effectively and deliver value. You are not responsible for managing the work or assigning tasks to the Developers. You should respect the self-organization and autonomy of the Developers, and support them in finding their own solutions to the problem. You should also facilitate collaboration and communication among the Developers and with other stakeholders.
Some reasons why option B is the correct answer are:
The Scrum Master should also help the Developers to come up with their own solutions on how to ensure full attendance and participation in the Daily Scrum. The Scrum Master should not impose or dictate a solution, but rather coach and guide the Developers to find what works best for them. The Scrum Master should also help the Developers to agree on some ground rules or norms for their Daily Scrum, such as when, where, and how to conduct it, what topics to discuss, and how to handle any issues or conflicts that may arise.
Some reasons why the other options are not correct are:
What is a Daily Scrum? | Scrum.org
What Is a Daily Standup? | A Guide to Running Effective Standup Meetings | Atlassian
Start a Discussions
Submit Your Answer:
Question 5
During the Sprint Retrospective, the newest developer says that his perspective and ideas have been ignored by the rest of the Developers throughout the Sprint What Scrum values are touched here?
(choose the best three answers)
Correct : B, D, E
The Scrum values of courage, openness, and respect are touched in this situation. Courage means that the Scrum Team members have the courage to do the right thing and work on tough problems, and also to speak up when they have concerns or disagreements. Openness means that the Scrum Team members and stakeholders agree to be open about all the work and the challenges with performing the work. Respect means that the Scrum Team members respect each other to be capable, independent people, and also respect the opinions and ideas of others.
In this case, the newest developer showed courage by expressing his feelings during the Sprint Retrospective, which is an opportunity for the Scrum Team to inspect itself and create a plan for improvements. The rest of the Developers should have been more open to listening to his perspective and ideas throughout the Sprint, as they might have valuable insights or suggestions for improving the product or the process. The Developers should also have respected the newest developer as a member of the team, and given him a fair chance to contribute and collaborate with them.
The Scrum Guide, November 2020, p. 13-14
What are the 5 Scrum Values?, Visual Paradigm, accessed on September 30, 2023
Scrum Values Poster, Scrum.org, accessed on September 30, 2023
Start a Discussions
Submit Your Answer:
All Official Question Types