Certified ScrumMaster (CSM)

The Certified ScrumMaster (CSM) is a widely recognized entry-level certification that introduces professionals to the Scrum framework and the role of the Scrum Master. It focuses on facilitating team collaboration, removing impediments, and ensuring the Scrum values are upheld. The symbol SCRUM_CSM is a hallmark for those starting their journey as agile facilitators and team coaches.

---------- Question 1

A Scrum Team is stuck in a heated debate during Sprint Planning about the scope of the upcoming Sprint. Developers cannot agree on how much work can be realistically committed, and the Product Owner insists on including more high-priority items than the Developers believe is feasible. The discussion has become circular, with no clear path forward. As the Scrum Master, which facilitation technique would be most effective in helping the group reach a decision and move forward, demonstrating your ability to serve the team?

1. Take control of the meeting, listen to all arguments, and then unilaterally decide on the Sprint Backlog scope to break the deadlock and ensure the meeting finishes on time.
2. Suggest a technique such as Fist of Five or Dot Voting to quickly gauge collective agreement or prioritize options, followed by a time-boxed discussion to resolve any remaining high-priority disagreements collaboratively, ensuring shared understanding.
3. Adjourn the meeting immediately, instructing the Product Owner and one Developer to meet separately and finalize the Sprint Backlog, then report back to the full team.
4. Focus solely on reminding the team of the 15-minute Daily Scrum timebox, implying they are wasting time by not reaching a decision faster during Sprint Planning.

---------- Question 2

A Scrum Team consistently experiences delays due to a complex, multi-level approval process required for deploying any software updates to production, which falls outside their direct control. This process often takes weeks, negating the benefits of frequent Incremental delivery. From the perspective of organizational impediments, what is the most appropriate action for the Scrum Master to take in this scenario?

1. Advise the team to adapt their Definition of Done to exclude deployment to production, focusing only on internal testing and readiness for deployment.
2. Work with the development team to create more detailed documentation for each deployment package, hoping to streamline the approval process through greater clarity.
3. Escalate the issue to relevant organizational management, facilitating conversations to identify bottlenecks and collaborating on systemic changes to the deployment process.
4. Instruct the Product Owner to only prioritize features that do not require external deployment, thereby avoiding the problematic approval process altogether.

---------- Question 3

A Scrum Team has been consistently skipping their Sprint Retrospective event for the past three Sprints, citing tight deadlines and a perceived lack of time for reflection. The team members believe they are already efficient and do not see the immediate value in discussing past Sprints. What are the most likely significant negative effects of continuously skipping the Sprint Retrospective on the team's long-term performance and their ability to embrace empiricism?

1. The team will become overly focused on past mistakes, leading to demotivation and a reluctance to take on new challenges, ultimately slowing down development.
2. Skipping retrospectives will prevent the team from identifying and addressing underlying process inefficiencies, improving their Definition of Done, or enhancing team dynamics, leading to the accumulation of unresolved issues and a stagnation of improvement.
3. The Product Owner will have fewer opportunities to update the Product Backlog, as critical feedback on new features will not be gathered, resulting in a less valuable product increment.
4. Developers will lose valuable time that could be spent on coding and feature development, thus increasing the risk of not completing the Sprint Goal due to reduced work capacity.

---------- Question 4

During a Sprint Planning session, a Scrum Team is discussing how much work they can realistically complete in the upcoming Sprint. The Product Owner has a very ambitious Sprint Goal and a large number of high-priority Product Backlog Items they hope the Developers can commit to. However, the Developers are concerned about their historical velocity, potential technical challenges, and the need to address some lingering technical debt. How should the Developers best conduct themselves during Sprint Planning to ensure they create a realistic and achievable Sprint Backlog, while leveraging Scrum principles?

1. Accept all Product Backlog Items proposed by the Product Owner to demonstrate commitment, assuming they will find a way to complete them.
2. Reject all Product Backlog Items they perceive as risky or too large, demanding the Product Owner refines them before the Sprint can begin.
3. Collaborate with the Product Owner, pulling enough Product Backlog Items into the Sprint to meet the Sprint Goal, while considering their past performance, current capacity, and the Definition of Done. They should also break down selected items into smaller, actionable tasks.
4. Agree to the Product Owners request but inform the Scrum Master that they will need to skip the next Sprint Retrospective to make up for lost time.
5. Estimate each Product Backlog Item individually without discussing dependencies or overall team capacity, then commit to the total sum of estimated effort.

---------- Question 5

An organization is transitioning to Scrum, and there is a debate about the Product Owner role. Some stakeholders propose forming a committee of department heads to act as the Product Owner to ensure all departmental interests are represented in the Product Backlog. The current Product Owner candidate, an expert in the product domain, fears this will lead to conflicting priorities and slow down decision-making. What is the most significant reason, aligned with Scrum principles, for the Product Owner to be a single individual rather than a group?

1. A single Product Owner can delegate all decision-making regarding the Product Backlog to the developers, thereby empowering the team fully.
2. Centralizing accountability in one person prevents the Developers from having direct access to stakeholders, streamlining communication channels.
3. A single Product Owner ensures clear accountability for maximizing the value of the product resulting from the work of the Scrum Team, providing a singular vision and efficient decision-making for Product Backlog ordering.
4. The Scrum Guide mandates that only one person can hold the Product Owner title, irrespective of organizational needs or product complexity, to maintain a strict hierarchy.

