Practice Free PSPO-II Exam Online Questions
Question #51
Team A is an excellent Scrum Team with a high velocity. At the 4th Sprint, the Scrum Team decided to lower the frequency of the Daily Scrum. They suggest conducting the Daily Scrum twice a week.
What are the three keys concerns if there are only two Daily Scrum meetings per Sprint? (choose ALL that apply).
- A . The Product Owner cannot make accurate report progress to the stakeholders.
- B . The Developers lose the opportunities to update the Gantt chart properly.
- C . The Sprint Planning might become inaccurate
- D . Impediments are raised and accumulated, and it requires a great effort to resolve.
- E . Lack of opportunities to inspect and adapt the Sprint Backlog
Correct Answer: C,D,E
C,D,E
Explanation:
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.
So as the frequency of the Daily Scrum reduces, the communication becomes ineffective, impediments occur. There is no Gantt chart in the Scrum framework and reporting the project status is not the primary responsibility of a Product Owner.
C,D,E
Explanation:
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.
So as the frequency of the Daily Scrum reduces, the communication becomes ineffective, impediments occur. There is no Gantt chart in the Scrum framework and reporting the project status is not the primary responsibility of a Product Owner.
Question #52
Which best describes testing responsibilities in the Developers? (choose the best two answers)
- A . Everyone in the Developers is responsible for the quality of the product.
- B . Ensuring all test cases created at Sprint Planning have been passed
- C . Sub-team formations (or hierarchies) in the Scrum Team are not allowed.
- D . Increments must be approved by the Tester before it can be deemed releasable
- E . There should be a testing phase at the end of each Sprint
Correct Answer: A,C
A,C
Explanation:
Sub-team formations (or hierarchies) in the Scrum Team is not allowed. Sub-Teams such as testing teams or operation teams are not allowed to be formed in the Scrum Team. Titles are not assigned to the developers within the Scrum Team members, regardless of the type of work they perform. Scrum Team collectively decides on the Scrum Length.
Scrum Team delivers a “Done” product every Sprint to ensure a potentially useful version of a working product is always available. However, it is up to the Product Owner to “Release” it.
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 specific skills needed by the Developers are often broad and will vary with the domain of work.
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; and,
● Holding each other accountable as professionals.
A,C
Explanation:
Sub-team formations (or hierarchies) in the Scrum Team is not allowed. Sub-Teams such as testing teams or operation teams are not allowed to be formed in the Scrum Team. Titles are not assigned to the developers within the Scrum Team members, regardless of the type of work they perform. Scrum Team collectively decides on the Scrum Length.
Scrum Team delivers a “Done” product every Sprint to ensure a potentially useful version of a working product is always available. However, it is up to the Product Owner to “Release” it.
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 specific skills needed by the Developers are often broad and will vary with the domain of work.
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; and,
● Holding each other accountable as professionals.
Question #53
Which of the following actions can provide you with insights into your product’s potential value? (choose the best answer)
- A . Measuring the satisfaction of your customers.
- B . Monitoring feature usage of customers.
- C . Learning about feature requests from customers.
- D . Evaluating your competitors’ products.
- E . All of the above.
- F . None of the above.
Correct Answer: E
E
Explanation:
All of them are correct are Unrealized Value Factors. The potential future value is the Unrealized Value. Unrealized Value (UV)
The potential future value that could be realized if the organization met the needs of all potential customers or users.
Questions that organizations need to continually re-evaluate for UV are:
E
Explanation:
All of them are correct are Unrealized Value Factors. The potential future value is the Unrealized Value. Unrealized Value (UV)
The potential future value that could be realized if the organization met the needs of all potential customers or users.
Questions that organizations need to continually re-evaluate for UV are:
Question #54
An experiment will help you to:
(choose the best answer)
- A . Create reliable estimations.
- B . Understand how users use the product.
- C . Validate or reject a hypothesis.
- D . Create a work plan for a product release.
Correct Answer: C
C
Explanation:
In simplified terms, a hypothesis is a proposed explanation for some observation that has not yet been proven (or disproven). In the context of requirements, it is a belief that doing something will lead to something else, such as delivering feature X will lead to outcome Y. An experiment is a test that is designed to prove or reject some hypothesis.
C
Explanation:
In simplified terms, a hypothesis is a proposed explanation for some observation that has not yet been proven (or disproven). In the context of requirements, it is a belief that doing something will lead to something else, such as delivering feature X will lead to outcome Y. An experiment is a test that is designed to prove or reject some hypothesis.
Question #55
Peter, a young member, has been assigned to a mature Scrum Team. He is surprised why the Product Owner keeps paying attention to the technical debt. He supposes it should be the Developers’s responsibility.
What is the best explanation? (choose the best answer).
- A . The Product Owner concerns the technical debt because it might impact the delivering value and the product’s cost.
- B . Peter is correct. The Product Owner should not concern the technical debt.
- C . The Product Owner, is used to be a developer, might have a basic understanding of programming. Observing the technical debt could refresh her/his knowledge, and it is useful to develop the product’s strategy.
- D . The Product Owner must report the technical debt’s status to stakeholders every Sprint Review.
Correct Answer: A
A
Explanation:
Reduce total cost of ownership by reducing technical debt. A poor technical design or a diluted Definition of Done by the Developers creates quality gaps toward the product quality.
Though the product might work properly, the performance is dramatically slow due to technical debt => impact the delivering value. It might take a great effort to fix the technical debt. Additionally, the organization pays the employee (the Scrum Team, for example) to resolve the technical debt => increase the Total Cost of Ownership (TCO) => impact the product’s cost.
A
Explanation:
Reduce total cost of ownership by reducing technical debt. A poor technical design or a diluted Definition of Done by the Developers creates quality gaps toward the product quality.
Though the product might work properly, the performance is dramatically slow due to technical debt => impact the delivering value. It might take a great effort to fix the technical debt. Additionally, the organization pays the employee (the Scrum Team, for example) to resolve the technical debt => increase the Total Cost of Ownership (TCO) => impact the product’s cost.
Question #56
What are the attributes of a good Product Vision and Strategy? (choose all that apply)
- A . It describes how the product compares to competitor products
- B . It describes how the product will generate revenue
- C . It describes how people will use the product to achieve outcomes.
- D . It describes who will use the product and what they would like to achieve
Correct Answer: A,B,C,D
A,B,C,D
Explanation:
All of them are correct.
The Product vision describes the purpose of a Product, the intention with which the Product is being created and what it aims to achieve for customers and users.
The Product vision describes a future state of the Product and what problems it tries to resolve or what ambitions it tries to fulfill. Having a clear and inspiring Product vision helps in motivating and inspiring
people, like the Developers, the stakeholders and customers and users. It also provides a common understanding of the direction we want to move towards. Besides that, the Product vision also supports the Product Owner in making choices about what to build and what not to build for the Product.
A,B,C,D
Explanation:
All of them are correct.
The Product vision describes the purpose of a Product, the intention with which the Product is being created and what it aims to achieve for customers and users.
The Product vision describes a future state of the Product and what problems it tries to resolve or what ambitions it tries to fulfill. Having a clear and inspiring Product vision helps in motivating and inspiring
people, like the Developers, the stakeholders and customers and users. It also provides a common understanding of the direction we want to move towards. Besides that, the Product vision also supports the Product Owner in making choices about what to build and what not to build for the Product.
Question #57
The Product Owner is also accountable for effective Product Backlog management, which includes (choose ALL that apply).
- A . Estimating the size of the Product Backlog Items at the high-level.
- B . Decomposing large Product Backlog Items into workable smaller Product Backlog Items.
- C . Eliminating or reducing dependencies between Product Backlog Items.
- D . Spending time to discuss and review the Product Backlog with stakeholders.
- E . Ordering the Product Backlog.
Correct Answer: B,C,D,E
B,C,D,E
Explanation:
The Product Owner is accountable for effective Product Backlog management, which includes:
1) Developing and explicitly communicating the Product Goal.
2) Creating and Clearly expressing Product Backlog items.
3) Ordering the items in the Product Backlog to best achieve goals and missions.
4) Ensuring that the Product Backlog is visible, transparent, and clear to all. The Product Owner can delegate above to others however remains accountable for it.
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. 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 are responsible for all work effort estimations in the Product Backlog. The Product Owner may influence the Developers by helping them understand and select tradeoffs, but the people who will perform the work make the final estimate.
B,C,D,E
Explanation:
The Product Owner is accountable for effective Product Backlog management, which includes:
1) Developing and explicitly communicating the Product Goal.
2) Creating and Clearly expressing Product Backlog items.
3) Ordering the items in the Product Backlog to best achieve goals and missions.
4) Ensuring that the Product Backlog is visible, transparent, and clear to all. The Product Owner can delegate above to others however remains accountable for it.
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. 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 are responsible for all work effort estimations in the Product Backlog. The Product Owner may influence the Developers by helping them understand and select tradeoffs, but the people who will perform the work make the final estimate.
Question #58
Your department has several teams working on different products at the same time.
Which of the following would be the best approach if managers want to understand the status of each team? (choose the best answer)
- A . Ask the teams to collaborate and develop a common way to share their goals and achievements toward their goals for each planning period.
- B . Have a common status reporting tool that each team will fill out and can be shared with the managers.
- C . Have the teams created a comprehensive project plan and track their work against the plan.
- D . Have the teams standardize their estimation practices across all teams to make it easier to compare
the performance of each team.
Correct Answer: A
A
Explanation:
Agile teams are structured and empowered by the organization to organize and manage their own work. The teams are responsible for applying the most appropriate practices to provide transparency in order to optimize value and control risk.
A
Explanation:
Agile teams are structured and empowered by the organization to organize and manage their own work. The teams are responsible for applying the most appropriate practices to provide transparency in order to optimize value and control risk.
Question #59
A company wants to hire you to lead their agile transformation. They have learned about the benefits of being agile but want to know how to measure the success of the initiative.
What advice would you provide? (choose the best answer)
- A . The number of projects delivered on-time, on-budget, and on-scope will increase.
- B . The improvement in customer outcomes.
- C . All of the above.
- D . The average team velocity will continuously improve.
- E . The level of agility is proportionate to the number of teams doing Scrum.
Correct Answer: B
B
Explanation:
Successful agile transformation increases business value, which can be measured by customer happiness
B
Explanation:
Successful agile transformation increases business value, which can be measured by customer happiness
Question #59
A company wants to hire you to lead their agile transformation. They have learned about the benefits of being agile but want to know how to measure the success of the initiative.
What advice would you provide? (choose the best answer)
- A . The number of projects delivered on-time, on-budget, and on-scope will increase.
- B . The improvement in customer outcomes.
- C . All of the above.
- D . The average team velocity will continuously improve.
- E . The level of agility is proportionate to the number of teams doing Scrum.
Correct Answer: B
B
Explanation:
Successful agile transformation increases business value, which can be measured by customer happiness
B
Explanation:
Successful agile transformation increases business value, which can be measured by customer happiness