[Aug-2025] Scrum Master CSM Exam Practice Dumps [Q17-Q31]

August 25, 2025 latestexam 0 Comments

4/5 - (1 vote)

[Aug-2025] Scrum Master CSM Exam Practice Dumps

2025 CSM Premium Files Test pdf – Free Dumps Collection

NO.17 What is one accountability of a Scrum Master?

Set the budget

Provide estimates

Improve the Scrum Team’s effectiveness

Decide when to release the product

One of the key accountabilities of aScrum Masteris toimprove the Scrum Team’s effectiveness. This aligns with the Scrum Master’s role as a servant leader who helps the team deliver value through better practices, collaboration, and adherence to Scrum principles.
According to the2020 Scrum Guide, the Scrum Master is accountable for:
* Establishing Scrum as defined in the Scrum Guide, helping everyone understand its theory and practices.
* Improving the Scrum Team’s effectivenessby enabling the team to self-manage, improve cross- functionality, and focus on delivering high-value Increments.
* Removing impedimentsthat hinder progress and supporting the team in achieving its Sprint Goals.
Why the other options are incorrect:
* A. Set the budget:The Scrum Master does not manage budgets. Budgeting decisions are outside the scope of the Scrum framework.
* B. Provide estimates:Developers are responsible for providing estimates during Product Backlog refinement and Sprint Planning.
* D. Decide when to release the product:Decisions about releases are made collaboratively by the Product Owner, often based on business needs and stakeholder input.

NO.18 A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems is known as

Kanban.

Scrum.

Agile.

Waterfall.

Scrumis a lightweight framework designed to help teams and organizations addresscomplex problemsand deliver value in an adaptive manner. It is based on the principles of empiricism (transparency, inspection, and adaptation) and is widely used for developing, delivering, and sustaining products in a flexible and iterative way.
According to the2020 Scrum Guide, Scrum is:
* A lightweight framework that helps people, teams, and organizationsgenerate valuethroughadaptive solutionsfor complex problems.
* Defined by roles, events, artifacts, and rules that are intentionally simple yet highly effective.
Why the other options are incorrect:
* A. Kanban:Kanban is a method for visualizing work and improving flow, but it is not a framework specifically designed for solving complex problems like Scrum.
* C. Agile:Agile is a broader philosophy or mindset that includes various frameworks (such as Scrum, Kanban, etc.), but Scrum itself is a specific framework.
* D. Waterfall:Waterfall is a traditional, sequential approach to project management that lacks the flexibility and adaptiveness of Scrum.

NO.19 During the Sprint, what Scrum Value must the team demonstrate to achieve the goal?

Completion

Commitment

Agreement

Alignment

The Scrum Team must demonstrateCommitmentto achieve the Sprint Goal. Commitment is one of the five Scrum Values, and it reflects the team’s dedication to the Sprint Goal, the work planned in the Sprint Backlog, and to collaborating effectively. Without commitment, the team cannot focus on delivering the Increment or achieving the Sprint Goal.
According to the2020 Scrum Guide, the Scrum Values are:
* Commitment: Dedication to the team’s goals and delivering value.
* Focus: Concentrating on the Sprint Goal and avoiding distractions.
* Openness: Being transparent about challenges and progress.
* Respect: Valuing each team member and their contributions.
* Courage: Facing challenges and making tough decisions.
Why the other options are incorrect:
* A. Completion:This is not a Scrum Value. Commitment drives completion, but “completion” itself is not a value.
* C. Agreement:While agreement is important, Scrum does not define it as a core value.
* D. Alignment:While alignment is critical to achieving goals, it is not one of the five Scrum Values.

NO.20 Daily Scrum is used to

Assign tasks.

Demo the changes to Stakeholders.

Inspect and adapt work.

Estimate the pending work.

TheDaily Scrumis a time-boxed event that allows theDevelopersto inspect progress toward the Sprint Goal and adapt their plan as necessary. This daily inspection and adaptation ensure the team stays aligned and on track to meet their objectives.
According to the2020 Scrum Guide:
* The Developers inspect how progress is trending toward completing the work in the Sprint Backlog.
* They adapt their work plan based on challenges, progress, or new information.
Why the other options are incorrect:
* B. Assign tasks:Tasks are not assigned in Scrum. Developers are self-organizing and decide collaboratively how to accomplish their work.
* C. Demo the changes to Stakeholders:Demos occur during the Sprint Review, not the Daily Scrum.
* D. Estimate the pending work:While work may be discussed, the Daily Scrum is not used for estimation purposes.

