PSPO 2 - LVL 1

Select all that apply. For a Scrum Team, the Sprint Planning meetings are always going beyond the time-box. What could the likely causes be?

The Team didn't invest enough in Product Backlog Refinement (Correct) The Product Backlog size is huge (Incorrect) The Scrum Team is trying to get a perfect, detailed and complete Sprint plan. (Correct) The Scrum Master does not moderate and control the participants (Incorrect) Explanation If the team doesn't invest enough in Product Backlog refinement the Sprint Planning can take longer as the Product Backlog Items lack information such as description and estimation. The Scrum Team is therefore less likely to forecast the necessary work to deliver a valuable and usable increment that meets the Definition of Done.

If two Scrum Teams are added to the development of a product that previously had only one Scrum Team, what will be the immediate impact on the productivity of the original Scrum Team?

The first team should spend time on interaction with the other teams and resolve dependencies. In the very beginning the productivity will decrease also because members of the first team will have to do some knowledge transfer to the new teams.

In the middle of the Sprint, a team member was required by another Department Manager to support an important task outside the Sprint work. What is recommended for the team member to do?

The team member should ask the manager to speak with the Scrum Master (Incorrect) The team member should politely decline and explain to the manager about his ownership and accountability for the Scrum Team. He should also ask the manager to speak with the Product Owner (Correct) Explanation If any external authority brings different work, the team should explain about how they self-organize their work in Scrum way. After that, the team can refer them to speak with the Product Owner if the external authority still wants to add this new work.

What are the prerequisites for starting a Sprint Planning

There are no such prerequisites

What is the accountability of the Product Owner during Sprint 0?

There is no such thing as sprint 0.

The Product Goal is in the Product Backlog.

True The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define "what" will fulfill the Product Goal.

When multiple teams are working on the same product, a Developer can be a member of more than one Scrum Team.

True -

The Product Owner can ask the Developers to order the Product Backlog items instead of him/her.

True - The Product Owner can delegate his/her responsibilities to the Developers but he/she stays accountable.

A Product Owner cannot send a representative to the Sprint Review instead of himself.

True - The Product Owner is the sole person responsible for managing the Product Backlog. Therefore, he is the only person responsible for collecting feedback from the stakeholders in order the shape his product's vision. While anyone in the Scrum Team can do the legwork at the Product Owner's discretion (by adding and ordering new Product Backlog Items for example), nobody can replace the Product Owner at the Sprint Review.

When multiple teams are working on the same product, a Developer can be a member of more than one Scrum Team.

True - The Scrum Guide doesn't prohibit it even though it is not considered best practice.None of the Scrum roles are necessarily full-time, and a single person can occupy more than one role or the same role in more than one team; e.g., there may be a special expertise that is needed in multiple teams, but it's not needed in a full-time basis. So, one person can provide that special type of expertise to multiple teams.

Product Backlog Refinement practice ideally focuses on Items for upcoming Sprints, not the current Sprint in progress. True or false?

True - The primary goal of Product Backlog Refinement is to ensure that the Product Backlog is well-groomed and ready for Sprint Planning. While it is IDEAL to focus on items for upcoming Sprints during this practice, some items for the current Sprint can be refined.

Which of the following is a prerequisite for starting the Sprint Planning meeting?

We prefer to have "ready" items at the top of the Product Backlog before Sprint Planning, which is done through Product Backlog refinement. However, nothing stops our flow of Sprints. For example, we do not delay the Sprint because the items are not ready. In such cases, the "unready" items would be selected for the Sprint and refined during the Sprint. "Ready" items are those that are clear and small enough to fit into one Sprint.

When a product grows, it is quite possible that the Product Owner 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 Product Owner to proxy or outsource some of their duties to these people (for example, Scrum Team facing duties)?

When a product grows, it is quite possible that the Product Owner 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 Product Owner to be aided by the aforementioned people, it is NOT acceptable for him/her to attempt to proxy or outsource their Product Ownership duties, especially the Scrum Team facing duties.

