Scrum PSPO-I - Professional Scrum Product Owner (PSPO I) Exam
Which two ways of creating Scrum Teams are consistent with Scrum's values?
(choose the best two answers)
Managers personally re-assign current subordinates to new teams.
The Chief Product Owner determines the new team structures and assignments.
Managers collaborate to assign individuals to specific teams.
Existing teams propose how they would like to go about organizing into the new
structure.
Bring all the people together and let them organize into Scrum Teams.
The Answer Is:
D, EExplanation:
The Scrum values are commitment, focus, openness, respect, and courage1. These values are embodied by the Scrum Team, which is a self-managing unit that organizes its own work and delivers a valuable product2. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers[3][3]. The best way to create Scrum Teams is to respect the self-management and empowerment of the people who will do the work, and let them decide how to organize themselves into Scrum Teams. This can be done by bringing all the people together and letting them form Scrum Teams based on their skills, interests, and alignment with the product vision4. Alternatively, existing teams can propose how they would like to reorganize themselves into Scrum Teams, based on their feedback and experience5. These ways of creating Scrum Teams are consistent with the Scrum values, as they foster commitment, focus, openness, respect, and courage among the team members and stakeholders. The other options are not consistent with the Scrum values, as they involve managers or the Chief Product Owner imposing their decisions on the team members, which undermines their self-management and empowerment, and creates a lack of trust and collaboration.
References:
1:Â The Scrum Guide, November 2020, p. 4
2:Â The Scrum Guide, November 2020, p. 5
[3][3]:Â The Scrum Guide, November 2020, p. 6
4:Â Managing Products with Agility, Scrum.org, accessed on December 16, 2023
5:Â Developing People and Teams, Scrum.org, accessed on December 16, 2023
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
Add security concerns to the Definition of Done.
Delegate the work to the security department.
Have the Scrum Team create Product Backlog items for each concern.
Add a Sprint to specifically resolve all security concerns.
Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
The Answer Is:
A, CExplanation:
 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.â€
True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.
True
False
The Answer Is:
AExplanation:
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
What are the two responsibilities of testers in a Scrum Team?
(choose the best two answers)
Tracking quality metrics.
Scrum has no "tester" role.
Verifying the work of programmers.
The Developers are responsible for quality.
Finding bugs.
The Answer Is:
B, DExplanation:
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
The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has the final say over the Definition of Done?
(choose the best answer)
Yes, the Product Owner decides the Definition of Done. The Developers may be
consulted.
No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
The Answer Is:
BExplanation:
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 Definition of Done is defined by the Scrum Team, not by the Product Owner alone. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
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 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.
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.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
Who should make sure everyone on the Scrum Team does their tasks for the Sprint?
(choose the best answer)
The Project Manager.
The Product Owner.
The Scrum Master.
The Scrum Team.
All of the above.
The Answer Is:
DExplanation:
The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
The Scrum Team is responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Scrum Team does not rely on any external authority, manager, or leader to assign or monitor their work. The Scrum Team collaborates and coordinates their work as one unit, without any hand-offs or silos. The Scrum Team also inspects and adapts their work based on empirical evidence and feedback.
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 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.
The other options are not valid or relevant answers for who should make sure everyone on the Scrum Team does their tasks for the Sprint. They are either nonexistent or irrelevant roles in Scrum. They are:
The Project Manager: There is no “Project Manager†role in Scrum. Scrum is a framework for developing, delivering, and sustaining complex products, not projects. A project is a temporary endeavor with a fixed scope, time, and cost. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project manager is a role in traditional project management, a discipline for planning, executing, and controlling projects. A project manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.
The Product Owner: The Product Owner is not responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner does not assign or monitor tasks to the Developers. The Product Owner collaborates with them to clarify and refine the Product Backlog items and their acceptance criteria.
All of the above: This is not a valid answer because it includes two invalid options: The Project Manager and The Product Owner.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?
(choose the best answer)
As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
As much as is required to meet the Scrum Team's Definition of Done.
All development work and at least some testing.
A proportional amount of time on analysis, design, development, and testing.
The Answer Is:
BExplanation:
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
Which of the following are true about the length of the Sprint?
(choose the best answer)
The length of the Sprint should be proportional to the work that is done in between
Sprints.
All Sprints must be one month or less.
Sprint length is determined during Sprint Planning, and should hold the time it will
take to build the planned features in the upcoming Sprint, but does not include time
for any testing.
Sprint length is determined during Sprint Planning, and should be long enough to
make sure the Scrum Team can deliver what is to be accomplished in the upcoming
Sprint
The Answer Is:
BExplanation:
The Scrum Guide states that “Sprints are the heart of Scrum where ideas are turned into valueâ€. It also states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprintâ€. Furthermore, it states that “Sprints are limited to one calendar month. When a Sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increaseâ€. Therefore, the correct answer is B. The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-organization, and adaptation.
References:
The Scrum Guide, section 3.1. Sprints
Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint
What is the timebox for the Sprint Planning event?
(choose the best answer)
Monthly.
Whenever it is done.
8 hours for a one-month Sprint.
4 hours for a one-month Sprint.
The Answer Is:
CExplanation:
The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
True or False: All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
True
False
The Answer Is:
AExplanation:
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
