Latest [Apr 25, 2024] PSPO-I Exam with Accurate Professional Scrum Product Owner I PDF Questions
Take a Leap Forward in Your Career by Earning Scrum 160 Questions
NEW QUESTION # 65
Which of the following should a Scrum Master do to start a project?
- A. Ask the Development Team to introduce themselves to each other and tell about their skills and background.
- B. Ensure, that all team members have a first ticket assigned to them.
- C. Ask the Lead Developer to explain the IT architecture.
Answer: A
NEW QUESTION # 66
What are the two responsibilities of testers in a Scrum Team?
(choose the best two answers)
- A. Tracking quality metrics.
- B. Finding bugs.
- C. Scrum has no "tester" role.
- D. Verifying the work of programmers.
- E. The Developers are responsible for quality.
Answer: C,E
Explanation:
Explanation
Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as "tester", "analyst", "designer", or "architect".
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 Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.
The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.
The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum Quality: https://www.scrum.org/resources/blog/quality-scrum-value
NEW QUESTION # 67
Each artifact contains a commitment. For the Sprint Backlog, it is the:
- A. Definition of Done
- B. Definition of Ready
- C. Sprint Goal
- D. Product Goal
Answer: C
NEW QUESTION # 68
Which is NOT a valid consideration when ordering a Product Backlog?
(choose the best answer)
- A. Dependencies on other Product Backlog items.
- B. Importance to customers.
- C. Tools and techniques.
- D. Risk.
- E. Alignment with business strategy and goals.
Answer: C
Explanation:
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 # 69
Who can cancel a Sprint?
(choose the best answer)
- A. The Scrum Master
- B. The Product Owner.
- C. The Scrum Team.
- D. The Stakeholders.
Answer: B
Explanation:
Explanation
The Product Owner is the sole person responsible for managing the Product Backlog and ensuring that the value of the work the Scrum Team performs is understood by everyone involved. The Product Owner is the only person who can cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master1. A Sprint can be cancelled before the Sprint time-box is over.
Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense1. References:
* Scrum Guide
* Sprint Cancellation
* Can Scrum Master cancel a sprint?
NEW QUESTION # 70
How do changes in the project environment impact the Product Backlog?
- A. The Product Backlog should be kept high-level enough to tolerate such changes.
- B. The old baselined Product Backlog would be saved, and a new one would be created for the rest of the project.
- C. There will be no effect on the Product Backlog.
- D. The Product Backlog evolves to reflect the changes.
Answer: D
NEW QUESTION # 71
Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items.
- A. FALSE
- B. TRUE
Answer: B
NEW QUESTION # 72
When n Scrum teams are working on a product, there are n Sprint Backlogs but only 1 Product Backlog.
- A. False
- B. True
Answer: B
NEW QUESTION # 73
Please select the answer representing a responsibility of a Product Owner.
- A. Defining the Definition of Ready.
- B. Defining the Definition of Done.
- C. Ordering the items in the Product Backlog to best achieve goals and missions.
Answer: C
NEW QUESTION # 74
Who is accountable for managing the progress of work during a Sprint?
(choose the best answer)
- A. The most junior member of the team.
- B. The Developers.
- C. The Scrum Master.
- D. The Product Owner.
Answer: B
Explanation:
Explanation
The Developers are accountable for managing the progress of work during a Sprint, as they are the ones who plan, execute, and deliver the work. The Scrum Guide states that "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."1 The Developers are also responsible for conducting the Daily Scrum, a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours.1 The Developers are self-managing, which means they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1 References:
1: The Scrum Guide2, page 7
2: The Scrum Guide
NEW QUESTION # 75
Who is accountable for creating a valuable and usable Increment each Sprint?
(choose the best answer)
- A. The Scrum Master.
- B. The Scrum Team.
- C. The Developers.
- D. The CEO.
- E. The Product Owner.
Answer: B
Explanation:
Explanation
Scrum
According to the Scrum Guide 2020, the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint1234. This includes the Developers, the Product Owner, and the Scrum Master4. The Developers are committed to creating any aspect of a usable Increment each Sprint12, while the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team12.
The Scrum Master fosters an environment where the Scrum Team can work effectively1.
NEW QUESTION # 76
What are the two responsibilities of testers in a Scrum Team?
(choose the best two answers)
- A. Tracking quality metrics.
- B. Finding bugs.
- C. Scrum has no "tester" role.
- D. Verifying the work of programmers.
- E. The Developers are responsible for quality.
Answer: C,E
Explanation:
Explanation
* Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as "tester", "analyst", "designer", or "architect".
* 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 Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.
* The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.
* The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Quality: https://www.scrum.org/resources/blog/quality-scrum-value
NEW QUESTION # 77
The Sprint length can be 3 weeks.
- A. FALSE
- B. TRUE
Answer: B
NEW QUESTION # 78
Which outcome is expected as a Scrum Team matures?
(choose the best answer)
- A. They will improve their Definition of Done to include more stringent criteria.
- B. Sprint Reviews will no longer be needed.
- C. The Sprint Retrospectives will grow to be longer than 4 hours.
- D. A Scrum Master is no longer needed since they are a mature team now.
- E. There will be no need for a timeboxed Sprint.
Answer: A
Explanation:
Explanation
A mature Scrum Team is expected to continuously improve their quality standards and deliver potentially releasable Increments of value that meet the Definition of Done12. The Definition of Done is a shared understanding of what it means to complete a Product Backlog item, and it may vary from one Scrum Team to another3. As the Scrum Team matures, they may expand their Definition of Done to include more rigorous criteria, such as higher levels of testing, documentation, performance, security, usability, etc . This way, they ensure that their product Increment is always ready for release and meets the expectations of the stakeholders and customers12.
NEW QUESTION # 79
Which two things should the Scrum Team do during the first Sprint?
(choose the best two answers)
- A. Build at least one piece of valuable functionality.
- B. Create at least one valuable, useful Increment.
- C. Define the major product features and a release plan architecture.
- D. Make up a plan for the rest of the project.
- E. Analyze, describe, and document the requirements for the subsequent Sprints.
Answer: A,B
Explanation:
the first Sprint is the same as any other Sprint, and the Scrum Team should deliver a potentially releasable Increment of "Done" product at its conclusion. This means that the team should build at least one piece of valuable functionality that meets the Definition of Done and aligns with the Sprint Goal. The other options are not things that the Scrum Team should do during the first Sprint, as they are either too detailed, too vague, or too long-term for the Scrum framework. The Scrum Team should not make up a plan for the rest of the project, as Scrum is an empirical process that adapts to changing requirements and feedback1. The Scrum Team should not define the major product features and a release plan architecture, as these are the responsibilities of the Product Owner, who should have a vision and a roadmap for the product2. The Scrum Team should not analyze, describe, and document the requirements for the subsequent Sprints, as this would violate the principle of emergent design and just-in-time planning3.
1: The Scrum Guide | Scrum.org 2: What is a Product Owner? | Scrum.org 3: Emergent Design and Just-in-Time Planning | Scrum.org
NEW QUESTION # 80
Changes that endanger the Sprint Goal achievement are allowed.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 81
Multiple teams working on the project means that there can be multiple Definitions of Done.
- A. False
- B. True
Answer: B
NEW QUESTION # 82
How much of the Sprint Backlog must be defined during the Sprint Planning event?
(choose the best answer)
- A. Just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint.
- B. Enough so the Developers can create their forecast of what work they can do.
- C. The entire Sprint Backlog must be identified and estimated by the end of Sprint Planning.
- D. Just enough to understand design and architectural implications.
Answer: B
Explanation:
Explanation
The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. This is because:
Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
The Developers are also accountable for creating a plan for how they will deliver the selected Product Backlog items as a "Done" Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their work.
The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their forecast of what work they can do and have a clear direction for the first few days of the Sprint.
Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast.
References:
[Scrum Guide], page 14, section "Sprint Planning"
[Scrum Guide], page 7, section "Developers"
[Scrum Guide], page 15, section "Sprint Backlog"
[Scrum Guide], page 14, section "Sprint Planning"
NEW QUESTION # 83
The Daily Scrum improves communication, eliminates other meetings and helps to identify impediments for removal.
- A. False
- B. True
Answer: B
NEW QUESTION # 84
......
Authentic Best resources for PSPO-I Online Practice Exam: https://www.vceengine.com/PSPO-I-vce-test-engine.html
Practice To PSPO-I - VCEEngine Remarkable Practice On your Professional Scrum Product Owner I Exam: https://drive.google.com/open?id=1c6s_SrUjb1nTe7LetOwf1b6tUXCxKWSc
