PSPO

How can a Product Owner use time-boxed Sprints to obtain feedback from users and the market?

Answer options for question 5 Through frequent delivery of Increments of the product into the market.

Owner to order Product Backlog items by value points?

It is a good practice, keeping in mind that market reception is the best measure of value.

How much is known about the Product over time

Not more than 10%

What variables should a Product Owner consider when ordering the Product Backlog?

Whatever is most appropriate for the Product Owner to achieve the product's goals and to optimize the value received

It is mandatory for the Product Owner to monitor and share progress of the Product Backlog by using which method?

Any practice based on trends of work completed and upcoming work

What technique should be used for representing Product Backlog Items?

Any technique, even a mix of several techniques; 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.

How does an organization know that a product built through Scrum is successful?

By releasing often, and updating key performance indicators (KPIs) on value after every release and feeding this information back into work on the Product Backlog

A Product Owner is essentially the same thing as a traditional Project Manager?

False

It is a good practice to have at least two Product Owners on big projects

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.

If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled.

False; 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.

The value delivered by a product can only be determined by revenue.

False; Value is likely to vary across products and organizations.

How frequently product releases should occur?

Frequently enough to eliminate the risk that the product's value will get out of line with the marketplace

What does Burn-down Chart show?

How much work remains till the end of the Sprint

What is the order of items in the Product Backlog?

Less valuable and most unclear items at the bottom

The Sprint Review is just a demo of the Product Backlog items completed during a Sprint. Do you agree?

No; 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.

The Product Owner's authority to change and update the Product Backlog is unlimited, except for:

Nothing. The entire organization must respect a Product Owner's decisions.

The Development Team finds out during the Sprint that they aren't likely to build everything they forecast. What would you expect a Product Owner to do?

Re-negotiate the selected Product Backlog items with the Development Team to meet the Sprint Goal.

Sort Scrum events in the right order.

Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

Who is responsible for all estimates in the Product Backlog?

The Development Team

The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?

The Development Team. As a collective, they have a complete view of the work needed to transform Product Backlog items into Increments of product.

What could be a source of requirements for any changes to be made to the product?

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.

What best describes the relationship of the Product Owner and the stakeholders?

The Product Owner actively asks for stakeholder input and expectations to process into the Product Backlog.

Who participates in the Sprint Planning?

The Product Owner; The Scrum Master; The Development Team

Who is responsible for crafting the Sprint Goal at the Sprint Planning?

The Scrum Team

What two things best help the Product Owner manage the value of a product?

The order of the Product Backlog Validating assumptions of value through frequent releases

What is the Increment?

The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints

What pre-conditions must be fulfilled in order to allow Sprint Planning to begin?

There are no such pre-conditions

What two phrases best describe the relationship of the Product Owner and the Development Team?

They collaborate often so the Development Team builds Increments keeping end-user and stakeholder concerns in mind. They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items.

A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place.

True

All Development Teams working on the same Product should use the same Product Backlog.

True; Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.

Which description best fits the role of the Product Owner?

Value Maximizer

What is the Sprint Backlog?

the Product Backlog items selected for this Sprint plus the plan for delivering them

How does Definition of "Done" help the Scrum Team?

1.Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning 2. DoD is used to assess when work is complete on the product Increment 3. DoD ensures artifact transparency

What are Product Backlog features

1.It is never complete 2. It is dynamic 3. As long as a product exists, its Product Backlog also exists 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

How can the Product Owner bring his product vision to life (select 3)?

1.Via the Product Backlog and iterating towards that vision every Sprint 2. Utilizing the underlying empirical product planning features of Scrum 3. Articulating the product vision to the Scrum Team and the Key Stakeholders early and often

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

In order to make investment decisions, the Product Owner is likely to look at the Total Cost of Ownership (TCO) of the product being built. What costs will a Product Owner take into account?

All investments required to conceive, develop, operate and maintain the product; The owner of a product is not only accountable for development and release of a product, but also the cost of maintaining and operating the product. If a person 'owns' the product, he/she can be expected to be responsible for the complete life cycle of a product.

When can the Product Backlog be updated?

At any time when done by the Product Owner or at the Product Owner's discretion

What is the Product Owner accountable for in Scrum?

Clearly expressing a Product Backlog that maximizes value and represents the needs of the stakeholders

Which KVA categories should the Product Owner consider to measure and track the creation and delivery of value to the market place (select three)?

Current Value Time-to-Market Ability to Innovate

