Question 74 - PSM II discussion

According to the Scrum Guide 2020, the Scrum Team commits to achieving the Sprint Goal and creating a valuable product Increment every Sprint1.The Sprint Goal is a short statement that provides direction and focus for the Scrum Team throughout the Sprint2.The product Increment is a concrete and usable outcome that meets the Definition of Done and adds value to the product3. Therefore, the Scrum Team commits to:

Working towards the Sprint Goal.This means that the Scrum Team collaborates and coordinates their work to deliver a product Increment that satisfies the Sprint Goal.The Sprint Goal is chosen by the Scrum Team during Sprint Planning, based on the Product Backlog items that they forecast to complete in the Sprint2.The Sprint Goal provides coherence and alignment for the Scrum Team, and helps them cope with complexity and uncertainty4.

Seeking stakeholder feedback.This means that the Scrum Team engages with the stakeholders and customers who have an interest or influence on the product. The Scrum Team seeks their feedback to inspect and adapt the product Increment and the Product Backlog, and to validate their assumptions and hypotheses. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on what was done in the Sprint and what to do next.

Upholding transparency.This means that the Scrum Team makes all aspects of their work visible to those who are responsible for the outcome. Transparency enables inspection and adaptation, which are essential for empiricism. The Scrum Team upholds transparency by using the Scrum artifacts (Product Backlog, Sprint Backlog, and Increment) as sources of information and progress, and by having frequent and honest communication among themselves and with the stakeholders.

The other options are not correct because:

Getting all the forecast work in the Sprint Plan done.This option is incorrect because it implies that the Scrum Team is committed to a fixed scope of work, rather than a flexible goal. The Scrum Guide 2020 states that ''the Developers do not commit to completing all of the work planned during a Sprint Planning'' but rather ''they plan their work as they perform it throughout the Sprint''. The Scrum Team can modify their Sprint Backlog during the Sprint as needed, as long as they do not endanger the Sprint Goal.

Increasing velocity.This option is incorrect because it implies that the Scrum Team is committed to a metric that is not part of the Scrum framework. Velocity is a measure of how much work a team can deliver in a given time period, usually based on story points or hours. However, velocity is not a reliable indicator of value or quality, and it can vary depending on many factors, such as team size, complexity, dependencies, etc. The Scrum Guide 2020 does not mention velocity as a commitment or an artifact of the Scrum Team.

Having the Product Owner available to the Developers on a daily basis.This option is incorrect because it implies that the Product Owner is not part of the Scrum Team, but rather an external stakeholder. The Scrum Guide 2020 states that ''the Product Owner is one person who is a member of the Scrum Team'' and ''is accountable for maximizing value resulting from work of Developers''. The Product Owner collaborates closely with the Developers throughout the Sprint, not only by being available, but also by providing vision, guidance, feedback, and clarification.