Practice Free PSPO-II Exam Online Questions
Question #71
How much of the Sprint Backlog must be define d during Sprint Planning? (choose the best answer)
- A . Enough so the Developers can create a forecast of what they can do during the Sprint.
- B . All of the potential work. Sprint Planning is not over until 100% of the work is identified and estimated.
- C . Just enough to understand design and architectural implications.
- D . Just enough tasks for the Scrum Master to be confident in the Developer’s understanding of the Sprint.
Correct Answer: A
A
Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal 1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment2. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum2. 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 learn more about the work needed to achieve the Sprint Goal2. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint3. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint.
Reference: 1: Sprint Backlog, 2: The Scrum Guide, 3: Commitment vs. Forecast
A
Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal 1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment2. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum2. 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 learn more about the work needed to achieve the Sprint Goal2. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint3. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint.
Reference: 1: Sprint Backlog, 2: The Scrum Guide, 3: Commitment vs. Forecast
Question #72
Yasmine, a Product Owner, sees that sales for his product is declining whereas a competitor’s is increasing.
Which Key Value Areas (KVA) can help Yasmine analyze and decide what to do next? (choose the best two answers)
- A . Time to Market
- B . Unrealized Value
- C . Current Value
- D . Ability to Innovate
Correct Answer: B,C
B,C
Explanation:
Focus first on whether or how your product delivers value to customers (Current Value), as well as whether your customers have unmet needs that your competitors are more effectively meeting (Unrealized Value).
B,C
Explanation:
Focus first on whether or how your product delivers value to customers (Current Value), as well as whether your customers have unmet needs that your competitors are more effectively meeting (Unrealized Value).
Question #73
An effective Product Owner must: (choose the best answer)
- A . Be the "expert" opinion for all Product Backlog items.
- B . All of the above.
- C . Ensure that the team is a productive as possible.
- D . None of the above
- E . Be the single point of contact for all stakeholders.
- F . Ensure that every stakeholder need is met.
Correct Answer: D
D
Explanation:
All are incorrect.
* Ensure that every stakeholder’s need is met.
This is a hard job! It’s a job in which you can’t satisfy everyone. Maybe you have a product that has been highly successful, has very happy customers (very low satisfaction gaps), and commands enviable market share.
* Be the "expert" opinion for all Product Backlog items.
It not correct saying that a Product Owner is the expert opinion. A product Owner is a decision maker, the collaborator, and the visionary.
The Visionary, clearly communicating the product vision, strategy, business goals and objectives with all the relevant parties. A visionary Product Owner tends to focus on the future, on changing the status quo and helping people to see what could be, instead of what is. The Collaborator, engaging with, and closely working together with the various stakeholders and Scrum Teams. A collaborative Product Owner tends to support people in their own discovery process, whether it’s about defining goals, clarifying PBIs or analyzing customer needs. The Decision Maker, which helps the stakeholders and Scrum Team to keep time-to-market short, by keeping decision making time short. All sorts of decisions have to made on a daily basis. Some can be delegated to the Scrum Team or stakeholders, some the
Product Owner has to take him/herself.
* Ensure that the team is as productive as possible.
Scrum is focus on the delivery of value rather than keeping individuals busy. Are your Developers busy around the clock but little work is actually delivered at the end of the Sprint? Then there might be a possibility that your team trumps individual efficiency over effective delivery of value. * Be the single point of contact for all stakeholders.
The Scrum team should have a close relationship with the stakeholders, not only the Product Owner
D
Explanation:
All are incorrect.
* Ensure that every stakeholder’s need is met.
This is a hard job! It’s a job in which you can’t satisfy everyone. Maybe you have a product that has been highly successful, has very happy customers (very low satisfaction gaps), and commands enviable market share.
* Be the "expert" opinion for all Product Backlog items.
It not correct saying that a Product Owner is the expert opinion. A product Owner is a decision maker, the collaborator, and the visionary.
The Visionary, clearly communicating the product vision, strategy, business goals and objectives with all the relevant parties. A visionary Product Owner tends to focus on the future, on changing the status quo and helping people to see what could be, instead of what is. The Collaborator, engaging with, and closely working together with the various stakeholders and Scrum Teams. A collaborative Product Owner tends to support people in their own discovery process, whether it’s about defining goals, clarifying PBIs or analyzing customer needs. The Decision Maker, which helps the stakeholders and Scrum Team to keep time-to-market short, by keeping decision making time short. All sorts of decisions have to made on a daily basis. Some can be delegated to the Scrum Team or stakeholders, some the
Product Owner has to take him/herself.
* Ensure that the team is as productive as possible.
Scrum is focus on the delivery of value rather than keeping individuals busy. Are your Developers busy around the clock but little work is actually delivered at the end of the Sprint? Then there might be a possibility that your team trumps individual efficiency over effective delivery of value. * Be the single point of contact for all stakeholders.
The Scrum team should have a close relationship with the stakeholders, not only the Product Owner
Question #74
Mike, the Product Owner, is surprised about the accumulated technical debt that slows down the product performance. The product is projected not to be able to serve a large number of customers. Ron is shocked that it might need several Sprints to address the scalability issue.
What factors have led to this situation? (choose ALL that apply)
- A . The Developers have not been paying enough attention to technical quality.
- B . The past Sprint Retrospectives had not been utilized for inspection and adaptation.
- C . The Scrum Master has not ensured the transparency of the Scrum Team.
- D . The Product Owner and the Developers are not having conversations about technical debt.
Correct Answer: A,B,C,D
A,B,C,D
Explanation:
Each component within the Scrum framework serves a specific purpose and is essential to Scrum’s success and usage. Scrum’s roles, events, artifacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum.
As the Developers did not pay attention to the technical quality, technical debt was generated. Problems should be discussed in the Sprint Retrospective. The Scrum team did not use the Retrospective effectively to solve the issue.
The Scrum Master did not complete his responsibility, he should facilitate a meeting between the Product Owner and the Developers to discuss the technical debt.
A,B,C,D
Explanation:
Each component within the Scrum framework serves a specific purpose and is essential to Scrum’s success and usage. Scrum’s roles, events, artifacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum.
As the Developers did not pay attention to the technical quality, technical debt was generated. Problems should be discussed in the Sprint Retrospective. The Scrum team did not use the Retrospective effectively to solve the issue.
The Scrum Master did not complete his responsibility, he should facilitate a meeting between the Product Owner and the Developers to discuss the technical debt.
Question #75
The Definition of Done is used to: (choose the best three answers)
- A . Increase transparency.
- B . Create a shared understanding of when work is complete
- C . Describe the purpose, objective, and timebox of each Scrum Event.
- D . Inform the Developers on how many Product Backlog items to select in a Sprint.
- E . Describe the work that must be done before the Sprint can be declared complete.
Correct Answer: A,B,E
A,B,E
Explanation:
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 returns to the Product Backlog for future consideration. All members of a Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency.
A,B,E
Explanation:
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 returns to the Product Backlog for future consideration. All members of a Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency.
Question #76
You work for a large financial institution. Your products have many interdependencies: you have mobile, web, and ATM product interfaces to financial products like savings, checking, credit card, and investments. When any of these financial products change, the changes ripple throughout the mobile, web, and ATM clients, and maintaining consistency is challenging.
What should you do to reduce this problem? (choose the best answer)
- A . Form products that are as independent as possible and let each product determine their own release plans, but ensure coordination.
- B . Create a centralized, coordinated cross-product Development Plan to ensure consistency.
- C . Appoint an overall Product Owner to oversee all the products.
- D . Ensure that the PMO manages the inter-product dependencies.
- E . All of the above.
Correct Answer: A
A
Explanation:
What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.”
The ordering of the Product Backlog is a key mechanism for reducing and eliminating dependencies. Dependencies are things that need to happen for an Agile in scale to complete an increment of value, but that cannot be achieved by the team alone. Dependencies, if not handled correctly, lead to blockers in task execution.
In scrum, the product backlog is the main planning tool used to inform the direction of the team. Broadly speaking, the product backlog consists of tasks (often called stories or user stories) with well-defined acceptance criteria. A good user story is scoped and written to follow INVEST (independent, negotiable, valuable, estimable, small, and testable). The concept of independence is key to the idea of managing external dependencies. If a piece of work is completely independent, it has no dependencies whatsoever. While this is something we should strive for, it is not always attainable. There is value in cross-functional, cross-vertical initiatives, and so we must plan for and manage dependencies.
A
Explanation:
What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.”
The ordering of the Product Backlog is a key mechanism for reducing and eliminating dependencies. Dependencies are things that need to happen for an Agile in scale to complete an increment of value, but that cannot be achieved by the team alone. Dependencies, if not handled correctly, lead to blockers in task execution.
In scrum, the product backlog is the main planning tool used to inform the direction of the team. Broadly speaking, the product backlog consists of tasks (often called stories or user stories) with well-defined acceptance criteria. A good user story is scoped and written to follow INVEST (independent, negotiable, valuable, estimable, small, and testable). The concept of independence is key to the idea of managing external dependencies. If a piece of work is completely independent, it has no dependencies whatsoever. While this is something we should strive for, it is not always attainable. There is value in cross-functional, cross-vertical initiatives, and so we must plan for and manage dependencies.
Question #77
A "cone of uncertainty" can be used to do what? (choose the best answer)
- A . Visualize the uncertainty of the potential value that a Scrum Team delivers over time.
- B . Rapidly identify and prioritize all uncertainties.
- C . Determine whether to cut quality, similar to the "Iron Triangle" of project management.
- D . Represent the relative level of difficulty for predicting the velocity of individual team members.
Correct Answer: A
A
Explanation:
Cone of Uncertainty describes the evolution of the amount of best case uncertainty during a project. At the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty. As more research and development is done, more information is learned about the project, and the uncertainty then tends to decrease, reaching 0% when all residual risk has been terminated or transferred
A
Explanation:
Cone of Uncertainty describes the evolution of the amount of best case uncertainty during a project. At the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty. As more research and development is done, more information is learned about the project, and the uncertainty then tends to decrease, reaching 0% when all residual risk has been terminated or transferred
Question #78
True or False: Achieving organizational goals is the accountability of the managers.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Anyone involved in doing the work or contributing towards the goals are accountable for finding the best ways of achieving those goals.
B
Explanation:
Anyone involved in doing the work or contributing towards the goals are accountable for finding the best ways of achieving those goals.
Question #78
True or False: Achieving organizational goals is the accountability of the managers.
- A . True
- B . False
Correct Answer: B
B
Explanation:
Anyone involved in doing the work or contributing towards the goals are accountable for finding the best ways of achieving those goals.
B
Explanation:
Anyone involved in doing the work or contributing towards the goals are accountable for finding the best ways of achieving those goals.
Question #80
The Product Owner should talk to customers? Choose the best answer
- A . False
- B . True
Correct Answer: B
B
Explanation:
Yes! And generally the more the better.
B
Explanation:
Yes! And generally the more the better.