NO.21 When is a Sprint Retrospective meeting held?

After the Sprint Review and prior to the next Sprint Planning

At the beginning of the Sprint

In the middle of the Sprint

At the end of all the Sprints

TheSprint Retrospectiveis heldafter the Sprint Review and before the next Sprint Planning. It is the final event in the Sprint, and its purpose is to reflect on the past Sprint and identify areas for improvement. The Scrum Team inspects how they worked during the Sprint in terms of processes, interactions, tools, and the Definition of Done, and then adapts for future Sprints.
According to the2020 Scrum Guide:
* The Sprint Retrospective is time-boxed and enables the team to inspect and adapt their working practices.
* It helps improve the Scrum Team’s effectiveness in subsequent Sprints.
Why the other options are incorrect:
* B. At the beginning of the Sprint:The Sprint Retrospective is not held at the start of the Sprint. Sprint Planning occurs at the beginning of the Sprint.
* C. In the middle of the Sprint:Mid-Sprint is not a designated time for this meeting; the team is focused on achieving the Sprint Goal.
* D. At the end of all the Sprints:The Retrospective is held at the end ofeach Sprint, not at the conclusion of all Sprints.

NO.22 Which one is true for Sprint Planning?

The work to be performed in the Sprint is planned

Demo of the previous increment is done

Customers will share the feedback

The Product Backlog is refined

DuringSprint Planning, the Scrum Team plans the work to be performed in the upcoming Sprint. The event is time-boxed and is attended by the entire Scrum Team. The main outcomes of Sprint Planning are:
* A Sprint Goalthat defines the purpose of the Sprint.
* Selected Product Backlog itemsthat are forecasted to be delivered during the Sprint.
* A plan for how the work will be completed, which is created by the Developers.
Why the other options are incorrect:
* B. Demo of the previous increment is done:Demonstrations and feedback occur during the Sprint Review, not Sprint Planning.
* C. Customers will share the feedback:Feedback from customers is gathered during the Sprint Review, not Sprint Planning.
* D. The Product Backlog is refined:Product Backlog refinement is an ongoing activity, not a specific focus of Sprint Planning.

NO.23 If Scrum Teams become too large, they should

Split into sub-teams based on function

Reorganize into multiple cohesive Scrum Teams and share the same Product Goal and Product Backlog

Divide into separate teams each with their own Product Owner

Do nothing and focus on delivering a usable product Increment

If a Scrum Team becomes too large, the team shouldreorganize into multiple cohesive Scrum Teamsthat share the sameProduct GoalandProduct Backlog. This approach ensures that all teams remain focused on delivering value while maintaining transparency and alignment.
According to the2020 Scrum Guide:
* Theideal sizefor a Scrum Team is small enough to remain nimble (typically 10 or fewerpeople).
* When a Scrum Team becomes too large, it should form multiple smaller teams, all working from the same Product Backlog and pursuing the same Product Goal.
Why the other options are incorrect:
* A. Split into sub-teams based on function:Scrum encourages cross-functional teams, so dividing based on function contradicts Scrum principles.
* C. Divide into separate teams each with their own Product Owner:A single Product Owner should manage the Product Backlog to ensure alignment and avoid conflicting priorities.
* D. Do nothing and focus on delivering a usable product Increment:Not addressing the issue of an oversized team can lead to inefficiencies and reduced team effectiveness.

NO.24 Which Agile principle is being practiced if a team chooses to focus on the highest priority product backlog items?

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Simplicity – The art of maximizing the amount of work not done is essential.

Business people and developers must work together daily throughout the project.

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

The Agile principle being practiced when a team focuses on the highest-priority Product Backlog items is
“Simplicity – The art of maximizing the amount of work not done is essential.”This principle emphasizes delivering only the most valuable work and avoiding unnecessary effort. By working on the most critical items, the team ensures that resources are used efficiently to maximize value.
Why the other options are incorrect:
* A. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly:This principle relates to Sprint Retrospectives and improving team processes, not prioritizing backlog items.
* C. Business people and developers must work together daily throughout the project:This principle relates to collaboration and communication, not prioritization.
* D. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation:This principle emphasizes communication methods, not prioritization.

