PCPO Exam Self Prep

Category: Scrum Team
What does Product Backlog management include? Select three most applicable items.
 Moving Product Backlog items into the Sprint Backlog
 Optimizing the value of the work the Development Team performs
 Ensuring that the Product Backlog is visible, transparent, and clear to all, and
shows what the Scrum Team will work on next
 Presenting Product Backlog items to the Key Stakeholders
 Ordering the items in the Product Backlog to best achieve goals and missions
Product Backlog management includes:
 Clearly expressing Product Backlog items;

 Ordering the items in the Product Backlog to best achieve goals and missions;
 Optimizing the value of the work the Development Team performs;
 Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what
the Scrum Team will work on next; and,
 Ensuring the Development Team understands items in the Product Backlog to the level
needed.

Could the Product Owner and the Scrum Master be a part of the Development Team?
 No
 Yes
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.
Category: Scrum Artifacts

What is the Sprint Backlog?
 The plan for delivering Product Backlog items
 The Product Backlog items selected for this Sprint plus the Team Backlog items
 The Product Backlog items selected for this Sprint plus the plan for delivering
them
 The Product Backlog items selected for this Sprint
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.
Category: Scrum Theory

How frequently product releases should occur?
 Every 3 months
 By the end of Product development
 Every Sprint
 At least every 6 months
 Frequently enough to eliminate the risk that the product’s value will 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. Looking at it another way, the sooner you release, the sooner you can start capturing the
value created by the product.

It is a good practice to have at least two Product Owners on big projects.
 True
 False
The Product Owner is one person, not a committee, but the Product Owner may represent the
desires of a committee in the Product Backlog.

Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood
of achieving the Sprint Goal?
 The Scrum Master
 The Scrum Team
 The Product Owner
 The Development Team
 The Product Owner and the Development Team
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.

What part of the capacity of the Development Team does Product Backlog refinement usually
consume?
 Not more than 10%
 The Development Team is not authorized for Product Backlog refinement
Product Backlog refinement usually consumes no more than 10% of the capacity of the
Development Team.
Category: Scrum Events
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.
 False
 True
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.

Who is allowed to participate in the Daily Scrum?
 The Key Stakeholders
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.

Who is allowed to tell the Development Team to work from a set of requirements?
 The Product Owner and the Scrum Master
 Upper Management
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.

In which meetings the Key Stakeholders are allowed to participate?
 The Sprint Review
 The Sprint Retrospective
 The Sprint Planning
 The Daily Scrum
Correct
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 Scrum Team consists of
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

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.
 True
 False
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.

What are the three most applicable characteristics of the Product Owner?
 Product Value Maximizer
 Facilitator of Scrum events
 Lead Facilitator of Key Stakeholder Involvement
 Product Marketplace Expert
 Lead Scrum evangelist in the Organization
 Product Value Maximizer

 Lead Facilitator of Key Stakeholder Involvement
 Product Marketplace Expert

Who is responsible for crafting the Sprint Goal at the Sprint Planning?
 The Scrum Team

Correct
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the
Scrum Team crafts a Sprint Goal.

How does the Scrum Master help the Product Owner? Select the three most appropriate answers.
 Finding techniques for effective Product Backlog management
 Understanding product planning in an empirical environment
 Facilitating Scrum events as requested or needed
 Leading and coaching the organization in its Scrum adoption
 Introducing cutting edge development practices
The Scrum Master serves the Product Owner in several ways, including:
 Ensuring that goals, scope, and product domain are understood by everyone on the Scrum
Team as well as possible;
 Finding techniques for effective Product Backlog management;
 Helping the Scrum Team understand the need for clear and concise Product Backlog items;
 Understanding product planning in an empirical environment;
 Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
 Understanding and practicing agility; and,
 Facilitating Scrum events as requested or needed.

Who participates in the Sprint Review? Select all applicable variants.
 The Organization CEO

Correct
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.

