Download Scrum.PSPO-I.VCEplus.2023-12-01.30q.tqb

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.Scrum Guide: https://www.scrumguides.org/scrum-guide.htmlTransparency: https://www.scrum.org/resources/blog/transparency-scrum-valueProduct Backlog: https://www.scrum.org/resources/what-is-a-product-backlogMoSCoW: https://www.agilealliance.org/glossary/moscow/

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.Scrum Guide: https://www.scrumguides.org/scrum-guide.htmlDevelopers: https://www.scrum.org/resources/what-is-a-developer-in-scrumQuality: https://www.scrum.org/resources/blog/quality-scrum-value

If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. 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 Product Owner is accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are most important and valuable for the product.If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the quality or value of the Increment.Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.[Scrum Guide], page 14, section ''Sprint Planning''[Scrum Guide], page 7, section ''Developers''[Scrum Guide], page 6, section ''Product Owner''[Scrum Guide], page 11, section ''Product Backlog''