NO.25 How should Scrum teams plan work to be performed within Sprints?

One release at a time, adjusting the number of Sprints to the prior releases’ average velocity

One Sprint at a time, adapting each Sprint Backlog according to what was learned from the last Sprint

One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception

One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders

Scrum teams plan workone Sprint at a time, using theSprint Planning eventto adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum’sempirical process control, which relies on inspection and adaptation to plan effectively.
According to the2020 Scrum Guide:
* Sprint Planning creates aSprint Backlog, which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.
* Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.
Why the other options are incorrect:
* A. One release at a time, adjusting the number of Sprints to the prior releases’ average velocity:
Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.
* C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception:Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.
* D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders:Product Backlog Refinement is an ongoing activity, not a Sprint planning process.
Stakeholders typically participate in Sprint Reviews, not in backlog refinement.

NO.26 Which Scrum artifacts provide transparency and opportunities for inspection and adaptation?

Burndown Charts, release plan and Product Backlog

Sprint Backlog, Product Backlog and Increment

Definition of Done and Product Backlog

Definition of Done, Sprint Backlog and Product Backlog

Thethree Scrum artifacts-Product Backlog,Sprint Backlog, andIncrement-providetransparencyinto the work and enable opportunities forinspection and adaptation. These artifacts are essential to ensuring the Scrum Team and stakeholders can inspect progress and adapt plans to maximize value.
According to the2020 Scrum Guide:
* Product Backlog: Represents all the work needed to achieve the Product Goal and allows inspection and prioritization of upcoming work.
* Sprint Backlog: A real-time plan for the Sprint that provides transparency into what the team is working on and allows inspection and adaptation during the Sprint.
* Increment: The outcome of the Sprint that is usable and meets the Definition of Done, enabling stakeholders to inspect progress and provide feedback.
Why the other options are incorrect:
* A. Burndown Charts, release plan and Product Backlog:Burndown charts and release plans are complementary tools, but they are not official Scrum artifacts.
* C. Definition of Done and Product Backlog:The Definition of Done is not an artifact but a shared understanding of when work is complete.
* D. Definition of Done, Sprint Backlog and Product Backlog:While the Sprint Backlog and Product Backlog are artifacts, the Definition of Done is not.

NO.27 A member of the Scrum Team does not want to participate in the Sprint Planning event and considers it a waste of time. What should the Scrum Master do first?

Ask for management’s assistance

Mandate attendance

Discuss the importance of team work

Meet individually to address concerns

When a team member refuses to participate in Sprint Planning, theScrum Master should first meet individually to address their concerns. Understanding the root cause of their reluctance can help the Scrum Master guide them toward recognizing the value of the event. This approach demonstrates respect and a willingness to resolve the issue constructively.
According to the2020 Scrum Guide, the Scrum Master is responsible for:
* Coaching team memberson the importance of Scrum events, such as Sprint Planning.
* Fostering collaborationand ensuring all team members understand their role and responsibilities in achieving the Sprint Goal.
Why the other options are incorrect:
* A. Ask for management’s assistance:Involving management should be a last resort. The Scrum Master should first attempt to resolve the issue directly with the team member.
* B. Mandate attendance:Forcing participation without addressing the underlying concerns could lead to disengagement and resentment.
* C. Discuss the importance of team work:While teamwork is important, addressing the individual’s specific concerns first is a more targeted and effective approach.

NO.28 A developer identified a major technical issue during a Daily Scrum. What should the team do?

Meet and discuss outside of Daily Scrum

Interrupt the Daily Scrum and solve the problem immediately

Escalate it to the Product Owner

Discuss it during the Sprint Review

TheDaily Scrumis a short, time-boxed event (15 minutes) where Developers inspect progress toward the Sprint Goal and adapt their plan for the day. It is not intended to solve problems or deep-dive into discussions.
If a major technical issue is identified during the Daily Scrum, the team should note it and arrange to discuss and solve itoutside of the Daily Scrum.
According to the2020 Scrum Guide:
* The Daily Scrum is focused on progress toward the Sprint Goal, and issues that require detailed discussion or resolution should be handled separately.
* The Scrum Master may help facilitate these follow-up discussions if needed.
Why the other options are incorrect:
* B. Interrupt the Daily Scrum and solve the problem immediately:The Daily Scrum is not a problem- solving session. Interrupting it for detailed discussions disrupts its purpose and timebox.
* C. Escalate it to the Product Owner:Technical issues are typically handled by the Developers, not the Product Owner, who is responsible for managing the Product Backlog and ensuring value delivery.
* D. Discuss it during the Sprint Review:Waiting until the Sprint Review to discuss atechnical issue would delay resolution and risk jeopardizing the Sprint Goal.

