Latest Scrum PSPO-I PDF and Dumps (2024) Free Exam Questions Answers
Pass Your Professional Scrum Product Owner PSPO-I Exam on Jul 15, 2024 with 175 Questions
The Product Owner is a critical role in the Scrum framework. The Product Owner is responsible for defining the product vision, creating and prioritizing the product backlog, and ensuring that the Development Team has a clear understanding of the product backlog items. The Product Owner also works closely with stakeholders to ensure that the product meets the needs of the customers.
NEW QUESTION # 41
Does a Product Backlog item have an item "Owner".
- A. False
- B. True
Answer: A
NEW QUESTION # 42
Scrum events are a formal opportunity for inspecting and adapting.
- A. False
- B. True
Answer: B
NEW QUESTION # 43
There can be more than one Sprint Goals (for one single Sprint).
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 44
True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.
- A. False
- B. True
Answer: B
Explanation:
Explanation
* The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an
* opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
* Stakeholders are people external to the Scrum Team who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. Stakeholders provide valuable input, feedback, and insights to the Scrum Team regarding the product vision, goals, value proposition, requirements, features, functions, quality, usability, or market conditions.
* Collecting stakeholder feedback is one of the main purposes of the Sprint Review. Stakeholder feedback can help the Scrum Team to:
* Assess the value and quality of the product Increment and identify any gaps or issues that need to be addressed.
* Understand the needs and expectations of the customers and users and discover new opportunities or ideas for improvement or innovation.
* Align and collaborate with the stakeholders on the product direction and priorities and ensure transparency and trust.
* Adapt the Product Backlog based on the feedback and data and plan for the next Sprint.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
* Stakeholders: https://www.agilealliance.org/glossary/stakeholders
NEW QUESTION # 45
A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team. Which of the following can be delegated to others, while the Product Owner remains accountable for the work?
(choose the best two answers)
- A. Ordering Product Backlog items.
- B. Attending the Sprint Retrospective.
- C. Attending the Sprint Review.
- D. Developing and communicating the Product Goal.
Answer: B,C
Explanation:
Explanation
A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team. However, they can delegate some of their responsibilities to others, while still remaining accountable for the work. Two of the responsibilities that can be delegated to others are:
* Attending the Sprint Retrospective. The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition
* of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness.
The Product Owner may attend the Sprint Retrospective as one of the Scrum Team members who has a stake in the outcome of the product development. However, they can also choose not to attend or delegate their attendance to someone else who can represent their interests and perspectives.
* Attending the Sprint Review. The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration. The Product Owner is accountable for ensuring that key stakeholders attend the Sprint Review and that they understand what has been done and what can be done next. However, they can also delegate some of their tasks to others who can facilitate or present the Increment on their behalf.
Other options, such as ordering Product Backlog items or developing and communicating the Product Goal, are not responsibilities that can be delegated to others by the Product Owner. They are essential accountabilities that only the Product Owner can perform.
References:
* [Scrum Guide], page 6, section "Product Owner"
* [Scrum Guide], page 18, section "Sprint Retrospective"
* [Scrum Guide], page 17, section "Sprint Review"
* [Scrum Guide], page 11, section "Product Backlog"
* [Scrum Guide], page 10, section "Product Goal"
NEW QUESTION # 46
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)
- A. At the Sprint Planning Event.
- B. Never. The entire Scrum Team is accountable for creating value every Sprint.
- C. Whenever a team member can accommodate more work.
- D. During the Daily Scrum.
Answer: B
Explanation:
answer: D. Never. The entire Scrum Team is accountable for creating value every Sprint.
Explanation: According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team's progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.
References:
* [Scrum Guide], section 2.2: "The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required."
* Accountabilities in Scrum | Scrum.org: "Scrum has three accountabilities, each with a different focus :
Product Owner (green figure) The "What". With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building something that is Done - that the increment is useable and potentially releasable."
* What is a Developer in Scrum? | Scrum.org: "The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal"
NEW QUESTION # 47
Which is NOT a valid consideration when ordering a Product Backlog?
(choose the best answer)
- A. Tools and techniques.
- B. Dependencies on other Product Backlog items.
- C. Importance to customers.
- D. Risk.
- E. Alignment with business strategy and goals.
Answer: A
Explanation:
* The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
* The Product Owner is accountable for ordering the Product Backlog. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. The order of the Product Backlog items provides a clear and consistent indication of what is most important and urgent for the product. The order of the Product Backlog items also helps the Scrum Team and the stakeholders to plan and forecast effectively.
* The tools and techniques used to create, manage, or refine the Product Backlog are not a valid consideration when ordering the Product Backlog. The tools and techniques are means to an end, not an end in themselves. The tools and techniques do not affect the value or quality of the product or service delivered. The tools and techniques may vary from one Product Owner to another, depending on their preferences, skills, or context. The tools and techniques may also change over time, as new technologies or practices emerge or evolve.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
NEW QUESTION # 48
The Scrum Master is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 49
How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?
(choose the best answer)
- A. A proportional amount of time on analysis, design, development, and testing.
- B. All development work and at least some testing.
- C. As much as is required to meet the Scrum Team's Definition of Done.
- D. As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
Answer: C
Explanation:
* The Developers are the people in the Scrum Team who are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* 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 Definition of Done is used to assess when work is complete on the product Increment.
* The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.
* The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product.
* The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are:
* As much as they can fit into the Sprint, with remaining work deferred to the next Sprint: This is a too vague and unrealistic measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the timebox or scope of the Sprint. It may lead to incomplete or unfinished work, technical debt, or scope creep.
* All development work and at least some testing: This is a too arbitrary and insufficient measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the Definition of Done or the potentially releasable nature of the Increment. It may lead to low-quality or unusable work, defects, or rework.
* A proportional amount of time on analysis, design, development, and testing: This is a too restrictive and prescriptive measure for the amount of work required of the Developers. It does not account for the complexity or variability of the product functionality delivered. It also does not respect the self-organization or cross-functionality of the Developers. It may lead to over-engineering or waste.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
NEW QUESTION # 50
True or False: A Product Owner should measure product value by the increase in the team's velocity.
- A. False
- B. True
Answer: A
Explanation:
A Product Owner should not measure product value by the increase in the team's velocity. This is because:
* Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done.
* Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good.
* Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals.
* A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data, market share, return on investment, or social impact.
References:
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 10, section "Definition of Done"
* [Scrum Guide], page 15, section "Sprint Backlog"
* [Professional Scrum Product Owner™ Training], page 5, section "Product Value"
* [Professional Scrum Product Owner™ Training], page 9, section "Business Strategy"
NEW QUESTION # 51
Which two things are appropriate for a Scrum Master to do, if the Scrum Team does not have the tools and environment to completely finish each selected Product Backlog item?
(choose the best two answers)
- A. Declare the Scrum Team not ready for Scrum.
- B. Refocus the current Sprint on establishing the Scrum Team's environment instead of delivering an Increment.
- C. Encourage the Product Owner to accept partially done Increments until the situation improves.
- D. Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances.
- E. Coach the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly.
Answer: D,E
Explanation:
Explanation
Scrum
Explore
The correct answers are A and D.
A: Coach the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly. This is an appropriate action for a Scrum Master, as it helps the Scrum Team to overcome the impediments that prevent them from delivering a potentially releasable Increment. The Definition of Done should reflect the current reality of the Scrum Team, but also be a source of continuous improvement12.
D: Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances. This is also an appropriate action for a Scrum Master, as it ensures that the Scrum Team has a clear and shared understanding of what it means to complete a Product Backlog item. The Definition of Done should be realistic and achievable, but also challenging and ambitious12.
B: Refocus the current Sprint on establishing the Scrum Team's environment instead of delivering an Increment. This is not an appropriate action for a Scrum Master, as it violates the purpose of the Sprint, which is to deliver a valuable product Increment that meets the Sprint Goal. The Scrum Team should not change the Sprint Goal or scope during the Sprint, unless the Product Owner decides to cancel the Sprint3.
C: Encourage the Product Owner to accept partially done Increments until the situation improves. This is not an appropriate action for a Scrum Master, as it compromises the quality and value of the product. The Product Owner should only accept Increments that meet the Definition of Done and the acceptance criteria. Partially done Increments increase technical debt and risk, and reduce transparency and feedback12.
E: Declare the Scrum Team not ready for Scrum. This is not an appropriate action for a Scrum Master, as it undermines the Scrum values and principles. The Scrum Master should support the Scrum Team in adopting and applying Scrum, regardless of the challenges and constraints they face. The Scrum Master should foster a culture of empiricism, self-organization, collaboration, and continuous improvement.
NEW QUESTION # 52
Which topics should be discussed in the Sprint Review?
(choose the best answer)
- A. The Scrum process, and how it was used during the Sprint.
- B. Coding and engineering practices.
- C. The product Increment.
- D. All of the above.
Answer: C
Explanation:
Explanation
The main topic of discussion is the product Increment, which is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints1. The product Increment is demonstrated and inspected by the attendees, and feedback is collected to inform the next Sprint Planning12.
The Sprint Review may also include other topics, such as the Product Backlog, the Product Goal, the market conditions, the budget, and the timeline, but the product Increment is the essential topic1234. The Scrum process, and how it was used during the Sprint, is not a topic for the Sprint Review, but rather for the Sprint Retrospective, which is a separate event where the Scrum Team inspects and adapts its way of working1.
Coding and engineering practices are also not relevant for the Sprint Review, as they are internal aspects of the Development Team that do not affect the value of the product Increment1. Therefore, the correct answer is C.
The product Increment.
NEW QUESTION # 53
During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?
(choose the best answer)
- A. During the Daily Scrum after the Developers approve it.
- B. When the Product Owner identifies new work.
- C. When the Scrum Master has time to enter it.
- D. As soon as possible after it is identified.
Answer: D
Explanation:
Explanation
New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:
It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.
It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.
It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.
References:
Scrum Guide 2020, page 6: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." Scrum Guide 2020, page 6: "The Developers are accountable for ... organizing and managing their work." Scrum Guide 2020, page 10: "The Sprint Goal is a single objective for the Sprint." Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done." Scrum Guide 2020, page 14: "The Sprint Backlog is composed of ... all of the work needed to deliver a product Increment that meets the Definition of Done." Scrum Guide 2020, page 14: "The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned."
NEW QUESTION # 54
The timebox for a Daily Scrum is?
(choose the best answer)
- A. Two minutes per person.
- B. The same time of day every day.
- C. 4 hours.
- D. 15 minutes.
Answer: D
Explanation:
The Scrum Guide states that "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."1 The Daily Scrum is a quick and simple planning meeting designed to keep everyone in the loop with how other team members are getting on. It ensures that team members are fully aligned with each other and on track to hit the Sprint Goal.
Reference:
1: The Scrum Guide2, page 11
2: The Scrum Guide
NEW QUESTION # 55
Changes that endanger the Sprint Goal achievement are allowed.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 56
In the middle of the Sprint, the customer decides that there are two new features she wants.
The Product Owner could:
(choose the best two answers)
- A. Have the Scrum Master add these features to the current Sprint.
- B. Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal.
- C. Introduce these features at the next Daily Scrum.
- D. Add these features to the Product Backlog.
Answer: B,D
Explanation:
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
A Sprint is a timebox of one month or less within which a "Done" product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
In the middle of a Sprint, if a customer decides that there are two new features she wants, there are two possible ways that a Product Owner could handle this situation:
Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal: The Product Owner could discuss with the Developers if they have enough capacity and skills to accommodate these new features in their current Sprint Backlog. The Product Owner could also explain why these features are valuable or urgent for the customer or user. The Developers could then decide if they can or want to add these features to their current work plan, or if they prefer to defer them to a future Sprint. The Developers should not compromise on quality or scope to fit these features in their current Sprint. The Developers should also ensure that these features are aligned with or support the current Sprint Goal.
Add these features to the Product Backlog: The Product Owner could add these new features to the Product Backlog as new items. The Product Owner could then order these items based on their value, risk, priority, dependency, feedback, or market conditions. The Product Owner could also refine these items with more details or acceptance criteria. The Product Owner could then plan to include these items in a future Sprint, depending on their order and availability.
The other options are not valid or relevant ways that a Product Owner could handle this situation. They are either too disruptive, impractical, or irrelevant. They are:
Introduce these features at the next Daily Scrum: This is not a valid way for a Product Owner to handle this situation. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers. However, introducing new features at this event would be disruptive and inappropriate for both parties.
Have the Scrum Master add these features to the current Sprint: This is not a valid way for a Product Owner to handle this situation. The Scrum Master is not responsible for adding or removing any work from the current Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
Reference:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
NEW QUESTION # 57
How should the Developers react, when they realize that they have overcommitted themselves in a Sprint?
- A. They should collaborate with the Product Owner and decide together how to adjust the Sprint Backlog.
- B. They should keep this information to themselves until the next Sprint Review.
- C. They should ask the Scrum Master to cancel the Sprint.
Answer: A
NEW QUESTION # 58
True or False: All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
- A. False
- B. True
Answer: B
Explanation:
* The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
* The Product Owner is accountable for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
The Scrum Team does not work on anything that is not in the Product Backlog. The Scrum Team does not add or remove anything from the Product Backlog without consulting with the Product Owner. The Scrum Team does not accept or implement any requests or changes that are not in the Product Backlog.
The Scrum Team does not create any other artifacts or documents that are not derived from or related to the Product Backlog.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
NEW QUESTION # 59
True or False: The Product Owner makes sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders.
- A. False
- B. True
Answer: A
Explanation:
The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3]. The Product Owner does not have the authority to tell the Developers how much work they should do, as this would violate the principle of self-management4.
Reference:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: The Scrum Guide, November 2020, p. 6
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 60
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
- A. Add security concerns to the Definition of Done.
- B. Have the Scrum Team create Product Backlog items for each concern.
- C. Delegate the work to the security department.
- D. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
- E. Add a Sprint to specifically resolve all security concerns.
Answer: A,B
Explanation:
Explanation
These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders. References:
* Scrum Guide, page 14: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."
* Scrum Guide, page 15: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."
NEW QUESTION # 61
What does it mean to say that an event has a timebox?
(choose the best answer)
- A. The event must happen by a given time.
- B. The event can take no more than a maximum amount of time.
- C. The event must take at least a minimum amount of time.
- D. The event must happen at a set time.
Answer: B
Explanation:
To say that an event has a timebox means that the event has a fixed duration that cannot be exceeded. The Scrum Guide states that "All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process."1 This means that the timebox sets an upper limit for the event, but the event can end sooner if the goal is met.
Reference:
1: The Scrum Guide2, page 10
2: The Scrum Guide
NEW QUESTION # 62
Which three of the following are true about Scrum?
(choose the best three answers)
- A. Scrum is a framework for developing and sustaining complex products.
- B. Scrum is based on empiricism and lean thinking.
- C. Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products.
- D. Scrum implements self-management by replacing Project Managers with Scrum Masters.
- E. Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment.
Answer: A,B,C
Explanation:
Explanation
The following are true about Scrum:
* Scrum is based on empiricism and lean thinking. Empiricism is the principle of making decisions based on what is observed and experienced, rather than on theory or speculation. Lean thinking is the philosophy of eliminating waste and maximizing value in any process or system. Scrum applies these concepts by providing a framework for inspecting and adapting the product and the process, and by focusing on delivering the most valuable features to the customers and stakeholders.
* Scrum is a framework for developing and sustaining complex products. A complex product is one that has unpredictable or unknown aspects that require creativity, experimentation, and adaptation to deliver.
A framework is a set of minimal and essential rules and roles that provide structure and guidance, but leave room for flexibility and innovation. Scrum provides such a framework for teams to collaborate and deliver complex products iteratively and incrementally, while embracing change and feedback.
* Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products. Scrum consists of three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). Each of these components has a clear definition, accountability, and goal that contributes to the overall effectiveness and value of Scrum.
Removing or changing any of these components may cause the benefits of Scrum to be lost or diminished.
References:
* Scrum Guide 2020, page 3: "Scrum is founded on empiricism and lean thinking."
* Scrum Guide 2020, page 3: "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."
* Scrum Guide 2020, page 4: "Each component within the framework serves a specific purpose and is essential to Scrum's success and usage."
NEW QUESTION # 63
What might indicate to a Product Owner that she needs to work more with the Scrum Team?
(choose the best answer)
- A. The acceptance criteria do not appear to be complete.
- B. People leave the Scrum Team.
- C. The Increment presented at the Sprint Review does not reflect what she thought she had asked for.
- D. She is not working full time with the Scrum team.
Answer: C
Explanation:
One of the possible indicators that a Product Owner needs to work more with the Scrum Team is when the Increment presented at the Sprint Review does not reflect what she thought she had asked for. This means that there is a gap or a misunderstanding between the Product Owner and the Developers regarding the Product Backlog items, the acceptance criteria, the Definition of Done, or the product vision and goals.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets her expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
If the Increment presented at the Sprint Review does not reflect what the Product Owner thought she had asked for, it may indicate that there was insufficient or ineffective communication, collaboration, or alignment between the Product Owner and the Developers during the Sprint. This may result in wasted effort, rework, delays, or dissatisfaction for both parties. To avoid or resolve this situation, the Product Owner needs to work more with the Scrum Team by doing some of the following actions:
Engage in frequent and regular interactions with the Developers throughout the Sprint to clarify, refine, and review the Product Backlog items and their acceptance criteria.
Provide clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item.
Involve key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
Empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards.
Solicit and incorporate feedback from the Developers on how to improve or simplify the Product Backlog items or their acceptance criteria.
Inspect and adapt based on empirical evidence from testing, data, or customer feedback.
Reference:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
NEW QUESTION # 64
......
PSPO-I Dumps for Professional Scrum Product Owner Certified Exam Questions and Answer: https://www.examtorrent.com/PSPO-I-valid-vce-dumps.html
PSPO-I Free Exam Study Guide! (Updated 175 Questions): https://drive.google.com/open?id=1xS85a_oAthlj-yWfXHD1nGs6p0i_SqAK
