Prepare Top Scrum PSPO-I Exam Study Guide Practice Questions Edition
Go to PSPO-I Questions - Try PSPO-I dumps pdf
Scrum PSPO-I certification is an entry-level certification for product owners who are just starting their journey in Scrum. Professional Scrum Product Owner I certification provides a solid foundation in Scrum and product ownership and prepares candidates for more advanced certifications in the future. It is also a great way for product owners to validate their knowledge and expertise in Scrum to their peers and employers.
Scrum framework is an Agile methodology that emphasizes transparency, inspection, and adaptation. Scrum is a lightweight framework that can be used for managing complex product development projects. The Scrum framework is used in various industries, including software development, finance, healthcare, and more. The Scrum framework consists of three roles: the Scrum Master, the Development Team, and the Product Owner.
NEW QUESTION # 32
Select typical responsibilities of a Scrum Master.
- A. Support the Development Team in tracking the release progress.
- B. Do the documentation for the Development Team.
- C. Coaching the Development Team in self-organization and cross-functionality.
- D. Facilitating Scrum events as requested or needed.
- E. Removing impediments to the Development Team's progress.
Answer: C,D,E
NEW QUESTION # 33
The Scrum Master in a Scrum Team is responsible for instilling quality by adhering to a Definition of Done.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 34
The Sprint Planning meeting is a time boxed Scrum event.
- A. True
- B. False
Answer: A
NEW QUESTION # 35
What are the two responsibilities of testers in a Scrum Team?
(choose the best two answers)
- A. Verifying the work of programmers.
- B. The Developers are responsible for quality.
- C. Tracking quality metrics.
- D. Scrum has no "tester" role.
- E. Finding bugs.
Answer: B,D
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 # 36
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 37
It is not allowed that the Product Owner is a Developer (part of the "Developers") at the same time.
- A. False
- B. True
Answer: A
NEW QUESTION # 38
What are reasons for working in Sprints at a sustainable pace?
- A. It improves the Scrum Team's consistency.
- B. It improves the Scrum Team's creativity.
- C. It improves the Scrum Team's focus.
Answer: A,C
NEW QUESTION # 39
The Product Backlog can be changed directly by stakeholders of the project.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 40
What is a Product Owner typically responsible for during a Sprint?
(choose the best two answers)
- A. Working with the Scrum Team on Product Backlog refinement.
- B. Attending every Daily Scrum to answer questions about the Sprint Backlog items.
- C. Nothing.
- D. Creating financial reporting upon the spent hours reported by the Developers.
- E. Collaborating with stakeholders, users, and customers.
- F. Updating the work plan for the Developers on a daily basis.
Answer: A,E
Explanation:
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.
* 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.
* During a Sprint, a Product Owner is typically responsible for:
* Collaborating with stakeholders, users, and customers: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them.
* Working with the Scrum Team on Product Backlog refinement: The Product Owner works closely with the Developers to clarify, refine, and review the Product Backlog items and their acceptance criteria. The Product Owner provides clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item. The Product Owner also empowers and trusts the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner also involves key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
* The other options are not valid or relevant responsibilities of a Product Owner during a Sprint. They are either too administrative, micromanaging, or unrelated to the product value delivery. They are:
* Creating financial reporting upon the spent hours reported by the Developers: This is not a responsibility of a Product Owner during a Sprint. This is an administrative task that does not contribute to the value or quality of the product or service delivered. It may also create unnecessary overhead or bureaucracy for the Developers. The Product Owner should focus on maximizing value rather than tracking hours.
* Updating the work plan for the Developers on a daily basis: This is not a responsibility of a Product Owner during a Sprint. This is a micromanaging task that does not respect the self-organization or cross-functionality of the Developers. The Developers are responsible for planning and executing their own work during a Sprint, based on their empirical experience and collaboration. The Developers also update their progress daily during the Daily Scrum event.
* Nothing: This is not a valid answer for a Product Owner's responsibility during a Sprint. A Product Owner has many important responsibilities during a Sprint, as mentioned above. A
* Product Owner should be actively involved in collaborating with stakeholders, users, customers, and Developers throughout a Sprint to maximize value delivery.
* Attending every Daily Scrum to answer questions about the Sprint Backlog items: This is not a mandatory responsibility of a Product Owner during a Sprint. 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.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
* Stakeholders: https://www.agilealliance.org/glossary/stakeholders
* Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
NEW QUESTION # 41
The Product Owner can also be a member of a team of developers.
- A. True
- B. False
Answer: A
NEW QUESTION # 42
When n Scrum teams are working on a product, there are n Sprint Backlogs but only 1 Product Backlog.
- A. True
- B. False
Answer: A
NEW QUESTION # 43
A Sprint Retrospective should be held:
(choose the best answer)
- A. At the end of the last Sprint in a project or a release.
- B. At the end of each Sprint.
- C. Only when the Scrum Team determines it needs one.
- D. At the beginning of each Sprint.
Answer: B
Explanation:
Explanation
The Sprint Retrospective is a time-boxed event for the Scrum Team to inspect how the last Sprint went and plan for improvements in the next Sprint. The Scrum Guide states that "The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter."1 This means that the Sprint Retrospective should be held at the end of each Sprint, regardless of the project or release status. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements, including to product quality and working relationships.1 References:
1: The Scrum Guide2, page 16
2: The Scrum Guide
NEW QUESTION # 44
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:
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 # 45
When is the Sprint Goal crafted by the Scrum Team?
- A. In the Sprint Review.
- B. During the Sprint Planning.
- C. Between two Sprints.
- D. During the Sprint.
Answer: B
NEW QUESTION # 46
When does a Sprint conclude?
(choose the best answer)
- A. When the Sprint Retrospective is complete.
- B. When the Product Owner decides enough has been delivered to meet the Sprint Goal.
- C. When all Product Backlog items meet their Definition of Done.
- D. When all the tasks are completed by the Developers.
Answer: B
Explanation:
A Sprint is a time-boxed period when a Scrum Team works to complete a set amount of work that delivers value to the customer1. A Sprint concludes when the time-box expires, regardless of whether all the tasks, Product Backlog items, or Definition of Done are completed or not23. The Product Owner has the authority to cancel a Sprint if they determine that the Sprint Goal is obsolete or the work done is no longer valuable1.
Therefore, the Product Owner decides when enough has been delivered to meet the Sprint Goal, and the Sprint ends accordingly.
NEW QUESTION # 47
True or False: A Scrum Master fulfills the same role as a traditional Project Manager.
- A. False
- B. True
Answer: A
Explanation:
A Scrum Master does not fulfill the same role as a traditional Project Manager. A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project1. A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team's progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3]. A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.
References:
1: What is Project Management?, Project Management Institute, accessed on December 16, 2023
2: The Scrum Guide, November 2020, p. 7
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
4: Developing People and Teams, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 48
......
Free Professional Scrum Product Owner PSPO-I Exam Question: https://www.vceengine.com/PSPO-I-vce-test-engine.html
Dumps Practice Exam Questions Study Guide for the PSPO-I Exam: https://drive.google.com/open?id=1v5gTq-890CnyZHnjLT9EMwxOMETOyndR