NO.29 Members of the Scrum Team do not consider the Sprint Retrospective necessary. What should a Scrum Master do?

Coach the Scrum Team to help them understand the purpose of the Sprint Retrospective

Let the Developers decide

Escalate to the Product Owner

Exclude those members of the Scrum Team from participating

TheScrum Mastershouldcoach the Scrum Teamto understand the importance of theSprint Retrospective.
This event is essential for inspecting and adapting processes, tools, and team dynamics, enabling continuous improvement in future Sprints.
According to the2020 Scrum Guide:
* TheSprint Retrospectiveis a key event where the Scrum Team reflects on their performance and identifies actionable improvements.
* It promotes collaboration, accountability, and self-management, all of which are crucial in Scrum.
Why the other options are incorrect:
* B. Let the Developers decide:The Sprint Retrospective is a mandatory event for the Scrum Team, and the Developers cannot decide to skip it.
* C. Escalate to the Product Owner:The Product Owner is not responsible for team dynamics or facilitating Scrum events. This is the Scrum Master’s responsibility.
* D. Exclude those members of the Scrum Team from participating:Excluding team members would undermine team collaboration and the purpose of the event. Instead, the Scrum Master should address the underlying concerns and help the team recognize its value.

NO.30 When the goal, scope and product domain are not understood by the Scrum Team, the Scrum Master should

Direct the Developers to stop working until the Product Owner improves the acceptance criteria.

Cancel the Sprint and schedule a new Planning meeting.

Do nothing because this is the responsibility of the Product Owner.

Facilitate a discussion between the Stakeholders, Product Owner and Developers.

When the Scrum Team does not understand the goal, scope, or product domain, theScrum Master should facilitate a discussion between the Stakeholders, Product Owner, and Developers. This ensures clarity and shared understanding, enabling the team to move forward effectively.
According to the2020 Scrum Guide, the Scrum Master serves the team by:
* Facilitating stakeholder collaborationas needed.
* Ensuring that the Product Backlog is understoodby the Scrum Team.
* Removing any barriers that hinder the team’s ability to achieve the Sprint Goal.
Why the other options are incorrect:
* A. Direct the Developers to stop working until the Product Owner improves the acceptance criteria:Stopping work is not productive, and collaboration with the Product Owner and stakeholders is the proper approach to resolving misunderstandings.
* B. Cancel the Sprint and schedule a new Planning meeting:Cancelling the Sprint should be an absolute last resort and is typically done only when the Sprint Goal becomes unachievable.
* C. Do nothing because this is the responsibility of the Product Owner:While the Product Owner owns the Product Backlog, the Scrum Master is responsible for facilitating collaboration and resolving impediments.

NO.31 Whose responsibility is it to lead and coach the organization in its Scrum adoption?

Customer

Product Owner

Developers

Scrum Master

TheScrum Masteris responsible for leading and coaching the organization in its Scrum adoption. They play a critical role in helping the organization understand and implement Scrum practices, fostering an environment of empiricism and continuous improvement.
According to the2020 Scrum Guide, the Scrum Master serves the organization by:
* Leading, training, and coaching the organization in Scrum adoption.
* Helping employees and stakeholders understand and enact an empirical approach to work.
* Removing barriers between stakeholders and Scrum Teams.
Why the other options are incorrect:
* A. Customer:Customers provide requirements and feedback but do not lead or coach the organization in Scrum adoption.
* B. Product Owner:The Product Owner manages the Product Backlog and focuses on delivering value but is not responsible for organizational Scrum adoption.
* C. Developers:Developers are responsible for delivering the Increment and are not accountable for coaching the organization.

Loading …

Get ready to pass the CSM Exam right now using our Scrum Master Exam Package: https://www.latestcram.com/CSM-exam-cram-questions.html

Free Cram & Latest Exams Dumps

[Aug-2025] Scrum Master CSM Exam Practice Dumps [Q17-Q31]

leave a comment Cancel reply

Recent Posts

Archives

Categories