CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSPO-I

Free PSPO-I Exam Braindumps

All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection.
Which two measures ensure that the Product Backlog is transparent? (choose the best two answers)

  1. The Product Backlog is ordered.
  2. The Product Backlog is available to all stakeholders.
  3. Each Product Backlog item has a MoSCoW priority.
  4. The Product Backlog only has work for the next 2 Sprints.
  5. The Product Backlog is managed using a web-based tool.

Answer(s): A,B

Explanation:

Transparency is one of the three pillars of Scrum, along with inspection and adaptation. Transparency means that all aspects of the Scrum process and the product are visible and understandable to everyone who needs to work on or with them. Transparency enables effective inspection and adaptation, which are essential for delivering valuable products and improving the Scrum Team's performance.
All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Scrum artifacts include the Product Backlog, the Sprint Backlog, and the Increment. 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.
Two measures that ensure that the Product Backlog is transparent are:
The Product Backlog is ordered: 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 Product Backlog is available to all stakeholders: The Product Owner makes the Product Backlog visible and accessible to everyone who has a stake in the product, such as customers, users, sponsors, managers, or other teams. The availability of the Product Backlog enables transparency, collaboration, feedback, and alignment among all parties involved in the product development. The other options are not valid or relevant measures to ensure that the Product Backlog is transparent. They are either too restrictive, arbitrary, or unrelated to the Product Backlog's transparency. They are:
Each Product Backlog item has a MoSCoW priority: MoSCoW is a technique for prioritizing requirements based on their importance: Must have, Should have, Could have, or Won't have.
While this technique can be useful for some products or contexts, it is not a mandatory or universal way to order the Product Backlog items. The Product Owner may use other factors or methods to order the Product Backlog items based on their value and relevance for the product. The Product Backlog only has work for the next 2 Sprints: This is a too limiting and unrealistic measure for the Product Backlog. The Product Backlog should contain all the work that is known to be needed in the product, not just for the next 2 Sprints. The Product Backlog is a living artifact that evolves as the product and the market change. The Product Owner should continuously refine and update the Product Backlog to reflect the current and future needs and expectations of the customers and users.
The Product Backlog is managed using a web-based tool: This is an irrelevant measure for the Product Backlog's transparency. The Product Owner can use any tool or format to manage the Product Backlog, as long as it is clear, concise, and valuable. The tool or format does not affect the transparency of the Product Backlog itself.
What matters more is how the Product Owner communicates and collaborates with the Scrum Team and the stakeholders using the Product Backlog.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Transparency: https://www.scrum.org/resources/blog/transparency-scrum-value Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog MoSCoW: https://www.agilealliance.org/glossary/moscow/



What are the two responsibilities of testers in a Scrum Team? (choose the best two answers)

  1. Tracking quality metrics.
  2. Scrum has no "tester" role.
  3. Verifying the work of programmers.
  4. The Developers are responsible for quality.
  5. Finding bugs.

Answer(s): B,D

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.


Reference:

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



True or False: An Increment must be released to customers or users at the end of each Sprint.

  1. True
  2. False

Answer(s): B

Explanation:

An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable.
The Scrum Team decides when and how to release an Increment to customers or users. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, and may decide to release an Increment at any time during or after a Sprint. The Developers are responsible for creating a potentially releasable Increment each Sprint, and may collaborate with the Product Owner and the stakeholders to determine the best way to deliver value. Releasing an Increment to customers or users is not mandatory at the end of each Sprint. The Scrum Team may choose to release an Increment more or less frequently, depending on the product goals, market conditions, customer feedback, or technical feasibility. However, releasing an Increment regularly can provide many benefits, such as:
Validating assumptions and hypotheses about the product value and quality. Obtaining feedback and data from real users and customers.
Increasing customer satisfaction and loyalty.
Reducing risks and uncertainties.
Improving transparency and collaboration.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Increment: https://www.scrum.org/resources/what-is-an-increment Releasing Value: https://www.scrum.org/resources/blog/releasing-value



How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?
(choose the best answer)

  1. As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
  2. As much as is required to meet the Scrum Team's Definition of Done.
  3. All development work and at least some testing.
  4. A proportional amount of time on analysis, design, development, and testing.

Answer(s): B

Explanation:

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.


Reference:

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






Post your Comments and Discuss Scrum PSPO-I exam with other Community members:

Barbara commented on October 07, 2024
good content!
UNITED STATES
upvote