When multiple Scrum Teams are working on the same product, should all of their Increments be
integrated every Sprint?
(choose the best answer)
A
Explanation:
When multiple Scrum Teams are working on the same product, they should integrate their
Increments every Sprint because:
It allows them to accurately inspect what is done and what is potentially releasable. By integrating
their work frequently, they can ensure that the product is in a usable and valuable state at the end of
each Sprint, and that it meets the Definition of Done and the Sprint Goal.
It enables them to adapt to changes and feedback faster. By integrating their work frequently, they
can reduce the complexity and risk of integration, and discover and resolve any issues or
dependencies sooner. They can also incorporate any new insights or requirements into their Product
Backlog and Sprint Planning.
It fosters collaboration and alignment among the teams. By integrating their work frequently, they
can share their learnings and best practices, and coordinate their efforts towards a common vision
and goal. They can also leverage the collective intelligence and creativity of the teams to deliver a
better product.
Reference:
Scrum Guide 2020, page 10: “When a Product Backlog item or an Increment is described as “Done”,
everyone must understand what “Done” means. Although this varies significantly per Scrum Team,
members must have a shared understanding of what it means for work to be complete, to ensure
transparency.”
Scrum Guide 2020, page 10: “The moment a Product Backlog item meets the Definition of Done, an
Increment is born.”
Scrum Guide 2020, page 10: “Each Increment is additive to all prior Increments and thoroughly
verified, ensuring that all Increments work together.”
Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially
releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and
the presentation of the Increment is intended to elicit feedback and foster collaboration.”
A Scrum Master is working with a Scrum Team that has Developers in different physical
locations. The Developers meet in a variety of meeting rooms and have much to do logistically
(for example: reserve meeting rooms and set up conference calls) before the Daily Scrum.
What action should the Scrum Master take?
(choose the best answer)
A
Explanation:
The Scrum Master should allow the Developers to self-manage and determine for themselves what
to do because:
It respects the autonomy and empowerment of the Developers. The Developers are accountable for
organizing and managing their own work, and they are the best people to decide how to conduct
their Daily Scrum. The Scrum Master should not impose or dictate how the meeting should be set up
or run, as that would undermine the self-organization and collaboration of the Developers.
It supports the continuous improvement and adaptation of the Developers. The Developers are
expected to inspect and adapt their process and practices, and to find ways to overcome any
challenges or impediments they face. The Scrum Master should not solve the problems for them, but
rather facilitate their problem-solving and learning abilities.
It aligns with the role and responsibilities of the Scrum Master. The Scrum Master is responsible for
promoting and supporting Scrum, and for helping everyone understand and enact Scrum theory,
values, principles, and practices. The Scrum Master is not a manager or a leader of the Developers,
but rather a servant-leader who enables them to work effectively.
Reference:
Scrum Guide 2020, page 6: “Developers are the people in the Scrum Team that are committed to
creating any aspect of a usable Increment each Sprint.”
Scrum Guide 2020, page 6: “The Developers are accountable for … organizing and managing their
work.”
Scrum Guide 2020, page 12: “The Developers can select whatever structure and techniques they
want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an
actionable plan for the next day of work. This creates focus and improves self-management.”
Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are
present, the Scrum Master ensures that they do not disrupt the meeting.”
Scrum Guide 2020, page 7: “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.”
Which statement best describes Scrum?
(choose the best answer)
C
Explanation:
The best statement that describes Scrum is: A framework to generate value through adaptive
solutions for complex problems.
Scrum is a lightweight framework that helps people, teams, and organizations to deliver valuable
products in complex and uncertain environments.
Scrum is based on empiricism, which means that knowledge comes from experience and making
decisions based on what is observed. Scrum employs an iterative and incremental approach to
optimize predictability and control risk.
Scrum is not a defined and predictive process, a complete methodology, or a cookbook that defines
best practices. Scrum provides the minimal boundaries within which teams can self-organize and
create innovative solutions. Reference: Scrum Guide, Section 1 (Definition of Scrum) and Section 2
(Uses of Scrum)
Why is the Daily Scrum held at the same time and same place?
(choose the best answer)
D
Explanation:
The Daily Scrum is held at the same time and same place because:
The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the
Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They
can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the
Developers can ensure that everyone is aware of when and where the meeting takes place, and that
everyone has an opportunity to participate and share their progress, plans, and challenges. They can
also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the
Developers can create a safe and comfortable space for them to communicate, interact, and
collaborate with each other. They can also build trust, rapport, and accountability among themselves,
and foster a sense of team spirit and ownership.
Reference:
Scrum Guide 2020, page 12: “The Daily Scrum is held at the same time and place each day to reduce
complexity.”
Scrum Guide 2020, page 12: “The purpose of the Daily Scrum is to inspect progress toward the Sprint
Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.”
Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are
present, the Scrum Master ensures that they do not disrupt the meeting.”
In order to maximize the value of the product, a Product Owner needs awareness of the following:
(choose the best answer)
E
Explanation:
In order to maximize the value of the product, a Product Owner needs awareness of the following:
Competitive research. The Product Owner should be aware of the competitive landscape and the
market trends that affect the product. They should know who are the competitors, what are their
strengths and weaknesses, how do they differentiate themselves, and what are their strategies and
goals. This can help the Product Owner to identify opportunities, threats, and gaps in the market,
and to position the product accordingly.
Customer feedback. The Product Owner should be aware of the customer needs, preferences,
expectations, and satisfaction with the product. They should collect and analyze feedback from
various sources, such as surveys, interviews, reviews, analytics, etc. This can help the Product Owner
to validate assumptions, test hypotheses, measure outcomes, and discover insights that can inform
the product decisions and priorities.
Product vision. The Product Owner should be aware of the product vision, which is a clear and
compelling statement of the desired future state of the product. The product vision describes the
purpose, value proposition, target audience, and key features of the product. It also aligns with the
organizational vision and mission. This can help the Product Owner to communicate and inspire the
stakeholders, to guide and focus the Scrum Team, and to evaluate and adjust the product direction.
Forecasting & feasibility. The Product Owner should be aware of the forecasting and feasibility of the
product. They should estimate and plan the scope, time, cost, quality, and risk of delivering the
product. They should also assess the technical, operational, legal, ethical, and social feasibility of
developing and releasing the product. This can help the Product Owner to optimize the value of the
work of the Scrum Team, to manage expectations and dependencies, and to handle uncertainties
and changes.
Reference:
Scrum Guide 2020, page 6: “The Product Owner is accountable for maximizing the value of the
product resulting from the work of the Scrum Team.”
Scrum Guide 2020, page 11: “The Product Goal describes a future state of the product which can
serve as a target for the Scrum Team to plan against.”
Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog
management, which includes … optimizing the value of the work the Scrum Team performs.”
During a Sprint, when is new work or further decomposition of work added to the Sprint
Backlog?
(choose the best answer)
D
Explanation:
New work or further decomposition of work is added to the Sprint Backlog as soon as possible after
it is identified because:
It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and
update throughout the Sprint, based on their progress, learnings, and changes. By adding new work
or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the
Sprint Backlog is transparent, accurate, and up-to-date.
It enables the Developers to self-manage their work. The Developers are accountable for organizing
and managing their own work, and they have the authority to change the Sprint Backlog as needed.
By adding new work or further decomposition of work to the Sprint Backlog promptly, the
Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.
It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides
guidance and focus for the Developers throughout the Sprint. By adding new work or further
decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is
aligned with and contributes to the Sprint Goal.
Reference:
Scrum Guide 2020, page 6: “Developers are the people in the Scrum Team that are committed to
creating any aspect of a usable Increment each Sprint.”
Scrum Guide 2020, page 6: “The Developers are accountable for … organizing and managing their
work.”
Scrum Guide 2020, page 10: “The Sprint Goal is a single objective for the Sprint.”
Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially
releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
Scrum Guide 2020, page 14: “The Sprint Backlog is composed of … all of the work needed to deliver a
product Increment that meets the Definition of Done.”
Scrum Guide 2020, page 14: “The Developers can change the content of the Sprint Backlog
throughout the Sprint as more is learned.”
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of
inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?
(choose the best answer)
E
Explanation:
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually
keeping it up to date with the most recent insights because:
It reflects the current state of the product and the work. The Product Backlog is a dynamic and
emergent artifact that represents all the possible features, functions, requirements, enhancements,
and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can
ensure that the Product Backlog is accurate, complete, and relevant.
It enables the Product Owner to optimize the value of the product and the work of the Scrum Team.
The Product Owner is accountable for effective Product Backlog management, which includes
ordering, refining, and communicating the Product Backlog items. By updating it frequently, the
Product Owner can incorporate new learnings, feedback, opportunities, and changes into the
product decisions and priorities.
It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product
Backlog is a source of information and transparency for everyone involved in the product
development. By updating it frequently, the Scrum Team and the stakeholders can inspect the
progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
Reference:
Scrum Guide 2020, page 10: “The Product Backlog is an emergent, ordered list of what is needed to
improve the product.”
Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog
management, which includes … ensuring that the Product Backlog is transparent, visible and
understood.”
Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole
responsibility of the Product Owner. They order Product Backlog items to best achieve goals and
missions.”
Scrum Guide 2020, page 11: “Higher ordered Product Backlog items are clearer and more refined
than lower ordered ones.”
Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and
the presentation of the Increment is intended to elicit feedback and foster collaboration.”
Which three of the following are true about Scrum?
(choose the best three answers)
B, C, E
Explanation:
The following are true about Scrum:
Scrum is based on empiricism and lean thinking. Empiricism is the principle of making decisions
based on what is observed and experienced, rather than on theory or speculation. Lean thinking is
the philosophy of eliminating waste and maximizing value in any process or system. Scrum applies
these concepts by providing a framework for inspecting and adapting the product and the process,
and by focusing on delivering the most valuable features to the customers and stakeholders.
Scrum is a framework for developing and sustaining complex products. A complex product is one that
has unpredictable or unknown aspects that require creativity, experimentation, and adaptation to
deliver. A framework is a set of minimal and essential rules and roles that provide structure and
guidance, but leave room for flexibility and innovation. Scrum provides such a framework for teams
to collaborate and deliver complex products iteratively and incrementally, while embracing change
and feedback.
Each component of Scrum serves a specific purpose and is essential to Scrum’s success and your
usage of Scrum to develop complex products. Scrum consists of three roles (Product Owner, Scrum
Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint
Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). Each of these
components has a clear definition, accountability, and goal that contributes to the overall
effectiveness and value of Scrum. Removing or changing any of these components may cause the
benefits of Scrum to be lost or diminished.
Reference:
Scrum Guide 2020, page 3: “Scrum is founded on empiricism and lean thinking.”
Scrum Guide 2020, page 3: “Scrum is a lightweight framework that helps people, teams and
organizations generate value through adaptive solutions for complex problems.”
Scrum Guide 2020, page 4: “Each component within the framework serves a specific purpose and is
essential to Scrum’s success and usage.”
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Select two statements
that explain what done means.
(choose the best two answers)
A, D
Explanation:
A Scrum Team is required to deliver a done Increment by the end of a Sprint. Done means:
No work is left to meet the 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. It is a shared
understanding among the Scrum Team and the stakeholders of what it means for work to be
complete. It may include criteria such as coding standards, testing, documentation, security,
performance, etc. If a Product Backlog item or an Increment does not meet the Definition of Done, it
cannot be released or presented at the Sprint Review.
Ready to be released to end users. The Increment is a concrete output of the Sprint that adds value
to the product. It is a potentially releasable functionality that adheres to the Scrum Team’s current
Definition of Done. It is not necessarily released at the end of each Sprint, but it must be in a state
that allows for immediate release if the Product Owner decides so. The Increment should also align
with the Sprint Goal and the Product Goal, and satisfy the needs and expectations of the customers
and stakeholders.
Reference:
Scrum Guide 2020, page 10: “The Definition of Done is a formal description of the state of the
Increment when it meets the quality measures required for the product.”
Scrum Guide 2020, page 10: “The moment a Product Backlog item meets the Definition of Done, an
Increment is born.”
Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially
releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
In accordance with Scrum theory, how should a group of 100 people be divided into multiple
Scrum Teams?
(choose the best answer)
C
Explanation:
In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum
Teams by understanding the product, the product vision and the rules of the Scrum framework, and
then dividing themselves into teams because:
It respects the self-organization and empowerment of the people. The people are the ones who have
the knowledge, skills, and experience to create and deliver the product. They are also the ones who
will work together as Scrum Teams, collaborating and coordinating their efforts. Therefore, they
should have the autonomy and authority to decide how to form their teams, based on their
preferences, interests, and capabilities.
It supports the alignment and coherence of the Scrum Teams. The people should have a clear and
shared understanding of the product, the product vision, and the rules of the Scrum framework
before forming their teams. This can help them to align their goals and missions, to ensure that they
are working on the same product and towards the same vision. It can also help them to follow the
same principles and practices of Scrum, to ensure that they are working effectively and consistently.
It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a
way that maximizes their collaboration and synergy. This can mean choosing team members that
complement each other’s skills and strengths, that have good rapport and trust, that can
communicate and coordinate well, and that can deliver a valuable Increment each Sprint.
Reference:
Scrum Guide 2020, page 5: “Scrum Teams are cross-functional, meaning the members have all the
skills necessary to create value in each Sprint.”
Scrum Guide 2020, page 5: “Scrum Teams are self-managing, meaning they internally decide who
does what, when, and how.”
Scrum Guide 2020, page 9: “Multiple Scrum Teams working together on a product use one Product
Backlog.”
Scrum Guide 2020, page 9: “The Product Owner is one person, not a committee.”