Pspo 2 Questions
Pspo 2 Questions
Product Owner100%
2. Scrum Artifacts70.83%
3. Scrum Events64.71%
4. Scrum Team75%
5. Scrum Theory72%
1. 1. Question
Who is responsible for tracking the total work remaining in the Sprint Backlog to project the
likelihood of achieving the Sprint Goal?
At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be
summed. The Development Team tracks this total work remaining at least for every Daily
Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work
throughout the Sprint, the Development Team can manage its progress.
2. 2. Question
Who is the leader in terms of getting feedback from the Key Stakeholders in the Sprint
Review?
The Product Owner is a vital leader in terms of getting feedback from the key stakeholders in
the Sprint Review.
3. 3. Question
The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the
Sprint Backlog later by the Development Team.
o True
o False
Correct
The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint
Backlog emerges during the Sprint. This emergence occurs as the Development Team
works through the plan and learns more about the work needed to achieve the Sprint
Goal. As new work is required, the Development Team adds it to the Sprint Backlog.
4. 4. Question
Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team
identified some improvements that can be done. What should the Scrum Team do? Select
the best option.
o Make sure the Sprint Backlog for the next Sprint includes at least one high
priority process improvement.
o Make sure the Sprint Backlog for the next Sprint includes all the improvements.
o Assign a responsible team member for at least one improvement. Check the
progress at the next Retrospective.
Incorrect
The Sprint Backlog makes visible all the work that the Development Team identifies as
necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least
one high priority process improvement identified in the previous Retrospective meeting.
5. 5. Question
What does Product Backlog management include? Select three most applicable items.
o Ordering the items in the Product Backlog to best achieve goals and
missions
o Ensuring that the Product Backlog is visible, transparent, and clear to all,
and shows what the Scrum Team will work on next
6. 6. Question
Who has the authority to cancel the Sprint?
Only the Product Owner has the authority to cancel the Sprint, although he or she may do so
under influence from the stakeholders, the Development Team, or the Scrum Master.
7. 7. Question
Who has the “last say” on the order of items in the Product Backlog?
While the Product Owner is not the only person who may influence the ordering of the
Product Backlog, the Product Owner has the “last say” on the order of the Product Backlog,
and those wanting to change the order of the Product Backlog have to influence the Product
Owner to do so.
8. 8. Question
What are the time-boxes for the Sprint Review and the Sprint Retrospective?
9. 9. Question
Select the two meetings in which people outside the Scrum Team are allowed to participate.
o The Development Team may invite other people to attend the Sprint Planning in
order to provide technical or domain advice.
o The Product Owner is responsible for inviting the Key Stakeholders to the Sprint
Review meeting
o At the Sprint Retrospective the Scrum Master determines who from the
Development Team is responsible for cancelling the Sprint
o Several top Product Backlog Items are taken into the Sprint Backlog to replace
the obsolete items
o All incomplete Product Backlog Items are re-estimated and put back on
the Product Backlog
When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed.
If part of the work is potentially releasable, the Product Owner typically accepts it. All
incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.
The Product Backlog is an ordered list of everything that might be needed in the product and
is the single source of requirements for any changes to be made to the product.
The Product Backlog is dynamic; it constantly changes to identify what the product needs to
be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists.
o False
o True
Correct
The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work
could not be done, the Sprint Backlog should be re-negotiated between the Product Owner
and Development Team.
o Employee Satisfaction
o Capability Building
o Risk Reduction
o Ability to Innovate
o Time-to-Market
o Current Value
Correct
o Current Value
o Time-to-Market
o Ability to Innovate
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was
done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint,
attendees collaborate on the next things that could be done to optimize value.
The PO should communicate and re-iterate his product vision to the Scrum Team and the
Key Stakeholders early and often, reminding all involved of how that vision aims to maximize
the value of the product and of the work the Scrum Team performs.
17. 17. Question
Select the three best options to finish the sentence below.
Technical debt …
o belongs entirely to the Development Team. No one else should know about it.
Technical debt is a concept in programming that reflects the extra development work that
arises when code that is easy to implement in the short run is used instead of applying the
best overall solution. In other words it can be defined as the longer term consequences of
poor design decisions. Technical debt is a real risk which can genuinely be incurred.
It compromises long-term quality of the Product.
One of the ways of handling technical debt is recording it on the Product Backlog. So, it
becomes visible to the Scrum Team.
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint,
the Scrum Team crafts a Sprint Goal.
o False
o True
Incorrect
By the end of the Sprint Planning, the Development Team should be able to explain to the
Product Owner and Scrum Master how it intends to work as a self-organizing team to
accomplish the Sprint Goal and create the anticipated Increment.
The essence of Scrum is a small team of people. The individual team is highly flexible and
adaptive. These strengths continue operating in single, several, many, and networks of
teams that develop, release, operate and sustain the work and work products of thousands
of people. They collaborate and interoperate through sophisticated development
architectures and target release environments.
The Product Owner is the sole person responsible for managing the Product Backlog.
o Scope may be clarified and re-negotiated between the Product Owner and
Development Team as more is learned
o The Sprint Goal is changed frequently to reflect the status of the remaining work
Incorrect
o Is the act of adding detail, estimates, and order to Product Backlog items
o Answers the question: how will the work needed to deliver the Increment be
achieved
o Is an ongoing process
o Usually takes no more than 10% of the capacity of the Development Team
Product Backlog refinement is the act of adding detail, estimates, and order to items in the
Product Backlog. This is an ongoing process in which the Product Owner and the
Development Team collaborate on the details of Product Backlog items. It usually consumes
no more than 10% of the capacity of the Development Team.
o Alphabetical
Correct
The Product Owner is responsible for placing the most valuable and clear items at the top of
the Product Backlog.
o Anyone
The Product Owner is the sole person responsible for the Product Backlog. However, he or
she can delegate some work related to product backlog management to the Development
Team.
o The human people who actually use the product under development
o The people responsible for making the funding decisions for the product
development effort
Incorrect
According to the Scrum Glossary, a stakeholder is “a person external to the Scrum Team
with a specific interest in and knowledge of a product that is required for incremental
discovery. Represented by the Product Owner and actively engaged with the Scrum Team at
Sprint Review.”
Typically, they fall into one of three broad categories:
o The Users – The human people who actually use the product under development
o The External Customers – The people responsible for paying to use the product
o The Internal Customers – The people responsible for making the funding
decisions for the product development effort
o The Product Backlog items selected for this Sprint plus the Team Backlog items
o The Product Backlog items selected for this Sprint plus the plan for
delivering them
Incorrect
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal.
o Commitment
o Courage
o Agility
o Effectiveness
o Focus
o Openness
o Self-organization
o Respect
Correct
The Scrum Guide recognizes the following Scrum Values: commitment, courage, focus,
openness and respect.
The Development Team is responsible for all estimates in the Product Backlog. The Product
Owner may influence the Development Team by helping it understand and select trade-offs,
but the people who will perform the work make the final estimate.
Scrum has been used to develop software, hardware, embedded software, networks of
interacting function, autonomous vehicles, schools, government, marketing, managing the
operation of organizations and almost everything we use in our daily lives, as individuals and
societies.
The Cone of Uncertainty describes the evolution of the amount of uncertainty during a
project.
o The risk that the product’s value can get out of line with the marketplace
While Scrum doesn’t require a release to occur every Sprint, it should be noted that the more
elapsed time that accumulates since the last release, the higher the risk that the product’s
value will get out of line with the marketplace. Product Owners should keep this risk in the
forefront of their mind.
Another factor in the release decision is whether your customers can actually absorb your
frequent releases. Most customers approach this upgrade decision using a common sense
method of weighing the costs and benefits of the upgrade(new increment). This is all the
more reason to make sure that your releases are of the utmost value, and offer relatively low
absorption costs. Regardless of the benefits and costs, some customers will still be
constrained, so this constraint should be a consideration when deciding how often or
whether to release.
The PO is the one and only person who can decide whether to release the latest increment
of the product.
The Increment is “Done” by its definition.
o No, the demo also should include the Items completed in the previous Sprints
that were not demonstrated for some reason
Correct
No. The Sprint Review contains much more activities to inspect the Increment and adapt the
Product Backlog.
For example:
o The Product Owner also explains what has not been “Done”;
o The entire group collaborates on what to do next, so that the Sprint Review
provides valuable input to subsequent Sprint Planning;
o Review of the timeline, budget, potential capabilities, and marketplace for the next
anticipated releases of functionality.
o True
o False
o It depends
Correct
The Product Owner should be expertly aware of the marketplace for the product. They
should constantly be gathering and re-gathering information and data regarding the
marketplace, so that the product value is maximized. Getting out of touch with the
marketplace can be a recipe for product disaster.
o True
o False
Correct
False. The Product Owner is solely responsible and accountable for the decisions in the
Product Backlog. However, the legwork of managing the Product Backlog might be fully
delegated to the Development Team, so it is quite possible that the Product Owner might not
ever create or write a User Story or Product Backlog Item.
o Complex work that can include all the suggested options and even more
When the words “develop” and “development” are used in the Scrum Guide, they refer to
complex work including software and hardware development, development and releasing of
products and enhancements, development and sustaining product operational environments,
research and identifying of viable markets and technologies, and even more.
o True
o False
Correct
It is NOT acceptable for the PO to attempt to proxy or outsource their PO Scrum Team
duties.
The Product Owner will work in concert with the Scrum Master to utilize Scrum correctly and
advantageously, and try to never been seen as subverting or disrespecting the Scrum
framework. When something about Scrum frustrates a Product Owner, she should consult
the Scrum Master for ways to implement the Scrum framework in a way that is effective.
o False
o True
Correct
The Product Owner is one person, not a committee, but the Product Owner may represent
the desires of a committee in the Product Backlog.
o True
o False
Correct
The PO should never be afraid to change the vision or tactics based on marketplace
changes. Being able to strategically re-pivot and capture value in new and different ways is
one of the key benefits of an Agile mindset.
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created
by the collaborative work of the entire Scrum Team.
o User Stories
o Scenarios
o Use Cases
o Acceptance Tests
User stories are a fairly common technique for representing Product Backlog Items, but other
techniques can be used instead. For instance, a team can use scenarios, use cases,
acceptance tests, etc. The Product Backlog might even contain a heterogeneous mix of the
above.
The Product Owner should work with the rest of the Scrum Team on choosing and optimizing
the techniques used to represent Product Backlog Items.
o True
o False
Correct
True. Product Backlog refinement is the act of adding detail, estimates, and order to items in
the Product Backlog. The Items in the current Sprint are no longer on the Product Backlog,
because they are now on the Sprint Backlog.
However, it is certainly fine for the Product Owner to add detail and clarification to the current
Sprint’s work as well.
The Product Owner tracks total work remaining at least every Sprint Review. The Product
Owner compares this amount with work remaining at previous Sprint Reviews to assess
progress toward completing projected work by the desired time for the goal. This information
is made transparent to all stakeholders.
o Listen to the people that fund the product’s development because they always
have the last word
o Calculate ROI (Return Of Investments) for every viewpoint and select the
maximal one
Correct
Inherent in the role of facilitating key stakeholder involvement is weighing and balancing the
(likely) differing viewpoints of multiple stakeholders who might have varied interests in the
product. The Product Owner’s responsibility is to maximize the value of the product as a
whole, and this will involve an intelligent balancing of interests.
If the definition of “done” for an increment is part of the conventions, standards or guidelines
of the development organization, all Scrum Teams must follow it as a minimum. If “done” for
an increment is not a convention of the development organization, the Development Team of
the Scrum Team must define a definition of “done” appropriate for the product. If there are
multiple Scrum Teams working on the system or product release, the development teams on
all of the Scrum Teams must mutually define the definition of “Done.”
Product Backlog refinement usually consumes no more than 10% of the capacity of the
Development Team.
o True
o False
Correct
False. The Scrum Team crafts a Sprint Goal during the Sprint Planning.
o Frequently enough to eliminate the risk that the product’s value will get
out of line with the marketplace
o Every 3 months
Correct
While Scrum doesn’t require a release to occur every Sprint, it should be noted that the more
elapsed time that accumulates since the last release, the higher the risk that the product’s
value will get out of line with the marketplace. Product Owners should keep this risk in the
forefront of their mind. Looking at it another way, the sooner you release, the sooner you can
start capturing the value created by the product.
Non-functional requirements describe qualities of the Product being developed. For example,
the Product should be secure and extensible. The only way to meet such requirements is to
have them as a part of the DoD and check every Increment against these criteria.
The Daily Scrum is an internal meeting for the Development Team. If others are present, the
Scrum Master ensures that they do not disrupt the meeting.
o Product Visionary
In executing Value Driven Development, the Product Owner must consider the focus areas
of:
o Until all the Items in the Sprint Backlog are decomposed to units of one day or
less
o The sum of all the Product Backlog items completed during the Sprint and
the value of the increments of all previous Sprints
o The sum of all the Product Backlog items completed during the Sprint
Incorrect
The Increment is the sum of all the Product Backlog items completed during
the Sprint and the value of the increments of all previous Sprints.
The Scrum Master is responsible for promoting and supporting Scrum as defined in the
Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory,
practices, rules, and values.
o Nothing. The Product Backlog already has the most valuable items at the top.
The Development Team cannot proceed further until the dependency is resolved.
o Remove the dependent Items from the Product Backlog and put them in a
special wait list. When the dependency is resolved, the Items should be returned
back.
o Make sure the dependency is visible in the Product Backlog and the
Development Team has enough independent Items for the next Sprint.
Correct
The Product Backlog should make the dependency visible to all the interested parties.
Usually Items with external dependencies are not considered “Ready” for selection at the
Sprint Planning.
Development Teams should deliver an Increment of product functionality every Sprint.
o Can be implemented within one Sprint and tested in the next Sprint
o Well refined
o Has less detail
Correct
Higher ordered Product Backlog items are usually clearer and more detailed than lower
ordered ones. More precise estimates are made based on the greater clarity and increased
detail; the lower the order, the less detail. Product Backlog items that will occupy the
Development Team for the upcoming Sprint are refined so that any one item can reasonably
be “Done” within the Sprint time-box. Product Backlog items that can be “Done” by the
Development Team within one Sprint are deemed “Ready” for selection in a Sprint Planning.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation
of Product Backlog. It provides guidance to the Development Team on why it is building the
Increment.
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum
Master.
The Product Owner is responsible for the Product Backlog, including its content, availability,
and ordering.
o Sprint Reviews
o Sprint Retrospectives
o Daily Scrums
Incorrect
The Product Owner communicates all of this marketplace knowledge to the Scrum Team
through daily ad hoc interactions as well as Product Backlog Refinement and in Sprint
Reviews.
The Scrum Master serves the Product Owner in several ways, including:
o Ensuring that goals, scope, and product domain are understood by everyone on
the Scrum Team as well as possible;
o Finding techniques for effective Product Backlog management;
o Helping the Scrum Team understand the need for clear and concise Product
Backlog items;
o Understanding product planning in an empirical environment;
o Ensuring the Product Owner knows how to arrange the Product Backlog to
maximize value;
o Understanding and practicing agility; and,
o Facilitating Scrum events as requested or needed.
o No
o Yes
Correct
Yes. Scrum does not prohibit the Product Owner or the Scrum Master do development work.
However, it is not the best practice because it could create a conflict of interest.
o False
o True
Correct
Multiple Scrum Teams often work together on the same product. One Product Backlog is
used to describe the upcoming work on the product.
o Description
o Value
o Dependencies
o Order
o Estimate
Incorrect
Product Backlog items have the attributes of a description, order, estimate, and value.
Product Backlog items often include test descriptions that will prove its completeness when
“Done”.
o Making the Scrum Master bring the vision to the Scrum Team and the Key
Stakeholders
o Via the Product Backlog and iterating towards that vision every Sprint
o Articulating the product vision to the Scrum Team and the Key
Stakeholders early and often
Correct
The PO should communicate and re-iterate his product vision early and often, reminding all
involved of how to help maximize value. Utilizing the underlying empirical product planning
features of Scrum, the PO should also be ready to make strategic pivots for the product
vision. This vision is brought to life in a more tactical way, via the Product Backlog and
iterating towards that vision every Sprint.
The Product Owner may or may not be the one doing the legwork of gathering the
marketplace data, but the PO should definitely be aware of said data/research.
o Product Backlog
o Increment
o Sprint Backlog
Correct
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
o When the final version of a product is rolled out, its Product Backlog is
dismissed
o A Product Backlog could be closed when it contains no items to include into the
next Sprint
o It is dynamic
o It is never complete
Correct
A Product Backlog is never complete. The earliest development of it only lays out the initially
known and best-understood requirements. The Product Backlog evolves as the product and
the environment in which it will be used evolves. The Product Backlog is dynamic; it
constantly changes to identify what the product needs to be appropriate, competitive, and
useful. As long as a product exists, its Product Backlog also exists.
The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However,
any member of the Scrum Team can interact with them any time.
The Product Owner is the chief product visionary. The PO should be able to clearly articulate
the product vision to the Scrum Team and key stakeholders, and how that vision aims to
maximize the value of the product and of the work the Scrum Team performs.
The Product Owner is the one and only person who can decide whether to release the latest
increment of the product.
Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint
Backlog is a highly visible, real-time picture of the work that the Development Team plans to
accomplish during the Sprint, and it belongs solely to the Development Team.
o True
o False
Correct
False. Scrum does not require having aligned Sprints for multiple teams.
In order to maximize value, the Product Owner should identify the Key Stakeholders for the
Product, and involve them as necessary throughout the development effort.
o Upper Management
Correct
The Product Owner’s decisions are visible in the content and ordering of the Product
Backlog. No one is allowed to tell the Development Team to work from a different set of
requirements, and the Development Team isn’t allowed to act on what anyone else says.
o No
o Yes
Correct
When a product grows, it is quite possible that the PO will get help from other Product
Managers and others in the organization who interact regarding the customer facing
activities and knowledge of the product marketplace. While it is fine for the PO to be aided by
the aforementioned people, it is NOT acceptable for the PO to attempt to proxy or outsource
their PO Scrum Team duties, especially the Scrum Team facing duties.