If multiple Stakeholders have varied interests in the product and different viewpoints what is the best strategy for the Product Owner?

Do an intelligent balancing of interests and try to maximize the value of the Product as a whole; 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.

Who participates in the Sprint Review

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 happens during the Sprint?

During the Sprint: No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

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; 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 Sprint Review is the only time at which stakeholder feedback is taken into account.

False

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

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.

The Scrum Team should choose at least one high priority process improvement, identified during the Sprint Retrospective, and place it in the Product Backlog.

False, to ensure continuous improvement, the Sprint Backlog rather than the Product Backlog includes at least one high priority process improvement identified in the previous Sprint Retrospective meeting.

All the Scrum Teams working on the same product should have the same Sprint length.

False. Scrum does not require having aligned Sprints for multiple teams.

What does Cone of Uncertainty show?

How much is known about the Product over time

What two things should be done if the Product Owner is unavailable?

In a permanent state of unavailability, a new Product Owner needs to be appointed. Development efforts without a Product Owner are not employing Scrum. Within the Sprint, the Development Team makes the best decisions possible to assure progress toward the Sprint Goal, re-aligning with the Product Owner once he/she is available again

Which two statements explain why the definition of "Done" is important to the Product Owner?

It creates transparency regarding progress within the Scrum Team. It assures the Increment reviewed at the Sprint review is usable so the Product Owner may choose to release it.

What is a Product Backlog?

It is a living artifact of product requirements that exists and evolves as long as a product exists.

Must the Product Owner be present at the Sprint Retrospective?(choose the best answer)

It is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess its performance and improve itself.

A Development Team is waiting for a specific software component that they need to integrate and use.The component should be ready in a month.The Backlog Items with highest priorities depend on this specific component. What should the Product Owner do?

Make sure the dependency is visible in the Product Backlog and the Development Team has enough independent Items for the next Sprint, 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.

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. Is it a good idea for the PO to proxy or outsource some of their PO Scrum Team duties to these people

NO; it is NOT acceptable for the PO to attempt to proxy or outsource their PO Scrum Team duties, especially the Scrum Team facing duties

Learning turns into 'validated learning' when assumptions and goals can be assessed through results. What is a key way for a Product Owner to apply validated learning?

Release an Increment to the market to learn about the business assumptions built into the product.; The Product Owner manages Product Backlog against the assumption that value will be generated. This assumption remains invalidated when not checked against users and market.

Time-box for each Scrum event

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. Sprint Retrospective is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

To what extent does technical debt limit the value a Product Owner can get from a product?

Technical debt causes a greater percentage of the product's budget to be spent on maintenance of the product. The velocity at which new functionality can be created is reduced when you have technical debt.

Who is allowed to change the Sprint Backlog during the Sprint?

The Development Team

Select the two meetings in which people outside the Scrum Team are allowed to participate

The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting

Who is allowed to make changes in the Product Backlog?

The Development Team, but with permission of the Product Owner The Product Owner

Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?

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.

Who has the authority to cancel the Sprint?

The Product Owner

How does the Product Owner communicate his marketplace knowledge to the Scrum Team (select three)?

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 process of regular inspection and adaptation employs knowledgeable and skilled inspectors. What are two ways in which the Product Owner takes the lead in the inspection process?

The Product Owner invites stakeholders to the Sprint Review to learn how the current state of the marketplace influences what is the most valuable thing to do next. At the Sprint Review the Product Owner shares the current state of Product Backlog, which, combined with the inspection of the Increment, leads to an updated Product Backlog.

Who is responsible for managing the Product Backlog?

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

Who is responsible for monitoring progress toward high-level goals?

The Product Owner; 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.

Who is allowed to tell the Development Team to work from a set of requirements?

The Product Owner; 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.

How does the Scrum Master help the Product Owner

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 is responsible for promoting and supporting Scrum

The Scrum Master; 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.

What are the Scrum Artifacts?

The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.

What provides guidance to the Development Team on why it is building the Increment?

The Sprint Goal; 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.

Who creates the definition of "Done"?

The development organization (or Development Team if none is available from the development organization); If the definition of "done" is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. The Development Team of the Scrum Team can complement it with elements specific for the product or context.

What is the essence of Scrum?

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.

A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:

There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint.

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

Who is allowed to participate in the Daily Scrum?

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

What are two typical activities for a Product Owner in a Sprint?

Work with the Development Team on Product Backlog refinement. Collaborate with stakeholders, user communities, and subject matter experts.