Scrum PSM-II Professional Scrum Master II Exam Practice Test

The Scrum Master should do this because it is the most effective way to ensure that the Scrum Teams are self-organizing, cross-functional, and collaborative. The Scrum Master can help the Scrum Teams to understand the benefits of working together as one integrated team, rather than as separate component teams. The Scrum Master can also facilitate the communication and coordination among the Scrum Teams, and support them in resolving any dependencies or conflicts that may arise.

References:

• Scrum Guide 2020, page 7: “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint.”
• Scrum Guide 2020, page 7: “Scrum Teams are self-managing, meaning they internally decide who does what, when, and how.”
• Nexus Guide 2020, page 5: “When multiple Scrum Teams are working together on the same product, there are additional complexities that arise. These complexities can be reduced by having the teams adhere to a common definition of “Done” and a single Product Backlog.”

 The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work1. It is one of the five events of the Scrum framework and enables the three pillars of the empirical process of Scrum: transparency, inspection, and adaptation2. The Daily Scrum is not a status meeting, but a chance for the Developers to collaborate, coordinate, and plan their work3.

As a Scrum Master, you could help the Developers understand that lowering the frequency of communication will only increase the feeling of disconnect between the team members, especially when they are working from globally distributed locations. You could also coach the Developers on why a daily frequency is important as an opportunity to update the Sprint Plan and how it helps the team organize work toward achieving the Sprint Goal. You could suggest alternative conferencing tools or methods that are easily available and effective for the team. You could also facilitate the Daily Scrum by ensuring that it is positive, productive, and focused on the Sprint Goal.

Acknowledging and supporting this self-managing team’s decision might seem like a good option, but it would not help the team to improve their collaboration and alignment. Having the Developers vote to make sure there is consensus within the team might also seem like a democratic way to handle the situation, but it would not address the underlying issue of why the team wants to reduce the frequency of the Daily Scrum.

References:

• The Scrum Guide 2020, section “The Daily Scrum”
• What Is the Daily Scrum?, A Guide to the Daily Event - Scrum Alliance
• The Importance of Daily Scrum Meetings | Grata Software

Splitting a team into two teams is a major decision that should not be taken lightly. It may have implications for the product vision, the product backlog, the sprint goal, the sprint backlog, the definition of done, and the team dynamics. It may also reduce the effectiveness of the Scrum Team by creating dependencies, communication overhead, and coordination challenges. Therefore, before considering such a drastic measure, it is advisable to explore other options to improve the quality and efficiency of the Daily Scrum. One option is to ask for help from another Scrum Master who can observe the Daily Scrum and provide feedback and suggestions.

References:

• The Scrum Guide, section 3.2 (The Daily Scrum), page 9
• The Scrum Master Learning Path, module 4 (The Daily Scrum), lesson 4 (Common Challenges) and lesson 5 (Tips for an Effective Daily Scrum)

 As a Scrum Master, you could help the Product Owner by suggesting working with the program manager and the project managers of the other components on the ordering and the value of your open Product Backlog items to redefine the possible delivery date. This would allow you to collaborate with the stakeholders and align on the expectations and priorities of the product. You could also inspect and adapt your integration process and communication channels with the other teams to minimize the impact of changes and dependencies.

References:

• The Scrum Guide 2020, section “The Scrum Master”
• The Scrum Master Learning Path, module “The Scrum Master as a Coach”
• The Professional Scrum Master II Course, topic “Stakeholder Management”

C. Timeboxes encourage the people who are closest to the problem to create the best possible result in the time allotted, given the current context.

• This is true because timeboxes limit the amount of time that can be spent on an activity, which forces the Scrum Team to focus on the most valuable and feasible outcomes. Timeboxes also empower the Scrum Team to make decisions based on their own expertise and experience, rather than relying on external authorities or instructions12. D. Timeboxes help everyone focus on the same problem at the same time.
• This is true because timeboxes create a shared sense of urgency and alignment among the Scrum Team and the stakeholders. Timeboxes also enable frequent feedback and inspection, which help the Scrum Team adapt to changing requirements and expectations12.