What provides guidance to the Development Team on why it is building the Increment?
 The Sprint Goal
 The Sprint Backlog
Correct
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.

What are the Scrum Artifacts? Select all applicable items.
 The Sprint Goal
 The list of removed impediments
 Increment
 Sprint Backlog
 Product Backlog
Incorrect
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.

What could be a source of requirements for any changes to be made to the product?
 The Product Backlog
 The CEO of the Organization
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.

Who is allowed to change the Sprint Backlog during the Sprint?
 The Scrum Team
 The Development Team and the Product Owner
Incorrect
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.

Who is responsible for managing the Product Backlog?

Correct
The Product Owner is the sole person responsible for managing the Product Backlog.

What does Cone of Uncertainty show?
 How much is known about the Product over time
 How much work remains till the end of the Sprint
 Dependencies, start times and stop times for project tasks
 Hierarchy of tasks that comprise a project
The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.

What is the Increment?
 The sum of all the Product Backlog items completed during the Sprint
 The sum of all the Product Backlog items completed during the Sprint and the
value of the increments of all previous Sprints
 All items in the Sprint Backlog that could be released regardless of whether the Product
Owner decides to actually do it
 All "Done" items in the Sprint Backlog
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.

Who has the authority to cancel the Sprint?
 The Product Owner and the Scrum Master
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.

How does Definition of “Done” help the Scrum Team? Select three most applicable items.
 DoD ensures artifact transparency
 Guides the Development Team in knowing how many Product Backlog items it
can select during a Sprint Planning
 DoD helps in inspection and adaptation
 DoD helps to calculate velocity of the Scrum Team
 DoD is used to assess when work is complete on the product Increment
 DoD is used to assess when work is complete on the product Increment

 Guides the Development Team in knowing how many Product Backlog items it can select
during a Sprint Planning
 DoD ensures artifact transparency

What does Burn-down Chart show?
 How much work remains till the end of the Sprint

 The evolution of the amount of uncertainty during a project
 Hierarchy of tasks that comprise a project
 Dependencies, start times and stop times for project tasks
Correct
Burn-down chart shows the evolution of remaining effort against time.

Who participates in the Sprint Planning? Select three.
 The Team Manager
Correct
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.

What are Product Backlog features? Select three.
 It is never complete
 It is dynamic
 As long as a product exists, its Product Backlog also exists
 A Product Backlog could be closed when it contains no items to include into the next
Sprint
 When the final version of a product is rolled out, its Product Backlog is dismissed
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.

What is the order of items in the Product Backlog?
 Less valuable and most unclear items at the bottom
 Alphabetical
 The less clear items at the top
 The recently added items at the top
Correct
The Product Owner is responsible for placing the most valuable and clear items at the top of the
Product Backlog.

All the Scrum Teams working on the same product should have the same Sprint length.
 True
 False
Correct
False. Scrum does not require having aligned Sprints for multiple teams.

Who is responsible for creation of the Definition of “Done”?

 The Scrum Team
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.”

The Sprint Review is just a demo of the Product Backlog items completed during a Sprint. Do you
agree?
 Yes. There is no much difference.
 No, the Sprint Review contains much more activities
 No, the demo also should include the Items completed in the previous Sprints that were
not demonstrated for some reason
No. The Sprint Review contains much more activities to inspect the Increment and adapt the Product
Backlog.
For example:
 The Product Owner also explains what has not been “Done”;

 The entire group collaborates on what to do next, so that the Sprint Review provides
valuable input to subsequent Sprint Planning;
 Review of the timeline, budget, potential capabilities, and marketplace for the next
anticipated releases of functionality.

Who is allowed to make changes in the Product Backlog? Select two options.
 The Development Team, but with permission of the Product Owner

 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.

Who is the chief product visionary?
 The Chief Marketing Officer (CMO)
 The Chief Executive Officer (CEO)
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.

Who is the leader in terms of getting feedback from the Key Stakeholders in the Sprint Review?
 The Scrum Team
