When should the Product Owner update the project plan?
(choose the best answer)
B
Explanation:
The Product Owner is responsible for managing and refining the Product Backlog, which is the single
source of truth for the plan of the product development. The Product Backlog is a living artifact that
changes as the product and the market evolve. The Product Owner updates the Product Backlog
continuously based on feedback, learning, and stakeholder needs. There is no separate project plan
document in Scrum.
Reference:
[Scrum Guide], section 3.1: “The Product Backlog is an emergent, ordered list of what is needed to
improve the product.”
[Professional Scrum Product Owner], chapter 5: “The Product Backlog represents everything
necessary to develop and launch a successful product.”
[What is a Product Backlog?]: “The Product Backlog is a list of all things that need to be done within
the project.”
True or False: Dependencies could influence how the Product Owner orders Product Backlog items.
A
Explanation:
Correct Answer : True
Dependencies are relationships between Product Backlog items that affect their order of
implementation. For example, a Product Backlog item may depend on another one to be completed
first, or it may have a dependency on a third-party system or resource. Dependencies could influence
how the Product Owner orders Product Backlog items, as they may introduce risks, constraints, or
uncertainties that affect the value delivery. The Product Owner should try to minimize dependencies
and order the Product Backlog items in a way that maximizes value and minimizes waste.
Reference:
[Professional Scrum Product Owner], chapter 6: “Dependencies are relationships between Product
Backlog items that affect their order of implementation.”
[Managing Dependencies on Agile Projects]: “Dependencies can have a significant impact on the
delivery of value.”
Which are appropriate topics for discussion in a Sprint Retrospective?
(choose the best three answers)
ACD
Explanation:
Correct Answers : A, C, and D .
The Sprint Retrospective is an event where the Scrum Team reflects on how they worked together in
the last Sprint and identifies ways to improve their collaboration, processes, and quality. Therefore,
appropriate topics for discussion in a Sprint Retrospective are:
Team relations: The Scrum Team should discuss how they communicated, interacted, and supported
each other during the Sprint. They should celebrate their successes, acknowledge their challenges,
and address any conflicts or issues that arose. They should also share feedback, appreciation, and
suggestions for improvement with each other.
How the Scrum Team does its work: The Scrum Team should inspect the methods, tools, and
practices they used to deliver the product increment. They should evaluate what worked well and
what could be improved. They should also identify any impediments, risks, or dependencies that
affected their work and how they handled them.
Definition of Done: The Scrum Team should review their Definition of Done and check if it is still
relevant, clear, and achievable. They should also assess how well they adhered to it and if they
delivered a potentially releasable product increment that meets the quality standards. They should
also consider if they need to update or adapt their Definition of Done based on new insights or
feedback.
The following topics are not appropriate for discussion in a Sprint Retrospective:
The value of work currently represented in the Product Backlog: The value of the Product Backlog
items is the responsibility of the Product Owner, who should continuously refine and order them
based on stakeholder needs and feedback. The value of the Product Backlog items is not directly
related to how the Scrum Team works together and does not affect their improvement actions for
the next Sprint.
Arranging the Sprint Backlog for the next Sprint: The Sprint Backlog is the plan for the next Sprint that
is created by the Scrum Team during the Sprint Planning event. The Sprint Backlog is based on the
Product Backlog items that are selected for the next Sprint and how the Developers intend to
accomplish them. The Sprint Retrospective is not a planning event but a reflection event that focuses
on the past Sprint.
Reference:
[Scrum Guide], section 3.5: “The purpose of the Sprint Retrospective is to plan ways to increase
quality and effectiveness.”
[Professional Scrum Product Owner], chapter 7: “The Sprint Retrospective is an opportunity for the
Scrum Team to inspect itself and create a plan for improvements to be enacted during the next
Sprint.”
What is a Sprint Retrospective? | Scrum.org
: “During each Sprint Retrospective, the Scrum Team
plans ways to increase product quality by improving work processes or adapting the definition of
“Done” if appropriate and not in conflict with product or organizational standards.”
The Sprint Retrospective - What It Is & Tips for Making the Most of Your Meeting
: “The focus is on
how the team worked together in the last sprint, including: Communication Teamwork Process Tools
Systems Work environment Missing competencies Collaboration with external parties”
Five new Scrum Teams have been created to build one product. A few of the Developers on one of
the Scrum Teams ask the Scrum Master how to coordinate their work with the other teams. What
should the Scrum Master do?
(choose the best answer)
A
Explanation:
Correct Answer : A) Teach them that it is their responsibility to work with the
Explanation:other teams to create an integrated Increment that is inclusive of all five team’s work.
According to the Scrum Guide, the Scrum Team is responsible for all product-related activities,
including coordination and integration with other teams. The Scrum Master should teach the
Developers how to work with the other teams to create a potentially releasable product increment
that meets the Definition of Done and the Product Goal. One way to facilitate this coordination is to
use a Scrum of Scrums meeting, which is a daily or periodic meeting where representatives from
each team share their progress, plans, and impediments. The Scrum of Scrums meeting is not
mandatory, but it can help the teams align their work and resolve dependencies.
The other options are not correct because they violate the principles of Scrum, such as self-
management, empiricism, and transparency:
B) Collecting the Sprint tasks from the teams and merging them into a consolidated plan for the
entire Sprint is a centralized and controlled way of coordination that undermines the self-
management and autonomy of the teams. The Scrum Master should not act as a project manager or
a coordinator, but as a servant-leader and a coach who enables the teams to manage their own
work.
C) Visiting the five teams each day to inspect that their Sprint Backlogs are aligned is a
micromanagement and inspection approach that does not respect the trust and transparency of the
teams. The Scrum Master should not interfere with the work of the teams, but support them in
creating a shared understanding of the product vision, goals, and requirements.
D) Teaching the Product Owner to work with the lead developers on ordering Product Backlog in a
way to avoid too much overlap during a Sprint is a suboptimal and inefficient way of coordination
that does not leverage the collective intelligence and creativity of the teams. The Product Owner
should not rely on a few individuals to order the Product Backlog, but collaborate with all the teams
and stakeholders to maximize value delivery.
Reference:
[Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from
stakeholder collaboration, verification, maintenance, operation, experimentation, research and
development, and anything else that might be required.”
Scrum Of Scrums - Guide to Agile Scaling Frameworks - Agilest®
: “The coordination of the various
teams is done in a Scrum of Scrums meeting which can be held daily, twice a week, or at a minimum,
once a week. Each Scrum team has its ScrumMaster or a designated team member attend the Scrum
of Scrum meeting as its representative.”
When does a Developer become accountable for the value of a Product Backlog item selected for the
Sprint?
(choose the best answer)
D
Explanation:
Correct Answer: D) Never. The entire Scrum Team is accountable for creating
Explanation:value every Sprint.
According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master,
and Developers. The Scrum Team is responsible for all product-related activities, including delivering
a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing
the value of the product and the work of the Developers. The Developers are accountable for
creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of
Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for
establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and
practice, and removing impediments to the Scrum Team’s progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item
selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a
Product Backlog item is determined by the Product Owner, who orders the Product Backlog items
based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to
understand the value and requirements of each Product Backlog item and deliver a potentially
releasable product increment that meets the Definition of Done and the Sprint Goal.
Reference:
[Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from
stakeholder collaboration, verification, maintenance, operation, experimentation, research and
development, and anything else that might be required.”
Accountabilities in Scrum | Scrum.org
: “Scrum has three accountabilities, each with a different focus :
Product Owner (green figure) The "What". With a focus on Value, time to market, return on
investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building
something that is Done – that the increment is useable and potentially releasable.”
What is a Developer in Scrum? | Scrum.org
: “The specific skills needed by the Developers are often
broad and will vary based on the type of work they are doing. However, the Developers are always
accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a
Definition of Done Adapting their plan each day toward the Sprint Goal”
True or False: Product Owners must specify complete acceptance criteria for a Product
Backlog item before the Developers can select the item in Sprint Planning.
B
Explanation:
False: Product Owners do not have to specify complete acceptance criteria for a Product Backlog
item before the Developers can select the item in Sprint Planning.
Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be considered
“Done” and acceptable for delivery.
Acceptance criteria are not mandatory in Scrum, but they can help the Product Owner and the
Developers to clarify the expectations and requirements of a Product Backlog item.
Acceptance criteria can be added or refined by the Product Owner at any time, but they should be
clear and testable before the Sprint starts.
The Developers can select a Product Backlog item in Sprint Planning based on their understanding of
its value, scope, and complexity, as well as their capacity and skills. They can also collaborate with
the Product Owner to define or refine the acceptance criteria during Sprint
Planning. Reference: Scrum Guide, Section 3.4 (The Product Backlog), Section 5.1 (Sprint Planning),
and Section 6.4 (The Increment)
Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of
Done?
(choose the best two answers)
C, D
Explanation:
The Product Owner should care that the Scrum Team adheres to its Definition of Done because:
It helps to forecast the team’s productivity over time. By having a clear and consistent Definition of
Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint
and plan accordingly.
It affects the product’s total cost of ownership. By ensuring that the work done by the team meets
the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of
technical debt, rework, defects, and maintenance costs in the future.
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 11: “The Product Owner is accountable for effective Product Backlog
management, which includes … ordering Product Backlog items; and, ensuring that the Product
Backlog is transparent, visible and understood.”
Scrum Guide 2020, page 14: “The Definition of Done creates transparency by providing everyone a
shared understanding of what work was completed as part of the Increment. If a Product Backlog
item does not meet the Definition of Done, it cannot be released or even presented at the Sprint
Review. Instead, it returns to the Product Backlog for future consideration.”
How is management that is external to the Scrum Team involved in the Daily Scrum?
(choose the best answer)
C
Explanation:
Management that is external to the Scrum Team is not involved in the Daily Scrum because:
The Daily Scrum is an event for the Developers to inspect their progress towards the Sprint Goal and
adapt their Sprint Backlog accordingly. It is not a status meeting or a reporting session for managers
or other stakeholders.
The presence of external managers may hinder the self-organization, collaboration, and transparency
of the Developers. It may also create pressure, interference, or distraction for the team.
The Scrum Master is responsible for ensuring that the Daily Scrum is held and that only the
Developers participate. The Product Owner and other stakeholders may attend as observers, but only
if the Developers find it useful.
Reference:
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 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.”
Which of the following are criteria to order Product Backlog items?
(choose all that apply)
A, B, C
Explanation:
The Product Owner orders the Product Backlog items according to various criteria, such as:
The value of Product Backlog items. The Product Owner aims to maximize the value of the product
and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to
the stakeholders and the users, considering factors such as customer satisfaction, market share,
revenue, social impact, etc.
The dependencies between Product Backlog items. The Product Owner tries to minimize the
dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they
order the items in a way that reduces or eliminates the dependencies, or resolves them as early as
possible.
The dependencies to other products. The Product Owner also considers the dependencies that the
product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they
order the items in a way that aligns with the availability and compatibility of those products.
Reference:
Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog
management, which includes … ordering Product Backlog items; and, 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.”
True or False: The value delivered by a product can only be determined by revenue.
B
Explanation:
The value delivered by a product can not be determined by revenue alone, because:
Revenue is only one aspect of value, and it may not reflect the true impact or benefit of the product
for the stakeholders, the users, and the society. For example, a product may generate high revenue,
but also cause environmental damage, ethical issues, or customer dissatisfaction.
Value is a subjective and relative concept, and it may vary depending on the context, the perspective,
and the criteria of the evaluation. For example, a product may have different value for different
segments of customers, or for different markets or regions.
Value is dynamic and emergent, and it may change over time due to various factors, such as
feedback, competition, innovation, or regulation. For example, a product may lose its value as new
alternatives or solutions become available, or as customer needs or preferences evolve.
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.”
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.”