References: 1: What Is Timeboxing in Scrum? - Visual Paradigm 2: What Is Timeboxing in Scrum and What Are the Benefits? Scrum Alliance

• This is a good option because the Scrum Master’s role is to help the Scrum Team understand and apply the Scrum framework and its principles12. The Scrum Master should also facilitate and enable the team’s self-organization and collaboration12. By coaching the Scrum Team, the Scrum Master can help them realize that the Daily Scrum is not a status update or a performance review, but a time to inspect and adapt their progress toward the Sprint Goal3 . D. Tell the Product Owner your concerns about how his behavior may impact the Developers, and ask him to stop attending the Daily Scrum for some time.
• This is another good option because the Scrum Master’s role is to protect the Scrum Team from external interference and distractions12. The Scrum Master should also coach the Product Owner on how to maximize the value of the product and collaborate effectively with the Developers12. By telling the Product Owner your concerns, you can help him understand that his behavior may create pressure, dependency, or resentment among the Developers, which can harm their motivation, creativity, and autonomy . By asking him to stop attending the Daily Scrum for some time, you can give the Developers some space to self-manage their work and communication.

References: 1: What is a Scrum Master? | Scrum.org 2: What is a scrum master? [+ Responsibilities] | Atlassian 3: What’s the role of the Product Owner at the Daily Scrum? | by Maarten Dalmijn | Serious Scrum | Medium : Scrum Guide | Scrum Guides : Product Owner’s Role in a Daily Scrum: How to Support the … - Eleken : The Power of Intrinsic Motivation - Forbes

 A self-managing Scrum Team is one that internally decides who does what, when, and how. It does not need external direction or supervision to accomplish its work. A self-managing Scrum Team can resolve conflicts and continue working, as this shows that the team members can collaborate effectively and handle disagreements without escalating them. Creativity flourishes and new possibilities are explored, as this shows that the team members are empowered to experiment and innovate, rather than following a fixed plan or process.

References:

• The Scrum Guide 20201, section “The Scrum Team”
• The Scrum Master Learning Path2, module “The Self-Managing Scrum Team”
• The Professional Scrum Master II Course3, topic “Self-Management”

Using Scrum does not ensure that adding more resources to a project proportionally increases the value delivered. In fact, adding more resources may have the opposite effect, as it can introduce more complexity, communication overhead, coordination challenges, and integration issues12. Scrum values quality over quantity, and focuses on delivering the most valuable and feasible outcomes in a given timebox3 . Scrum also encourages teams to be self-organizing and cross-functional, which means that they can work autonomously and collaboratively without relying on external resources or dependencies3 .

References: 1: Adding more resources in Scrum will proportionally increase the value … 2: The Mythical Man-Month - Wikipedia 3: Scrum - What is it, how it works, & how to start - Atlassian : How Scrum Teams can Complement Scrum by Adding Practices, Tools and …

The possible explanations for why this Scrum Team is struggling to craft a Sprint Goal are B, D, and E.

B. The Sprints are too long. A four-week Sprint is the maximum duration allowed by the Scrum Guide, and it may not be suitable for complex and uncertain work that requires frequent feedback and adaptation. A shorter Sprint may help the Scrum Team to focus on a clear and coherent Sprint Goal that aligns with the Product Goal and delivers a valuable Increment.

D. The Product Owner is not communicating the Product Goal that they want to achieve in upcoming Sprints. The Product Goal is a long-term objective for the Scrum Team that provides direction and purpose for their work. The Product Owner is responsible for communicating the Product Goal to the Developers and collaborating with them to create Sprint Goals that move them closer to the Product Goal. Without a clear Product Goal, the Scrum Team may lack a shared vision and end up working on unrelated items.

E. The Scrum Team is too big. The Scrum Guide recommends that the Scrum Team consists of 10 or fewer people, including the Scrum Master and the Product Owner. A larger team may have difficulties in collaborating effectively, self-organizing, and creating a meaningful Sprint Goal that reflects the collective commitment of the Developers. A smaller team may improve the communication, coordination, and cohesion among the Developers and help them to create and achieve a Sprint Goal.