Could the Product Owner and the Scrum Master also be Developers of the Scrum Team?

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.

Select all that apply. Empiricism provides...

frequent opportunities to make informed decisions, reducing risk (Correct) frequent opportunities to discuss different possibilities (Correct) frequent opportunities to get info using which uncertainty can be completely eliminated (Incorrect)

What is the main reason for the Scrum Master to be at the Daily Scrum?

test 1 - 117 Does not have to be - The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute time-box. Also, if the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers. Note: The Daily Scrum is an internal meeting to the Developers. Therefore, the Product Owner and the Scrum Master may ATTEND the Daily Scrum as silent observers but they cannot actively PARTICIPATE in the Daily Scrum.

You are the Scrum Master of a newly formed Scrum Team. Select three of the following activities that would probably help the team get started.

test 1 - 26

What are the areas of focus that can help a Product Owner ensure that the product delivers value?

test 1 - 49 Customer Satisfaction, Customer Usage Index, and Customer or user satisfaction gap are Key Value Measures defined in the Evidence-Based Management (EBM) approach. It is an empirical approach that provides organizations with the ability to measure the value they deliver to customers.

What are the reasons why it is important to have only one Product Owner per product?

test 1 - 59

Which three phrases best describes the purpose of a Definition of Done?

test 1 - 66

The Scrum Master serves the Product Owner in several ways, including:

test 1 - 90

What enhances the transparency of an increment?

test 2 - 10 Doing all work needed to meet the definition of "Done"

What portion of the Sprint Backlog needs to be outlined in the Sprint Planning meeting?

test 2 - 16 Sufficient details should be determined to allow the Developers to forecast their work capacity and initiate the Sprint's initial days effectively.

Who can do the legwork of gathering the marketplace data for the Product Owner?

test 2 - 18 Anyone can do the legwork -The Product Owner may or may not be the one doing the legwork of gathering the marketplace data, but he/she should definitely be aware of said data/research.

When multiple Scrum Teams are working on the same product, their Sprints should start and end at the same time.

test 2 - 60 False - It's not mandatory in Scrum.org to start and end the Sprints at the same time. That makes it much more difficult to manage the whole project. It's not mandatory, because you may need it in certain cases: maybe some teams are working on parts of the project that need longer Sprints (four-week), while others need shorter ones (two-week) for shorter feedback loops.

The result of the Sprint Review is...

test 2 - 64 A revised Product Backlog that defines the probable Product Backlog items for the next Sprint

The Developers are required to deliver a done increment by the end of a Sprint. Select two statements that explain what "done" means.

test 2 - 77 The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done.- Developers deliver an Increment of product functionality every Sprint. This Increment is useable, so a Scrum Team may choose to immediately release it. 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.

When the Developers on the Scrum Team determine that they have overcommitted to a Sprint, who have to be present when the Sprint Backlog is reviewed and adjusted?

test 2- 45 If the Developers determine it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner.

An organization decides to have very small Scrum Teams of less than three persons. The likely result could be:

test 3 - 30 Optimal Scrum Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Only 3 Scrum Team members decrease interaction and results in smaller productivity gains. Smaller Scrum Teams may encounter skill constraints during the Sprint, causing the Scrum Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Scrum Teams generate too much complexity for an empirical process to be useful.

During the Sprint:

- No changes are made that would endanger the Sprint Goal; - Quality does not decrease; - The Product Backlog is refined as needed; and, - Scope may be clarified and renegotiated with the Product Owner as more is learned. " - The Scrum Guide (TM) of 2020

Hundreds of developers are identified for a Scrum work. Which two of the following may be appropriate considerations to form these developers into Scrum Teams? (select 2)

Each team must be sized to reduce external dependencies with less internal communication issues (Correct) The team formation should seek input from the business side (Correct) Each team must be a technical component team (Incorrect)

Which of the following is a 'TRUE' statement?

