CSM Practice Exam Questions with Answers Certified ScrumMaster Exam Certification

TheDaily Scrumis the event where impediments to achieving the Sprint Goal are shared. It is a time-boxed event (15 minutes) held every day during the Sprint. During this event, the Developers inspect their progress toward the Sprint Goal and identify any blockers or impediments that need to be addressed.

According to the2020 Scrum Guide:

The Developers use the Daily Scrum to inspect progress andadapt their planto achieve the Sprint Goal.

Impediments are raised and addressed by the Scrum Master if they cannot be resolved by the team.

Why the other options are incorrect:

B. Sprint Planning:Sprint Planning is focused on creating the Sprint Goal and selecting Product Backlog items for the Sprint, not sharing impediments.

C. Sprint Retrospective:The Retrospective focuses on process improvements and team dynamics, not day-to-day impediments during the Sprint.

D. Sprint Review:The Sprint Review is about presenting the Increment and gathering feedback, not resolving impediments.

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.

The Scrum Master is aservant leader, focused on enabling the Scrum Team to work effectively. By taking action to resolve the Developer's impediment (lack of hardware), the Scrum Masterdemonstratesleadershipby facilitating the team’s progress and ensuring they can meet the Sprint Goal.

According to the2020 Scrum Guide, the Scrum Master serves the Scrum Team by:

Removing Impediments: Resolving obstacles that block the team’s progress is a key responsibility of the Scrum Master.

Supporting Team Effectiveness: By addressing issues outside the team’s control, the Scrum Master ensures that the Developers can focus on their work.

Why the other options are incorrect:

A. Disciplinarian:A Scrum Master does not enforce rules or discipline team members. They lead by fostering collaboration and resolving issues, not by control.

B. Project Manager:Scrum Masters do not perform traditional project management tasks like resource allocation or task assignment. Their role is to serve and support the team rather than manage it.

C. Authoritarian:The Scrum Master is not an authoritarian leader. Their approach is grounded in servant leadership, enabling and empowering the team rather than commanding it.

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.

Incremental processrefers to building and delivering software in small, usable pieces (Increments). In Scrum, each Increment is a usable part of the product that adds value and meets the Definition of Done.

According to the2020 Scrum Guide:

The Increment isa concrete step toward the Product Goal.

Increments allow for frequent inspection and adaptation while ensuring transparency of progress.

Why the other options are incorrect:

A. An iterative process:While Scrum is iterative, "iterative" describes repeated cycles of planning and improving, whereas "incremental" refers to delivering usable pieces of the product.

C. A lifecycle process:This is a generic term for any process involving software development and does not specifically describe building in pieces.

D. A release process:A release process focuses on deploying software, not the incremental building of usable Increments.

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.

Product Backlog refinementis the act of breaking down and further defining Product Backlog items into smaller, clearer, and more actionable items. This process ensures that the Product Backlog is well-organized, understood, and ready for the upcoming Sprint Planning. Refinement helps the Developers and Product Owner collaborate to add detail, order, and estimates to Product Backlog items.

According to the2020 Scrum Guide:

Product Backlog refinement is an ongoing activity that occurs throughout the Sprint.

It is not a formal event, and its timing and structure are determined by the Scrum Team.

Refinement improves clarity and helps the team better understand upcoming work.

Why the other options are incorrect:

A. a recurring event in the middle of each Sprint:Product Backlog refinement is not a time-boxed event. It occurs continuously, as needed.

C. an opportunity for the Developers to estimate Product Backlog items:While estimation may occur during refinement, the primary purpose is breaking down and clarifying items, not solely estimation.

D. a pre-planning meeting to shorten the length of Sprint Planning:Product Backlog refinement is not a pre-planning meeting but an ongoing activity to prepare for future Sprints.

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.

In theScrum framework, the three defined accountabilities are:

Product Owner– Responsible for maximizing the value of the product by managing the Product Backlog.

Scrum Master– Ensures that Scrum is understood and enacted effectively, removes impediments, and serves the Scrum Team and organization.

Developers– Responsible for delivering a "Done" Increment that meets the Sprint Goal.

There is no role forLead Developer,Project Manager, orBusiness Analystin Scrum. Scrum promotes self-management, cross-functional teams, and does not include traditional hierarchical roles.

Why the other options are incorrect:

A. Lead Developer:Scrum does not have a Lead Developer role or accountability.

B. Project Manager:Scrum does not include a Project Manager role as tasks and responsibilities are distributed among the Scrum Team.

D. Business Analyst:While the Product Owner may perform some business analysis tasks, there is no separate role for a Business Analyst in Scrum.