References:

• The Scrum Guide, section 2.3 (The Scrum Team), page 7
• 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 4.1 (The Product Backlog), page 11
• The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 2 (The Sprint) and lesson 3 (The Sprint Goal)

• A: There is one Product Owner for each product (five in total). Each Product Owner may delegate to others for specific value, capabilities, and functionality within their product. The five Product Owners share and align work via Product Backlog. This is a reasonable alternative, as it allows each Product Owner to focus on one product and its vision, value proposition, and stakeholder needs. The Product Owner can also leverage the expertise and input of other people who can help with the product development, such as business analysts, domain experts, or user representatives. The five Product Owners can coordinate and collaborate with each other through the Product Backlog, which is a single source of truth for the product requirements and priorities.
• D: There is one Product Owner responsible for all five products. This person may delegate work to others for specific value, capabilities, and functionality within each product to scale their accountability. This is another reasonable alternative, as it allows one Product Owner to have a holistic view of the five products and their interdependencies, synergies, and trade-offs. The Product Owner can also delegate some of the work to other people who can act as proxies or representatives for the different aspects of the products, such as features, modules, or components. The Product Owner can still maintain the ultimate authority and responsibility for the Product Backlog and the product value delivery.

References:

• Scrum Guide 2020, page 7: “The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.”
• Scrum Guide 2020, page 8: “The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.”
• Professional Scrum Master II Course, page 22: “The Product Owner may delegate some of their work to others who can help them with the product development, such as business analysts, domain experts, or user representatives. However, the Product Owner remains accountable for the Product Backlog and its content.”
• Professional Scrum Master II Course, page 23: “The Product Owner may scale their role by working with other Product Owners who are responsible for different products, features, modules, or components. However, there should be only one Product Owner per product who has the final say on the product vision and value proposition.”

• B: Developers can artificially increase velocity by incurring technical debt. This is a true statement, as some Developers may choose to take shortcuts or compromise on quality in order to deliver more work in a Sprint. However, this is not a sustainable or ethical practice, as it will create more problems and costs in the future. The Scrum Master can help the Developers to avoid this temptation and focus on delivering value and quality instead.
• D: Velocity may unexpectedly drop when the Developers run into technical debt while attempting to complete new Product Backlog items. This is a true statement, as technical debt can act as a drag on the productivity and progress of the Developers. Technical debt can make the work more difficult, complex, or risky, and may require more time and effort to fix or refactor. The Scrum Master can help the Developers to identify and manage technical debt, and communicate its impact to the Product Owner and the stakeholders.

References:

• How Technical Debt Affects Your Velocity1
• Understanding the impact of technical debt on the capacity and velocity2

When scaling Scrum, it is important to have multiple Scrum Teams working from one Product Backlog, because this ensures that they are aligned on the same product vision, goal, and value12. Having one Product Backlog also helps to reduce duplication, inconsistency, and waste, and to optimize the flow of work and feedback12. The Product Owner is accountable for managing the Product Backlog and ensuring that it is transparent, ordered, and refined for the multiple Scrum Teams3 . The Scrum Teams collaborate with the Product Owner and each other to deliver a single integrated product Increment every Sprint3 .

References: 1: What is Scaling Scrum? | Scrum.org 2: Scaling Scrum with Nexus | Scrum.org 3: Scrum Guide | Scrum Guides : The Nexus Framework for Scaling Scrum: Continuously Delivering an Integrated Product with Multiple Scrum Teams

 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.

References:

• 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]

• A: Arrange one-on-one coaching sessions where concerns the Scrum Master has identified can be discussed. This is a good way to provide individual feedback and guidance to the Scrum Team members and other people involved in the Scrum process. The Scrum Master can help them overcome any challenges or misunderstandings they may have about Scrum.
• C: Schedule group training about Scrum. This is a good way to educate and inform a larger audience about the principles and practices of Scrum. The Scrum Master can use this opportunity to share their knowledge and experience with Scrum, and answer any questions or concerns that may arise.
• E: Educate stakeholders and customers about Scrum. This is a good way to ensure that the people who have a stake in the product or service understand the benefits and expectations of Scrum. The Scrum Master can help them appreciate the value of empirical feedback, transparency, and collaboration that Scrum provides.