Facilitating discussion and handling conflict resolution is the product owner's responsibility. (Incorrect) A Scrum Team manages itself to commitments. (Correct) Explanation When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. The Scrum Team members learn and explore those values as they work with the Scrum roles, events, and artifacts. Successful use of Scrum depends on people becoming more proficient in living these five values. People personally commit to achieving the goals of the Scrum Team.

The purpose of the Sprint Retrospective is to inspect the outcome of the Sprint and determine future adaptations. True or false?

False

There is a "Development Team" within the Scrum Team

False

Scrum is easy to master

False Scrum is: • Lightweight • Simple to understand • Difficult to master

During the Sprint Planning the Product Owner crafts a Sprint Goal.

False - During the Sprint Planning the Scrum Team crafts a Sprint Goal.

Conflicts should be avoided at all cost on Agile teams. True or false?

False - Managed conflicts can be very helpful to the project. The Scrum Team must always keep a constructive mind though.

All items of the Product Backlog must be written by the Product Owner before being given to the Developers.

False - The Product Owner is responsible for the Product Backlog. Who adds the items and how they are added to the Product Backlog vary widely across organizations, Scrum Teams, and individuals. "Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion."

The Sprint Retrospective marks the beginning of a new Sprint.

False - The Sprint Retrospective is the last event of a Sprint. A new Sprint starts immediately after the conclusion of the previous Sprint.

A Scrum Team can have an exclusive first Sprint to prepare Product Backlog which is the sole outcome from that Sprint

False - The only outcome of each Sprint is a potentially releasable Increment of "Done" product. A "Done" increment is required at the Sprint Review.

Every Developer must answer the three questions during the Daily Scrum.

False - The structure of the meeting is set by the Developers and can be conducted in different ways if it focuses on progress toward the Sprint Goal.

A properly functioning Scrum Team will have at least one Release Sprint.

False - There is no such thing as a "Release Sprint" in Scrum.

If it's not possible to complete the Sprint Backlog, who would try to resolve it?

First of all, it's OK of the Sprint Backlog is not complete until the end of the Sprint. However, we would try to complete it if it's possible. When the Developers find out they are behind schedule they will ask the Product Owner for help and the two roles together will adjust the work (tasks), or reorder the times to make sure the highest value will be created at the end of the Sprint.

A group of stakeholders want to come to the Daily Scrum. How should the Scrum Master handle that situation?

Instruct the stakeholders to remain quiet and refrain from asking questions or making comments; they are allowed to listen in for the sake of transparency but the meeting is for the developers (Correct) Explanation 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. Note: The Daily Scrum is an internal meeting to the Developers. Therefore, the Product Owner and the Scrum Master may ATTEND the Daily Scrum as silent observers but they cannot actively PARTICIPATE in the Daily Scrum.

Which of the following may change during the Sprint?

Product backlog Sprint goal does not change!

At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What could the Scrum Team do? (choose the best answer)

Put the improvements to the Product Backlog and might choose some to the Sprint Backlog. test 2 - The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.

Select all that apply. Scrum Team participates in:

Sprint Retrospective (Correct) Sprint Review (Correct) Sprint Planning (Correct) Daily Scrum (Incorrect) Explanation Only the Developers participate in the Daily Scrum. Not the entire Scrum Team.

During a Sprint Review, the stakeholders notice that the product development progress is not clear and visible. Who is responsible for this lack of transparency?

Test 1 - 113 The Scrum Team - The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.

What are the desired benefits of a Product Owner with a clear Product Vision?

Test 1 - 42 Having a clear and inspiring Product vision helps in motivating and inspiring the people involved and affected by the product. It also provides a common understanding of the direction we are working towards. It also supports the Product Owner in making choices about what to build and what not to build for the Product.

What measures can help determine the success of the product?

Test 1 - 54 As a Product Owner, you have to find a balance in both delivering internal value and external value. Internal measures can be cost savings, FTE reductions, employee satisfaction, time spend on a certain (internal) process, revenues, etc. External measures can be customer satisfaction, NPS, etc....

Which topics are NOT appropriate in a Sprint Retrospective?

Test 1 - 69

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