---------- Question 6

A Scrum Team is halfway through its Sprint when a critical external event occurs: a major regulatory change renders the entire current Sprint Goal and a significant portion of the Product Backlog completely obsolete and irrelevant to the products future direction. Continuing the Sprint as planned would be a waste of resources. Under these specific conditions, who has the authority to terminate the Sprint prematurely, and what is the primary consequence of such an action?

1. Any Developer on the Scrum Team can decide to terminate the Sprint, and all completed work is immediately discarded.
2. The Scrum Master can terminate the Sprint after consulting with the stakeholders, and the team immediately starts a new Sprint.
3. Only the Product Owner has the authority to prematurely terminate a Sprint, and all completed Product Backlog Items that are Done are reviewed, while incomplete items are re-estimated and returned to the Product Backlog.
4. The entire Scrum Team must vote unanimously to terminate the Sprint, and all remaining Sprint Backlog items are automatically moved to the next Sprint.

---------- Question 7

A Scrum Team has been consistently struggling with delivering a truly releasable Increment at the end of each Sprint. Often, significant bugs or integration issues are discovered during or immediately after the Sprint Review, necessitating substantial rework in subsequent Sprints. This leads to unpredictability, delays, and a perception that the product is not ready for market. What is the most significant advantage a strong, well-understood, and consistently applied Definition of Done provides to address this particular challenge?

1. It enables the Scrum Team to skip the Sprint Review and directly deploy their Increment to production, saving time.
2. It ensures that the Increment delivered at the end of each Sprint is of consistently high quality and is potentially usable or releasable, reducing rework.
3. It helps the Product Owner prioritize Product Backlog items more effectively by outlining technical implementation details.
4. It provides a clear checklist for the Scrum Master to evaluate individual developer performance and provide targeted coaching.

---------- Question 8

An organization is considering adopting Scrum across several new product development teams. Historically, the company has operated with a traditional hierarchical structure, featuring strong functional silos and project managers responsible for timelines, budgets, and resource allocation. As a Scrum Master introducing the framework, you are frequently asked about the role of a project manager in Scrum and how the organization's structure might need to change. Which of the following statements accurately explains why Scrum does not have a project manager and summarizes a key organizational design change caused by adopting Scrum?

1. Scrum replaces the project manager with the Scrum Master, who is solely responsible for resource allocation, budget control, and enforcing project timelines.
2. Scrum distributes traditional project management responsibilities among the Scrum Team members: the Product Owner manages scope and value, Developers manage work execution, and the Scrum Master manages process and impediments, fostering self-management and cross-functionality.
3. Scrum eliminates the need for any form of management, allowing teams to operate entirely autonomously without guidance or structure, thus removing project managers entirely.
4. Scrum retains the project manager role but renames it to Scrum Project Lead, who then oversees all Scrum Teams and ensures they adhere to a master project plan.

---------- Question 9

A Scrum Team is consistently struggling to make decisions during Sprint Planning, with discussions often becoming circular and without a clear outcome. Different developers hold strong, but conflicting, opinions on how to approach a complex technical challenge. As the Scrum Master, you need to facilitate this group decision-making process effectively. Which of the following techniques would be most appropriate to guide the team towards a consensus or a clear path forward, while ensuring all voices are heard and respected, rather than simply dictating a solution?

1. Implementing a strict majority vote where the option with the most votes is immediately chosen, regardless of dissenting opinions.
2. Using a Fist of Five technique or a modified dot-voting system to gauge team sentiment and identify areas of strong agreement or disagreement, followed by targeted discussion.
3. Assigning the most senior developer on the team to make the final decision to expedite the process and avoid prolonged debate.
4. Suggesting that the team defer the decision until after the Sprint has started, allowing more time for individual research and reflection before reconvening.

---------- Question 10

A Scrum Team has been conducting their Daily Scrum every morning, with each Developer providing a detailed status report of their individual tasks to the Scrum Master. This often extends beyond the 15-minute timebox, and team members rarely engage with each other during the meeting. Considering the Scrum Guide's intent for the Daily Scrum, which statement best explains how this event differs from a traditional status meeting and why constraints like the timebox and Developer-centric focus are vital for its effectiveness?

1. The Daily Scrum is a formal reporting session where Developers update the Scrum Master on task completion, whereas a status meeting is an informal check-in. The 15-minute timebox serves primarily to limit individual Developer speaking time.
2. The Daily Scrum is a planning event for Developers to synchronize activities and inspect progress toward the Sprint Goal, fostering adaptation of their plan for the next 24 hours. It differs from a status meeting by being an internal team communication and commitment session, not a report to management, with constraints supporting Developer self-management.
3. The Daily Scrum is solely for the Scrum Master to identify impediments that need immediate resolution, making it distinct from a status meeting where management gathers information. The constraints are there to prevent Developers from discussing non-work related topics.
4. The Daily Scrum is an opportunity for the Product Owner to provide updated requirements and feedback to the Developers, distinguishing it from a status meeting focused on project timelines. The timebox ensures the Product Owner has sufficient time to convey all necessary information.

---

Are they useful?

Click here to get 360 more questions to pass this certification at the first try! Explanation for each answer is included!

Follow the below LINKEDIN channel to stay updated about 89+ exams!

The Agile Hub