True or False: When scaling Scrum it is important to have multiple Scrum Teams working from one
Product Backlog
A
Explanation:
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
.
Reference: 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
You are the Scrum Master for four Scrum 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 Stella, an external specialist who is not a member of any of the
four Scrum Teams. What would you consider acceptable solutions for the problem?
(choose the best three answers)
BFG
Explanation:
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
.
Reference: 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
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)
CD
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 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 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 of openness, 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
.
Reference: 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
Another team's Scrum Master seeks your advice. The Daily Scrum always runs longer than 15
minutes. The Developers suggest splitting the Scrum Team into two teams. What is your response?
(choose the best answer)
A
Explanation:
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.
Reference:
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)
You are a Scrum Master helping to establish five Scrum Teams that will be building a product.
You discuss with them the high level of integration that the product Increment will require by the
end of their first Sprint. It is a highly anticipated product, both by consumers and by the organization.
Of the options raised by the future Scrum Team members, which option do you encourage?
(choose the best answer)
D
Explanation:
The Scrum Guide states that “the moment a Product Backlog item meets the Definition of Done, an
Increment is born” and that “the Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous Sprints”. Therefore, to deliver a
product Increment that is integrated and potentially releasable, all Scrum Teams must have a shared
understanding of what “Done” means and ensure that their work meets that standard. This also
enables transparency, inspection, and adaptation across the Scrum Teams.
Reference:
The Scrum Guide, section 3.4 (The Increment), page 10
The Scrum Master Learning Path, module 5 (The Increment), lesson 1 (What is an Increment?) and
lesson 2 (Definition of Done)
What can the Scrum Value of openness easily impact?
(choose the best answer)
F
Explanation:
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.
Reference:
The Scrum Guide, section 2.2 (Scrum Values), page 6
The Scrum Master Learning Path, module 1 (Scrum Theory), lesson 3 (Scrum Values)
Your Scrum Team has been working together for over a dozen Sprints. The Scrum Team consists of 10
members. Each Sprint takes four weeks. As a Scrum Master, you observe that the Developers are
hardly collaborating; during the Sprint, members are primarily working on their own items. You also
notice that the items on the Sprint Backlog are mostly unrelated. You suspect that the lack of a Sprint
Goal might be the cause.
Although you have encouraged the use of a Sprint Goal, both the Product Owner and the Developers
have concluded that they are unable to create Sprint Goals based on the wide variety of items on
their Product Backlog.
What might explain why this Scrum Team is struggling to craft a Sprint Goal?
(choose all that apply)
BDE
Explanation:
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.
Reference:
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)
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)
AD
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.
Reference:
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)
At the seventh Sprint Review, the stakeholders seem disappointed and angry. When asked about it,
they say the product being built will not meet their needs and will cost more than they anticipated
spending. What factors may have led to this?
(choose the best three answers)
ADE
Explanation:
A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and
evaluate progress. This is a possible factor that may have led to the disappointment and anger of the
stakeholders. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate
to inspect the product Increment and adapt the Product Backlog based on feedback and new
insights. If the stakeholders do not participate actively in the Sprint Review, they may miss the
opportunity to provide input, voice their concerns, and influence the direction of the product
development.
D) The Scrum Master has not ensured transparency. This is another possible factor that may have led
to the disappointment and anger of the stakeholders. The Scrum Master is accountable for
establishing and promoting transparency among the Scrum Team and the stakeholders, by ensuring
that everyone has a clear and common understanding of the product vision, the Product Goal, the
Product Backlog, the Sprint Goal, the Sprint Backlog, and the Definition of Done. Without
transparency, there may be misalignment, confusion, or unrealistic expectations among the
stakeholders regarding the product being built.
E) The Product Owner has not been interacting frequently with the stakeholders and kept them
aware of the progress of the project. This is also a possible factor that may have led to the
disappointment and anger of the stakeholders. The Product Owner is responsible for engaging with
the stakeholders regularly and communicating the value, scope, and status of the product
development. The Product Owner should also seek feedback from the stakeholders and incorporate
it into the Product Backlog refinement and ordering. If the Product Owner does not interact
frequently with the stakeholders, they may feel disconnected, ignored, or dissatisfied with the
product being built.
Reference:
The Scrum Guide, section 2.3 (The Scrum Team), page 7
The Scrum Guide, section 3.6 (The Sprint Review), page 11
The Scrum Guide, section 4.1 (The Product Backlog), page 11
The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 5 (The Sprint Review)
and lesson 6 (The Sprint Retrospective)
You have just been hired as a Scrum Master by a company new to Scrum. The company wants to use
Scrum to build a new product that was conceived by the product management department. You will
be the Scrum Master of two new teams that will build a first version of the product. The product
management department assigns two new Product Owners, but wants more advice about the
required participation with the new Scrum Teams. Which two suggestions would you offer?
(choose the best two answers)
AD
Explanation:
A) Having one Product Owner will improve the clarity of accountability to the teams and to the
product management department. This is a good suggestion, as it ensures that there is a single
person who is responsible for maximizing the value of the product and managing the Product
Backlog. Having one Product Owner also avoids confusion, duplication, or conflict among multiple
Product Owners who may have different visions, priorities, or expectations for the product.
D) A single Product Backlog should be maintained holding all requirements for the new product. This
is also a good suggestion, as it ensures that there is a single source of truth for the product
requirements and that they are transparent and visible to all stakeholders. Having a single Product
Backlog also enables the Product Owner to order the items based on their value, risk, dependency,
and urgency, and to collaborate with the Scrum Teams to select and refine the items for each Sprint.
Reference:
The Scrum Guide, section 2.3 (The Scrum Team), page 7
The Scrum Guide, section 4.1 (The Product Backlog), page 11
The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 4 (Sprint Planning) and
lesson 5 (The Sprint Review)