Test 2 - 4 Nothing. The entire organization must respect a Product Owner's decisions.

Who participate in the Sprint Planning?

Test 2 - 5 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.

In the middle of a Sprint, a team member was required by another department manager to support an important task outside the Sprint work. What is recommended for the team member to do?

Test 3 - 103 The team member should inform the other Scrum Team members so the whole Scrum Team can decide what to do with the inquiry

What does the word 'development' mean in the context of Scrum? (choose the best answer)

Test 3 - 15 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. As Scrum's use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word "developers" in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included.

During the Sprint, the Sprint Goal can be changed

Test 4 - 44 False - No changes are made that would endanger the Sprint Goal. The Sprint Goal, once set during the Sprint Planning meeting, should not be changed during the Sprint. In summary, the Sprint Goal is intended to be a fixed objective for the duration of the Sprint, providing focus and direction to the Scrum Team. While the tasks and approach may adapt, the goal itself remains unchanged to ensure stability, transparency, and effective guidance throughout the Sprint.

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.

Test 5 - 109 False

What can you take into consideration when ordering items in the Product Backlog?

Test 5 - 15 When maximizing the flow of value, the Product Owner needs to consider the business value, user's unmet needs, effort to complete the item, availability of Developers and skills, dependencies within the product and outside of the product, etc. The Development tools and techniques and the availability of the Scrum Master has no direct impact on the flow of value.

Which of the following statements are false? Select all that apply

Test 5 - 46

How important is it for a Product Owner to order Product Backlog items by value points?

Test 5 - 96 Calculating value points is an upfront approach that conflicts with the empiricism of Scrum, and is therefore not acceptable. (Incorrect) It is a good practice, keeping in mind that market reception is the best measure of value (Correct)

Who must attend the Daily Scrum?

The Developers You must be careful of the difference between: - "can" and "must" - "attend" and "participate" The Product Owner CAN ATTEND the Daily Scrum as a silent observer. The Developers MUST PARTICIPATE in the Daily Scrum (actively).

Who is responsible for all estimates in the Product Backlog?

The Developers (Correct) The Product Owner and the Developers (Incorrect) The Developers are responsible for all estimates. The Product Owner may influence the Developers by helping them to understand and select trade-offs, but the people who will perform the work make the final estimate.

Who is allowed to participate in the Daily Scrum?

The Developers (Correct) 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. (Be careful, "participate" is different from "attend").

Who is responsible for ensuring that the work done on a Product Backlog Item meets the Definition of Done?

The Developers - The Developers must follow the Definition of Done and are accountable for the quality of the Product Backlog items.

The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Developers.

The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, the Developers add it to the Sprint Backlog.

The Product Owner must always consider the dependencies of the software tools the Developers use when ordering the Product Backlog

The Product Owner may consider the dependencies between Product Backlog Items but not the dependencies of the software tools used by the Developers.

Who is accountable for promoting and supporting Scrum?

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. The Scrum Master is accountable for the Scrum Team's effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

When multiple Scrum Teams are working on the same product, should they integrate all their work into a single functional increment every Sprint?

The Scrum Teams in a Nexus (Scaled Scrum) produce a single Integrated Increment every Sprint.The Nexus Sprint Review is held at the end of the Sprint to provide feedback on the done Integrated Increment that the Nexus has built over the Sprint and determine future adaptations.

The Sprint Backlog is crafted via the answers of these 3 questions : Why, What and How

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).

Which event is the most appropriate for discussing or updating the Definition of Done?

The Sprint Retrospective The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work

Scrum Team adapts the Definition of Done during

The Sprint Retrospective - The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

The Scrum Team uses the information of Scrum artifacts to make ongoing decisions. The soundness of these decisions depends on:

Artifacts Transparency

How much work must the Developers do to a Product Backlog item they select for a Sprint?

As much as they have informed the Product Owner will be done for every Product Backlog item they select in conformance with the Definition of Done.

How can the Product Owner bring his Product vision to life?