The Product Owner is a vital leader in terms of getting feedback from the key stakeholders in the
Sprint Review.

Product Backlog Refinement practice focuses on Items for upcoming Sprints, not the current Sprint
in progress. True or false?
 True
 False
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.

Once the Product Owner gained his Product Vision and defined the tactics of bringing this vision to
life, it is a bad idea to change them before the next Product Release.
 False
 True
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.

Select the five Scrum Values.
 Commitment
 Effectiveness
 Focus
 Agility
 Self-organization
 Openness
 Courage
 Respect
The Scrum Guide recognizes the following Scrum Values: commitment, courage, focus, openness
and respect.

Who decides whether to release the latest increment of the product?
 The Scrum Team
 The Product Owner and The Scrum Master
The Product Owner is the one and only person who can decide whether to release the latest increment of the
product.

Select the three best options to finish the sentence below.
Technical debt …
 belongs entirely to the Development Team. No one else should know about it.
 reflects some extra development work
 is a lack of technical supplies
 compromises long-term quality of the Product
 is a real risk which can genuinely be incurred
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.

The Product Owner should be expertly aware of the marketplace for the product.
 False
 It depends
 True
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.

The Product Owner wants to apply some non-functional requirements to the Product. What is the
best way to proceed?
 Add the non-functional requirements to the DoD and check every Increment
against these criteria
 Create a new Item for every requirement in the Product Backlog
 Non-functional requirements cannot be handled within the bounds of Scrum
 Find a way to convert non-functional requirements into Product features and act
accordingly
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.

When is the Scrum Team allowed to interact with the Key Stakeholders (select the most applicable
option)?
 The Sprint Review
 Any time where it’s valuable to have the Stakeholder input
 The Daily Scrum
 The Sprint Retrospective

The Product Owner is responsible for making sure that the Key Stakeholders attend and interact in
the Sprint Reviews, but really the Stakeholders can be involved with the Scrum Team any time
where it’s valuable to have the Stakeholder input.

PCPO Exam Self Prep

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCPO Exam Self Prep

Uploaded by

Copyright:

Available Formats

Category: Scrum Team

 Moving Product Backlog items into the Sprint Backlog

 Optimizing the value of the work the Development Team performs

 Presenting Product Backlog items to the Key Stakeholders

Product Backlog management includes:

 Clearly expressing Product Backlog items;

Category: Scrum Team

Category: Scrum Artifacts

 The plan for delivering Product Backlog items

 The Product Backlog items selected for this Sprint

Category: Scrum Theory

 By the end of Product development

 At least every 6 months

Category: Scrum Team

Category: Scrum Artifacts

 The Scrum Master

 The Scrum Team

 The Product Owner

 The Development Team

 The Product Owner and the Development Team

Category: Scrum Artifacts

 Not more than 10%

 Not more than 20%

 Not more than 5%

 The Development Team is not authorized for Product Backlog refinement

Category: Scrum Events

 The Product Owner

 The Scrum Master

 The Key Stakeholders

 The Development Team

Category: Scrum Theory

 The Product Owner and the Scrum Master

 The Key Stakeholders

 The Scrum Master

Category: Scrum Events

 The Sprint Review

 The Sprint Retrospective

 The Sprint Planning

 The Daily Scrum

Category: Scrum Team

 The Product Owner

 The Scrum Master

 The Key Stakeholders

 The Development Team

Category: Scrum Artifacts

Category: Scrum Team

 Product Value Maximizer

 Facilitator of Scrum events

 Lead Facilitator of Key Stakeholder Involvement

 Product Marketplace Expert

 Lead Scrum evangelist in the Organization

 Product Value Maximizer

Category: Scrum Events

 The Scrum Master

 The Development Team

 The Scrum Team

 The Key Stakeholders

 The Product Owner

Category: Scrum Team

 Finding techniques for effective Product Backlog management

 Understanding product planning in an empirical environment

 Facilitating Scrum events as requested or needed