References:

• Scrum Guide 2020, page 6: “The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.”
• Professional Scrum Master II Course, page 8: “The role of the Scrum Master is to help everyone involved in creating products with Scrum to understand, apply, and improve upon the use of the framework.”

 Done means that the Increment is in a usable condition and meets the Scrum Team’s Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. Having an Increment that could be released to end users means that it is potentially releasable, which is one of the goals of Scrum. All work performed meets the Definition of Done means that the Developers have ensured that every Product Backlog item selected for the Sprint conforms to the agreed quality standards.

References:

• The Scrum Guide, November 2020, p. 10-11
• What is a Definition of Done?, Scrum.org, accessed on September 30, 2023
• DONE Understanding Of The Definition Of "Done”, Scrum.org, December 16, 2019

The Scrum Value of openness can easily impact all of the aspects listed in the question. Openness means that the Scrum Team and the stakeholders agree to be transparent about their work, their challenges, their learnings, and their progress. This fosters a culture of collaboration, trust, feedback, and continuous improvement. Openness also helps to ensure that the product quality meets the expectations of the customers and the stakeholders, and that the product is delivered in a timely manner. Openness also contributes to employee satisfaction, as it allows the Scrum Team members to express their opinions, share their ideas, and learn from each other.

References:

• The Scrum Guide, section 2.2 (Scrum Values), page 6
• The Scrum Master Learning Path, module 1 (Scrum Theory), lesson 3 (Scrum Values)

A Definition of Ready (DoR) is a set of agreements that lets everyone know when a product backlog item is ready to be taken into a sprint12. A DoR can help the Scrum Team ensure that the product backlog items are clear, feasible, valuable, and testable12. However, a DoR does not necessarily maximize the team’s velocity, nor does it ensure that the sprint planning can end within its timebox. Velocity is a measure of how much work a team can complete in a sprint, and it depends on many factors, such as the team’s capacity, skills, collaboration, and quality standards3 . A DoR may help the team avoid wasting time on unclear or incomplete items, but it does not guarantee that the team can deliver more value or faster. Similarly, a DoR may help the team prepare for the sprint planning, but it does not guarantee that the team can finish the planning within its timebox. The sprint planning is an empirical and collaborative event, where the team inspects the product backlog, negotiates with the product owner, and crafts a sprint goal and a sprint backlog . A DoR may reduce some uncertainties and risks, but it does not eliminate them. The team still needs to adapt to changing requirements and expectations, and make realistic and meaningful commitments .

References: 1: What is Definition of Ready in Scrum? - Visual Paradigm 2: Walking Through a Definition of Ready | Scrum.org 3: What is Velocity in Agile? - Atlassian : Velocity in Scrum | Scrum.org : Sprint Planning | Scrum.org : Sprint planning - Atlassian

The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Product Owner is also accountable for managing the Product Backlog, which is an ordered list of what is needed in the product. The Product Owner should collaborate with the Developers and the stakeholders to create and refine the Product Backlog, as well as to define and communicate the product vision and goals. Therefore, as a Scrum Master, you should direct the new Product Owner towards focusing on:

• Building a good relationship with the stakeholders of the product (A), which is a valid option as it helps the Product Owner to understand and align with the changing organizational or market expectations, as well as to invite and receive feedback from the appropriate stakeholders during the Sprint Review, which is an event that inspects the outcome of the Sprint and determines future adaptations.
• Relying on others in the Scrum Team and the stakeholders to formulate the Product Backlog (D), which is another valid option as it helps the Product Owner to leverage the functional and business insights of the Developers and the stakeholders, who are more familiar with the product and the customer needs. By questioning them and working with them, the Product Owner will quickly become more productive and effective.

The other options are not correct because they:

• Inform the Product Owner that it is important that the Developers are updated on changing business priorities on a daily basis at the Daily Scrum (B), which is not a good option as it shows a misunderstanding of the purpose and format of the Daily Scrum, which is an event for the Developers to inspect their progress and plan their work for the next 24 hours, not a status report or a meeting for changing requirements or scope. The Product Owner should respect and support the Developers’ commitment to their Sprint Goal and Sprint Backlog, and only introduce changes that do not endanger them.
• Tell the Product Owner to make sure that there are no ambiguities or possible misunderstandings in the items on the Product Backlog by capturing the functional requirements during an analysis phase ©, which is not a good option as it shows a misunderstanding of the nature and process of the Product Backlog, which is a dynamic and emergent artifact that can change as more is learned about the product, users, market, and technology. The Product Owner should collaborate with the Developers to refine and clarify the Product Backlog items throughout the product development, not create detailed documents that are considered as final outputs of analysis Sprints.

References: : [Scrum Guide], The Product Owner : [Scrum Guide], The Product Backlog : [Scrum Guide], The Sprint Review : [Scrum Guide], The Scrum Master : [Scrum Guide], The Developers : [Scrum Guide], The Daily Scrum

A Scrum Master is not a management position in the traditional sense of the word. A Scrum Master does not have authority over the team members, the product, or the project. A Scrum Master is a servant leader who helps the team self-organize, collaborate, and deliver value. A Scrum Master is accountable for managing the Scrum process, ensuring that the team follows the Scrum values and principles, and facilitating the team’s interactions with stakeholders and the organization. A Scrum Master is also accountable for removing organizational impediments that limit the team’s progress and productivity, such as bureaucracy, silos, or conflicts. A Scrum Master is not accountable for reporting on the performance of a team, managing the project plan and the project deliverables, or managing the capacity and utilization of the Developers. These are responsibilities of the Product Owner, the Developers, or other roles in the organization.

References:

• Scrum Guide 2020, section “The Scrum Master”, “The Scrum Team”.
• What is a scrum master? [+ Responsibilities] | Atlassian, section “Scrum master responsibilities”.
• Scrum Master Roles and Responsibilities [2023] | Simplilearn, section “What Does a Scrum Master Do?”, “Scrum Master Responsibilities”.

B. Developers with an interest in Stella’s domain could volunteer to take on this work in their respective Scrum Teams.

• This is a good solution because it is consistent with the Scrum value of commitment, which means that the Scrum Team members are willing to learn new skills and take on new challenges to deliver value12. By volunteering to take on this work, the Developers can reduce the dependency on Stella, increase their cross-functionality, and collaborate more effectively within and across the Scrum Teams34. F. Ask Stella for a plan to hire and train additional people in her domain, and in the meantime work with the Product Owner and Scrum Teams to re-prioritize the work so that tasks not depending on Stella can be done first
• This is another good solution because it is consistent with the Scrum principle of empiricism, which means that the Scrum Team learns and adapts based on the actual outcomes and feedback, rather than following a predefined plan12. By asking Stella for a plan to hire and train additional people, the Scrum Master can help address the root cause of the dependency and create more capacity and diversity in Stella’s domain. By working with the Product Owner and Scrum Teams to re-prioritize the work, the Scrum Master can also help optimize the value and feasibility of the product backlog items, and enable the Scrum Teams to deliver valuable and functional increments every Sprint34. G. Create a team with Stella and identify people from the Scrum Teams to temporarily work in Stella’s domain to learn to better serve the existing teams
• This is also a good solution because it is consistent with the Scrum value of respect, which means that the Scrum Team members appreciate and value each other’s skills and perspectives12. By creating a team with Stella, the Scrum Master can acknowledge and leverage Stella’s expertise and experience in her domain. By identifying people from the Scrum Teams to temporarily work in Stella’s domain, the Scrum Master can also facilitate knowledge transfer and skill development among the team members, which can improve their self-organization and collaboration34.

References: 1: Scrum Values | Scrum.org 2: Scrum Values - Atlassian 3: Scrum Guide | Scrum Guides 4: Scrum - What is it, how it works, & how to start - Atlassian