Online PSPO-I Questions Video

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.

The Scrum Master should allow the Developers to self-manage and determine for themselves what to do because:

It respects the autonomy and empowerment of the Developers. The Developers are accountable for organizing and managing their own work, and they are the best people to decide how to conduct their Daily Scrum. The Scrum Master should not impose or dictate how the meeting should be set up or run, as that would undermine the self-organization and collaboration of the Developers.

It supports the continuous improvement and adaptation of the Developers. The Developers are expected to inspect and adapt their process and practices, and to find ways to overcome any challenges or impediments they face. The Scrum Master should not solve the problems for them, but rather facilitate their problem-solving and learning abilities.

It aligns with the role and responsibilities of the Scrum Master. The Scrum Master is responsible for promoting and supporting Scrum, and for helping everyone understand and enact Scrum theory, values, principles, and practices. The Scrum Master is not a manager or a leader of the Developers, but rather a servant-leader who enables them to work effectively.

The Sprint Retrospective is one of the five events defined by Scrum. It is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to adapt the way of working so that it becomes more effective and enjoyable. The other options are not required by Scrum, but may be useful practices depending on the context. Developers do not have to stand up at the Daily Scrum, they can choose any format that works for them. A Sprint Burndown Chart is a common way to visualize the remaining work in a Sprint, but it is not mandated by Scrum. Release Planning is a topic that falls under the broader competency of Managing Products with Agility, but it is not a prescribed event in Scrum.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner™ I Certification

The correct answer isC.

The purpose of every Sprint, including the first Sprint, is to create a valuable, useful Increment. Scrum is based on empiricism, meaning teams learn through doing, inspecting results, and adapting. Therefore, the first Sprint should produce something tangible and valuable rather than focusing only on long-term planning or documentation.

Why the other options are incorrect:

A. Make up a plan for the rest of the project— Scrum does not require full up-front planning for the whole project. Plans emerge and adapt over time.

B. Define the major product features and a release plan architecture— this may happen in some organizations, but it is not the main purpose of the first Sprint.

D. Analyze, describe, and document the requirements for the subsequent Sprints— Scrum is not a phase-based requirements process. The goal is to deliver value each Sprint.