Asking for an approval of the Upper Management. Making the Scrum Master bring the vision to the Scrum Team and the Key Stakeholders. (Incorrect) Articulating the product vision to the Scrum Team and the Key Stakeholders early and often. (Correct) Utilizing the underlying empirical product planning features of Scrum. (Correct) Via the Product Backlog and iterating towards that vision every Sprint. (Correct)

Who is accountable 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 Developers 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 Developers can manage its progress.

For the purpose of transparency, when does Scrum say a new increment must be available?

At the end of every sprint - Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of "Done" product ensure a potentially useful version of working product is always available.

For the first Sprint, the inputs are the Product Backlog and the Projected Capacity of the Developers. What are the additional inputs to the subsequent Sprints?

Defect list from previous Sprint (Incorrect) Last Product Increment (Correct) Sprint Plan (Incorrect) Past performance of the Developers (Correct) Explanation The input to the Sprint Planning is the Product Backlog, the latest product Increment, projected capacity of the Developers during the Sprint, and past performance of the Developers. Note: There is no such thing as "Sprint Plan" in the Scrum framework.

At the end of the Sprint, all items are done except for one that is almost done. What should be done with this item?

Do not include it in the Increment. a. Everything in the Increment must be Done; i.e., 100% DONE! If an item is not done, we won't include it in the Increment and send it back to the Product Backlog. b. The Increment contains only 100% DONE items. c. We only present the Increment, and the Increment contains only the DONE items.

Which two statements explain why the Definition of Done is important to the Scrum Team?

It assures the Increment reviewed at the Sprint review is usable so the Scrum Team may choose to release it. (Correct) It creates transparency regarding progress within the Scrum Team. (Correct) It helps the Scrum Team track the open work during a Sprint. (Incorrect) Explanation It's rather the Kanban board (or other techniques) that helps the Scrum Team track the open work during a Sprint and identifies undone work that can be addressed in a separate Sprint. The Scrum Guide™ of 2020 says : " The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. 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. If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. "

Which statements are correct about Product Backlog refinement?

It is the act of breaking down and further defining Product Backlog items into smaller more precise items (Correct) Multiple teams may participate (Correct) It should be done right before the Sprint Planning (Incorrect) Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work. The Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs.

When multiple teams are working on the same product, who should make sure that their outputs can be integrated into one Increment?

It's up to the Developers of the Scrum Teams to find their way and ensure that their outputs will create an integrated Increment that is potentially releasable.

A Scrum Team uses 2-week Sprints and time box their Sprint Planning to 6 hours. Does this break the rules of Scrum?

No - The concept of "event duration proportional to the sprint duration" used to be mandatory but it has been abandoned in the last updates of the Scrum Guide. It's now only best practice but not mandatory so no rule is broken here.

In general, is it important to have documentation about a product's requirements?

No. Documentation is generally considered a waste of time for experienced teams. (Correct) In Agile : Working Software Over Comprehensive Documentation Historically, enormous amounts of time were spent on documenting the product for development and ultimate delivery. Technical specifications, technical requirements, technical prospectus, interface design documents, test plans, documentation plans, and approvals required for each. The list was extensive and was a cause for the long delays in development. Agile does not eliminate documentation, but it streamlines it in a form that gives the developer what is needed to do the work.In Scrum : We must put all the products requirements in the Product Backlog.

How complete should the Sprint Backlog be at the end of the Sprint Planning meeting?

Not all tasks are identified in the Sprint Planning; just enough to show what the Developers are going to do in the next few days. The rest of the tasks will be created during the Sprint.

Which two of the following may change during the Sprint? (choose the BEST two answers)

Product Backlog (Correct) Sprint Backlog (Correct) Composition of the Scrum Team (Incorrect) Sprint Goal (Incorrect) Explanation - The Product Backlog is an emergent, ordered list of what is needed to improve the product. Attributes often vary with the domain of work. - The Sprint Backlog is updated throughout the Sprint as more is learned. - Composition of the Scrum Team can be changed during the Sprint if needed but it's not best practice. - The Sprint Goal never changes during the Sprint.