CSM Practice Questions

This is a key service the Scrum Master provides to the Product Owner. Helping the PO develop skills to manage competing stakeholder demands ensures that a clear, unified direction is provided to the team.

This action addresses the problem at a systemic level. By facilitating a discussion, the Scrum Master helps create transparency and establish clear communication protocols, which protects the team's focus and empowers the Product Owner.

The Sprint Backlog is created by the Developers during Sprint Planning. It is a highly visible, real-time picture of the work they plan to accomplish during the Sprint to achieve the Sprint Goal. It is a living artifact that can be updated throughout the Sprint by the Developers as they learn more.

This is the most effective and proactive solution. The root cause is the late discovery of the dependency. By having both teams refine the Product Backlog together, they can collaboratively identify cross-team dependencies well before a Sprint begins. This allows the Product Owner to order the backlog in a way that resolves these dependencies, or for the teams to create a plan to manage them. This approach fosters communication, transparency, and a shared understanding of the work, directly addressing the core problem.

At the end of a Sprint, the Sprint Backlog ceases to exist. Any incomplete Product Backlog Items are returned to the Product Backlog. The Product Owner then re-orders them based on the current priorities and understanding of value. They are not automatically carried over to the next Sprint, as their value and priority may have changed.

The problem described is a classic symptom of a missing or misaligned Definition of Done (DoD). The DoD is a formal description of the state of the Increment when it meets the quality measures required for the product. It creates transparency by providing a shared understanding of what work was completed. The Scrum Master should facilitate a workshop for the entire Scrum Team to create a DoD that everyone agrees upon.

Scrum teams are self-managing. While the Product Owner is the final authority on the Product Backlog, the Developers are empowered to make decisions to keep moving toward the Sprint Goal. The best course of action is to use their professional judgment, document their assumptions, and proceed, ensuring they sync with the PO as soon as possible. This maintains momentum and embodies the principle of self-management.

This statement is false. The Sprint Review is a formal event for stakeholder feedback, but collaboration is not limited to this event. The Product Owner is expected to be in regular contact with stakeholders throughout the Sprint to gather insights and refine the Product Backlog. This ongoing collaboration helps ensure that the Sprint Review does not contain major surprises.

The value of 'Focus' is most directly compromised. By allowing frequent interruptions, the team loses its ability to concentrate on the work of the Sprint and progress towards the Sprint Goal. The Scrum Master should coach the stakeholders on how to interact with the team appropriately, likely directing communication through the Product Owner and respecting the Sprint's boundary.

This statement is true. It directly describes the pillar of Transparency. For inspection and adaptation to be effective, the state of the artifacts and progress towards goals must be transparent to all involved parties, ensuring everyone operates from a common understanding.

The Product Goal is the commitment for the Product Backlog. It describes a future state of the product which can serve as a target for the Scrum Team to plan against. A missing or poorly defined Product Goal leads to a lack of long-term vision, causing Sprint Goals to seem random and tactical rather than strategic steps toward a larger objective.