Scrum Alliance · Free Practice Questions · Last reviewed May 2026
36real exam-style questions organised by domain, each with the correct answer highlighted and a plain-English explanation of why it's right — and why the others are wrong.
A Product Owner is struggling to manage a massive Product Backlog that has grown to over 500 items. What is the most effective way for the Scrum Master to assist the Product Owner in optimizing the Product Backlog?
Advise the Product Owner to archive all items older than six months.
Take over the responsibility of writing and splitting user stories.
Coach the Product Owner on techniques for refinement, ordering, and transparency.
Coaching the Product Owner on backlog management techniques empowers them to handle complexity effectively. This includes teaching how to decompose large items into smaller ones and how to effectively sequence the backlog. By providing these skills, the Scrum Master enables the Product Owner to maintain a lean, actionable, and transparent Product Backlog.
Instruct the Developers to prioritize the backlog items themselves.
The Product Owner frequently changes the Sprint Backlog during the Sprint, causing the Developers to miss their Sprint Goal. How should the Scrum Master address this with the Product Owner?
Explain that the Sprint Backlog is locked and cannot be changed under any circumstances.
Coach the Product Owner on the impact of changing scope on team focus and Sprint Goals.
Effective coaching involves helping the Product Owner understand the negative impact of interruptions on the team's ability to achieve the Sprint Goal. By discussing the relationship between stability and predictability, the Scrum Master helps the Product Owner make better decisions about when to introduce new work versus waiting for the next Sprint.
Request that the Developers work longer hours to accommodate the new requests.
Update the Definition of Done to include more flexible testing cycles.
A Product Owner is struggling to communicate a clear product vision to stakeholders. What should the Scrum Master do?
Write the product vision statement on behalf of the Product Owner.
Facilitate a session where the Product Owner articulates the vision to the team and stakeholders.
Facilitating a collaborative session allows the Product Owner to practice articulating the vision in a safe environment. This provides an opportunity for direct feedback from the team and stakeholders, ensuring the vision is understood and shared. It reinforces the Product Owner's role as the primary communicator of product strategy.
Tell the Product Owner to create a vision board and present it next month.
Ask the stakeholders to define the vision since the Product Owner is unable to.
Which TWO of the following actions best demonstrate a Scrum Master serving the Product Owner in facilitating stakeholder collaboration?
Representing the Product Owner in all stakeholder meetings.
Coaching the Product Owner on how to say 'no' to stakeholders.
Learning to manage stakeholder expectations by saying 'no' or 'not yet' is vital for protecting the product's focus. A Scrum Master coaches the Product Owner on how to communicate these decisions professionally and transparently, ensuring that stakeholders understand the reasoning based on the current product goals and the strategic priorities.
Ensuring stakeholders have access to the Product Backlog and progress updates.
Transparency is a pillar of Scrum. By ensuring stakeholders have appropriate access, the Scrum Master helps the Product Owner maintain an open flow of information. This reduces the administrative burden on the Product Owner and fosters trust, allowing the Product Owner to focus more on the strategic aspects of product management.
Filtering all feedback from stakeholders before presenting it to the Product Owner.
Writing the user stories for the stakeholders to review.
The Product Owner is having difficulty getting the Developers to understand the 'why' behind product features. What should the Scrum Master do?
Require the Product Owner to provide a 50-page document for every feature.
Coach the Product Owner on techniques to communicate the vision and value to the team.
Coaching the Product Owner on storytelling and effective communication ensures they can convey the product vision and the 'why' behind each feature. This helps the Developers connect their work to the bigger picture, resulting in higher engagement, better problem-solving, and a product that truly meets the needs of the users.
Have the Developers conduct independent research to find the 'why' themselves.
Ask the organization's executives to explain the product strategy to the team.
Which THREE of the following are ways a Scrum Master helps the Product Owner with Product Backlog management?
Teaching the Product Owner how to order the backlog for maximum value.
The Scrum Master coaches the Product Owner on various prioritization frameworks and techniques. This ensures the Product Owner understands how to make trade-offs that maximize value, which is essential for the product's success and the efficiency of the Scrum Team as they work through the backlog items.
Facilitating Product Backlog refinement events to ensure clarity.
The Scrum Master ensures that refinement happens regularly and effectively. By facilitating these sessions, the Scrum Master helps ensure that items are well-understood by the Developers, reducing ambiguity and preventing delays during the Sprint. This is a critical service to the Product Owner for maintaining a high-quality backlog.
Writing the technical implementation details for the Product Owner.
Ensuring the Product Backlog is transparent to all stakeholders.
Transparency is a key pillar of Scrum. The Scrum Master ensures the Product Owner maintains a backlog that is visible and understood by stakeholders. This helps manage expectations and allows for better collaboration between the Product Owner and those who have a vested interest in the product's outcomes and direction.
Assigning specific story points to every backlog item.
Want more Service to the Product Owner practice?
Practice this domainA newly formed Scrum Team is struggling to reach a 'Definition of Done'. Which TWO actions should the Scrum Master prioritize to support the team?
Write the Definition of Done for the team.
Facilitate a session to define criteria that ensure the increment is releasable.
Facilitation is a core competency that helps the team articulate their standards collectively. By focusing on the 'releasable' aspect, the Scrum Master ensures the team considers the entire value chain, including testing, documentation, and compliance, which are essential for creating a high-quality, potentially shippable increment every single Sprint.
Suggest using the organization's quality standards as a baseline.
Using existing organizational standards provides a foundation, ensuring that the Scrum Team aligns with company-wide quality and compliance requirements. This pragmatic approach saves time while allowing the team to expand upon these requirements with more specific, project-relevant criteria that address their unique technical and operational context.
Force the team to meet daily until they agree on criteria.
Wait for the Product Owner to define the criteria.
Refer to the exhibit. As a Scrum Master, how do you address this misinterpretation of the Sprint Review?
Update the policy to include Refinement.
Coach the team and stakeholders on the purpose of the Sprint Review.
Coaching is a fundamental Scrum Master competency. By clarifying the intent of the event, the Scrum Master enables the team to leverage the Sprint Review for its true purpose: inspecting the increment and adapting the Product Backlog based on feedback, thereby increasing the value delivered in subsequent Sprints.
Allow the session to continue as it is.
Host a separate session for Backlog Refinement.
A team has a very high 'WIP' limit and consistently fails to finish items. What is the most appropriate Scrum Master intervention?
Mandate a lower WIP limit for the next Sprint.
Facilitate a data-driven discussion in the Retrospective.
Using data to facilitate the Retrospective encourages an objective examination of performance issues. This transparency allows the team to see the direct correlation between high WIP and their inability to reach 'Done', empowering them to choose a more sustainable WIP limit that improves their delivery flow and team health.
Ask the Product Owner to provide fewer items.
Increase the Sprint length to finish more work.
Which THREE traits demonstrate that a Scrum Master is effectively acting as a servant-leader?
Assigning specific tasks to team members.
Removing impediments that block the team.
Removing impediments is a core responsibility that directly supports the team's flow. By handling blockers, the Scrum Master shields the team from external noise, allowing them to focus on the Sprint Goal. This service-oriented behavior builds deep trust and respect within the team and demonstrates commitment to their success.
Facilitating collaborative decision-making processes.
Facilitation promotes shared ownership and consensus. By ensuring everyone's voice is heard, the Scrum Master creates a culture of inclusion and respect. This approach is essential for high-performing teams, as it leverages the collective intelligence of the group to solve complex problems and make more informed, durable decisions.
Focusing on coaching the team toward self-management.
Coaching towards self-management is the ultimate goal of a servant-leader. By empowering the team to make their own choices, the Scrum Master builds capability and independence. This ensures that the team can continue to improve and deliver value even when the Scrum Master is not directly involved in tasks.
Judging the team's performance based on velocity.
A Scrum Master notices that the team is silent during the Daily Scrum, and the Developers only provide status updates to the Scrum Master. How should they respond?
Start asking each member specific questions.
Remind the team that the Daily Scrum is for them.
Direct coaching on the purpose of the event encourages the team to pivot their focus toward each other. By reinforcing that the event is for the Developers, the Scrum Master nudges the team to discuss their plan for the next 24 hours, fostering collaboration and accountability among peers.
Cancel the Daily Scrum until they can do it properly.
Report the lack of engagement to management.
A stakeholder asks the Scrum Master to add a high-priority feature to the current Sprint. What is the correct response?
Accept the feature if the team has capacity.
Direct the stakeholder to the Product Owner.
The Product Owner is responsible for the Product Backlog and its prioritization. By directing the stakeholder to the Product Owner, the Scrum Master respects the roles and responsibilities defined in Scrum. This ensures that backlog changes are evaluated against the overall product vision rather than being impulsively added to a Sprint.
Add the feature but remove an equal amount of work.
Ask the team to vote on the new request.
Want more Scrum Master Core Competencies practice?
Practice this domainA Development Team member consistently interrupts fellow developers during Daily Scrums and pushes technical architectural changes without team consensus. What is the most appropriate Scrum Master response?
Escalate the developer's behavior to the functional engineering manager for a formal performance review.
Facilitate a private coaching session with the developer to discuss collaborative norms and active listening.
Private coaching targets behavioral root causes respectfully while upholding servant leadership principles. It empowers the developer to adjust their interpersonal approach without causing public embarrassment, aligning directly with the Scrum Master's core duty of team enablement.
Facilitate the Daily Scrum personally to strictly enforce time limits and prevent anyone from speaking out of turn.
Remove the developer from the Scrum Team immediately to restore immediate harmony during the next sprint.
Who holds the final authority for determining the order of items within the Product Backlog in a Scrum environment?
The entire Scrum Team through unanimous consensus during Sprint Planning sessions.
The Product Owner, incorporating feedback from stakeholders, customers, and the Scrum Team.
The Product Owner holds sole accountability for Product Backlog ordering, satisfying Scrum's single-authority constraint. Stakeholder, customer and Scrum Team input informs their decisions, but final prioritisation authority rests with the Product Owner alone. This preserves clear ownership and prevents competing priorities from fragmenting backlog order.
The Scrum Master after facilitating alignment workshops with organizational executives.
The Development Team based purely on technical dependencies and architectural complexity.
A Product Owner is unavailable for three consecutive Sprints due to a medical emergency. Who is responsible for managing the Product Backlog during this absence?
The Scrum Master takes over all Product Owner accountabilities until they return.
The Developers collectively decide on the priority of the Product Backlog items.
The organization must ensure the Product Owner accountabilities are fulfilled through temporary delegation or reassignment.
Accountability for the Product Backlog cannot simply vanish during an absence. The organization must take responsibility to ensure someone is empowered to make decisions regarding value and priority. This maintains the flow of the Scrum process and prevents the team from becoming stalled or directionless during the gap.
The Sprint remains frozen until the Product Owner returns to manage the backlog.
Which TWO of the following describe a responsibility of the Scrum Master regarding the Developers?
Assigning specific tasks to Developers to ensure the Sprint Goal is met.
Coaching the team in organizational environments in which Scrum is not yet fully adopted.
Scrum Masters act as change agents within the organization. They coach the team and the broader organization on how to effectively work within the Scrum framework, even when the surrounding culture is resistant. This helps create an environment where the Developers can maximize their productivity and team health.
Removing impediments to the Developers' progress.
The Scrum Master is explicitly accountable for removing impediments to the Scrum Team's progress. By clearing organizational or technical blockers, the Scrum Master allows Developers to focus entirely on building the Increment, thereby increasing the team's velocity and reducing frustration associated with external delays and bureaucratic hurdles.
Approving the final Increment at the end of the Sprint.
Managing the daily schedule of each Developer to track individual utilization.
Refer to the exhibit. As a Scrum Master, what is your primary concern regarding the Scrum Team's effectiveness?
The velocity is too low for the size of the team.
The Scrum Master is not resolving enough impediments.
The Product Owner is failing to provide necessary support for backlog refinement and collaboration.
The Product Owner must be available to Developers for refinement and questions. Without this interaction, the team may build features that do not meet customer needs. This is a systemic failure in the Scrum Team's collaboration that the Scrum Master must address to ensure the product remains valuable and relevant.
The Developers are not taking enough responsibility for the product vision.
Who is accountable for creating the Sprint Backlog?
The Product Owner.
The Scrum Team as a whole.
The Developers.
The Developers are solely accountable for creating and maintaining the Sprint Backlog. This plan is theirs to manage, update, and follow. By owning the Sprint Backlog, they ensure they are committed to the work they have planned, which is a fundamental aspect of self-management in the Scrum framework.
The Scrum Master.
Want more Scrum Team Roles and Accountabilities practice?
Practice this domainDuring the middle of a Sprint, the Development Team realizes they will not be able to complete all the items selected during Sprint Planning. What is the most appropriate course of action according to Scrum?
Cancel the Sprint immediately and schedule a new Sprint Planning meeting to reset the team capacity.
Work mandatory overtime to ensure all selected Product Backlog items are completed by the end of the Sprint.
Collaborate with the Product Owner to renegotiate the scope of the Sprint Backlog based on revised capacity.
Collaborating with the Product Owner ensures transparency and shared understanding of what can realistically be delivered. The Product Owner adjusts expectations and re-prioritizes remaining work, preserving the Sprint Goal while respecting the team actual delivery capacity.
Independently drop the lowest priority items from the Sprint Backlog without consulting the Product Owner.
A newly formed Scrum Team is struggling to finish their Sprint Backlog items by the end of the time-boxed Sprint. The Product Owner demands that the Sprint duration be doubled to four weeks to accommodate their slow velocity. How should the Scrum Master respond?
Support the Product Owner by extending the Sprint duration to four weeks to provide immediate relief.
Facilitate a discussion with the team to investigate root causes of incomplete work and improve refinement.
Addressing root causes directly targets the delivery process bottlenecks rather than altering the rhythm of the framework. Fixing estimation, backlog refinement, and WIP limits empowers the team to meet goals within the established two-week or shorter time-box.
Advise the team to work through weekends to finish the items so the Sprint length can remain unchanged.
Transfer the unfinished items back to the Product Backlog and cancel the remaining days of the Sprint.
At the Sprint Review, an important stakeholder expresses dissatisfaction with a core feature delivered by the Development Team, stating it does not solve their current business workflow. How should this feedback be handled?
Ignore the feedback because the Development Team strictly followed the requirements provided in the initial backlog.
Scold the Development Team for failing to understand the business needs during Sprint Planning.
Capture the stakeholder feedback as new items in the Product Backlog for the Product Owner to prioritize.
Feedback at the Sprint Review is not a change request to action immediately; it is new information. Logging it in the Product Backlog lets the Product Owner weigh it against other items and re-prioritise, preserving the team's sprint commitment and the Product Owner's sole authority over backlog ordering.
Suspend the release pipeline and force the team to rewrite the entire feature before leaving the room.
Which TWO statements accurately describe the Sprint Review event in Scrum? (Choose TWO)
It is a formal gatekeeping presentation where management approves or rejects the team performance.
It is a collaborative working session with stakeholders to inspect the Increment and adapt the backlog.
Collaboration and adaptation are at the heart of the Sprint Review. Stakeholders and the Scrum Team inspect what was built, discuss market shifts, and collaboratively update the Product Backlog to guide future development.
It is strictly time-boxed to a maximum of four hours for a one-month Sprint.
Scrum defines the Sprint Review as a time-box of at most four hours for a one-month Sprint, with shorter Sprints typically requiring proportionally less time. Time-boxes prevent meetings from dragging on and encourage focused collaboration.
It is primarily used by the Scrum Master to evaluate individual developer velocity and productivity.
It replaces the need for continuous communication and stakeholder engagement throughout the Sprint.
During a Sprint Retrospective, the team identifies a major impediment involving company-wide HR policies that restrict cross-functional collaboration. The team feels helpless to change it. What should the Scrum Master do?
Tell the team to ignore the HR policies and work around them without seeking management support.
Take ownership of the impediment and collaborate with organizational leaders to drive systemic change.
Escalate the impediment beyond the team's authority by engaging organisational leadership, since HR policy sits outside the Scrum Team's control. The Scrum Master owns removing impediments, and systemic, company-wide constraints require influencing decision-makers rather than expecting the team to resolve what they cannot change.
Remove the impediment from the Retrospective action items because it falls outside the Scrum Team control.
Instruct the Product Owner to rewrite the Product Backlog items to avoid cross-functional dependencies.
Which TWO conditions must be met for a Sprint to be officially canceled before its time-box expires? (Choose TWO)
The Development Team realizes they will finish all backlog items two days ahead of schedule.
The Sprint Goal becomes obsolete due to significant shifts in company strategy or market conditions.
An obsolete Sprint Goal renders the entire iteration pointless, making cancellation the correct economic choice. It prevents wasted effort and allows the team to refocus immediately on newly aligned business priorities.
The Product Owner determines that the business need driving the Sprint Goal no longer exists.
The Product Owner holds the ultimate accountability for product value and can cancel the Sprint if the business rationale vanishes. This protects the organization from building features that no longer serve strategic goals.
Key developers fall ill, causing a temporary reduction in team velocity for the current iteration.
The Scrum Master and senior executives mutually agree that the team is moving too slowly.
Want more Scrum Events practice?
Practice this domainA Scrum Team is struggling to maintain focus during the Sprint because external stakeholders frequently interrupt Developers with requests for minor feature tweaks. How should the Scrum Master address this?
Direct the Developers to ignore all external communication until the Sprint ends.
Update the Sprint Backlog to include these minor tweaks immediately.
Coach the stakeholders on why the Product Owner is the sole person responsible for managing the Product Backlog.
Directing stakeholders to the Product Owner ensures that requests are properly prioritized and evaluated against the product strategy. This protects the Developers from context switching and keeps the team focused on the Sprint Goal, reinforcing the accountabilities defined in the Scrum Guide regarding product backlog management and stakeholder engagement.
Require that the Developers hold a formal meeting with stakeholders every day.
During a Sprint Retrospective, the Scrum Team identifies that their technical debt is preventing them from meeting the Definition of Done. What is the most effective way for the Scrum Master to serve the team?
Force the team to dedicate 50% of every Sprint exclusively to technical debt.
Advise the Developers to discuss the impact of technical debt with the Product Owner.
Transparency is essential; the Product Owner must understand that debt affects the team's ability to deliver value. By facilitating this conversation, the Scrum Master empowers the team to advocate for quality, ensuring the Product Backlog reflects the necessary work to maintain a high-quality, releasable increment for stakeholders.
Ask the Product Owner to remove items from the Product Backlog to save time.
Request that management hire additional developers to handle the technical debt.
A Scrum Master observes that the Developers are taking too long to reach a consensus during their Daily Scrum. What should the Scrum Master do to support the team?
Facilitate the meeting and force everyone to speak in a strict rotation.
Coach the team on the purpose of the Daily Scrum and help them identify ways to keep it time-boxed.
Coaching focuses on helping the team understand the 'why' behind the event, allowing them to self-organize and adjust their behavior. This approach builds long-term effectiveness rather than providing a short-term fix. It respects the Developers' autonomy while ensuring the event provides the intended synchronization value for their daily goals.
Limit the number of people who are allowed to speak during the meeting.
Suggest that the team move the meeting to an asynchronous communication tool.
Which action best demonstrates the Scrum Master's commitment to serving the Scrum Team as a coach?
Updating the team's Jira board daily to ensure tasks are tracked correctly.
Asking open-ended questions that lead the team to find their own solutions.
Coaching involves guiding the team through reflection so they can solve their own problems. This fosters long-term growth and independence within the team, which is central to the Scrum Master's role. It creates a culture of continuous improvement where the team feels empowered to own their processes and outcomes.
Assigning specific tasks to each team member during the Sprint Planning meeting.
Attending all meetings to ensure nobody deviates from the official Scrum Guide.
The Scrum Master is serving the team during the Sprint Retrospective. Which TWO of the following actions are appropriate for the Scrum Master to take? (Choose two)
Facilitate the meeting to ensure all participants have a chance to contribute.
Facilitation is a core skill for the Scrum Master to ensure all voices are heard and the team achieves a shared understanding. This leads to better problem identification and more effective solutions. Ensuring balanced participation prevents dominant voices from overshadowing others, creating a more inclusive and effective retrospective outcome.
Direct the team on exactly which process changes they must implement next.
Ensure that the team identifies at least one concrete improvement for the next Sprint.
A key outcome of the Retrospective is an actionable plan for improvement. By holding the team to this standard, the Scrum Master fosters a culture of continuous learning. This ensures that the time spent in the retrospective leads to tangible, positive changes in how the team works together moving forward.
Invite external stakeholders to witness the team's internal conflicts.
Assign the least performing team member to lead the next Retrospective.
Refer to the exhibit. A Scrum Master notices this status report for a blocker affecting the team. What should be the Scrum Master's immediate response to serving the team?
Immediately send the escalation to upper management to clear the path.
Help the team reach out to the other involved team to facilitate a collaborative solution.
Facilitating cross-team collaboration is a key responsibility. By helping the teams connect, the Scrum Master promotes transparency and shared problem-solving. This approach is more sustainable than escalation, as it builds bridges between teams and addresses the root cause of the dependency rather than just reporting the symptom to management.
Document the delay in the Sprint backlog and adjust the Sprint Goal accordingly.
Tell the Product Owner that the current Sprint is now a failure and should be cancelled.
Want more Service to the Scrum Team practice?
Practice this domainAn organization is transitioning to Scrum. The Scrum Master notices that middle management continues to assign specific tasks to developers during the Sprint. How should the Scrum Master handle this?
Ask the Product Owner to prevent managers from entering the team area.
Instruct the developers to politely refuse the assigned tasks.
Coach the management team on the benefits of self-organizing teams.
Coaching is the primary tool for a Scrum Master when influencing organizational structure. By explaining how autonomous teams deliver higher value and faster feedback, the Scrum Master helps managers see the benefits of stepping back. This systemic change supports long-term agility and empowers developers to manage their own commitments.
Include the managers in the Daily Scrum to improve communication.
Refer to the exhibit. As a Scrum Master serving the organization, what is the most appropriate action regarding these policies?
Enforce these policies strictly to maintain organizational compliance.
Facilitate a discussion with leadership to redefine these policies.
Proactively addressing organizational impediments is a core responsibility. The Scrum Master must use data and Scrum principles to demonstrate why these policies prevent team autonomy and empirical learning. By helping leaders understand the negative impact, the Scrum Master fosters a more supportive environment for the teams to succeed.
Ask the team to ignore the policies while continuing their work.
Advise the PMO to attend the Sprint Review to gain transparency.
Which TWO of the following actions best demonstrate a Scrum Master serving the organization during an enterprise-wide transformation? (Choose two)
Hosting training sessions for stakeholders on Scrum values.
Educating stakeholders is essential for organizational buy-in. When leaders understand the 'why' behind Scrum, they become better supporters rather than barriers. This educational effort ensures that the entire organization speaks a common language, reducing friction and setting realistic expectations for the teams as they embrace agility.
Managing the team's JIRA tickets to ensure perfect velocity.
Working with other Scrum Masters to align organizational processes.
Collaboration across Scrum Masters is critical for scaling agility. By aligning processes, they identify systemic bottlenecks that affect multiple teams. This collective effort provides a unified voice when speaking to leadership, making it easier to drive the cultural and structural changes needed for the entire organization's transformation.
Taking notes during every meeting to ensure reporting consistency.
Directing the team on which technical practices to implement.
A department head complains that they don't know the exact release date for the next major feature. What is the most effective way for the Scrum Master to serve the organization in this situation?
Ask the Product Owner to provide a firm date to appease them.
Explain that the team works in Sprints and dates are irrelevant.
Coach the department head on how to use Sprint Reviews for transparency.
The Sprint Review is the primary venue for stakeholders to inspect product progress. By coaching the stakeholder on how to participate and what to expect, the Scrum Master turns a complaint into a productive engagement, fostering transparency and trust while adhering to the core tenets of Scrum.
Create a Gantt chart showing projected delivery dates for them.
Which THREE of the following are valid ways a Scrum Master serves the organization by improving the Scrum implementation? (Choose three)
Leading the organizational transformation to Scrum.
The Scrum Master is explicitly tasked with leading and coaching the organization in its Scrum adoption. This is a high-level responsibility that involves identifying patterns in the organization that hinder or support Scrum. It requires continuous improvement efforts across departments, not just within the Scrum Team itself.
Planning and executing the product release schedule.
Working with other Scrum Masters to increase effectiveness.
Collaboration with peers creates a community of practice that is essential for scaling Scrum. By sharing experiences and identifying organizational roadblocks together, Scrum Masters can exert more influence on leadership to drive meaningful change. This collective effort is more effective than any single Scrum Master working in isolation.
Setting individual performance goals for developers.
Helping employees and stakeholders understand empirical work.
Empiricism—transparency, inspection, and adaptation—is the foundation of Scrum. Many organizations struggle because they do not understand this concept, leading them to treat Scrum as a standard project plan. By teaching these principles, the Scrum Master helps everyone understand the necessity of flexibility and constant feedback loops.
When a Scrum Master is asked to serve as a project manager, how should they respond?
Accept the role to maintain good relationships with leadership.
Educate the organization on the differences between the roles.
Clear communication is vital for organizational understanding. By contrasting the servant-leadership of a Scrum Master with the administrative focus of a project manager, the Scrum Master helps leadership understand why they need an agile facilitator rather than a task master to achieve the desired organizational results.
Create a new role title called 'Scrum Project Manager'.
Perform the tasks of both roles to ensure nothing is missed.
Want more Service to the Organization practice?
Practice this domainThe CSM exam has 60–90 questions and must be completed in 120 minutes. The passing score is 700/1000.
Scenario-based questions covering exam objectives with detailed answer explanations.
The exam covers 6 domains: Service to the Product Owner, Scrum Master Core Competencies, Scrum Team Roles and Accountabilities, Scrum Events, Service to the Scrum Team, Service to the Organization. Questions are weighted by domain — higher-weight domains appear more on your actual exam.
No. These are original exam-style practice questions written against the official Scrum Alliance CSM exam objectives. They are not copied from the real exam. Courseiva focuses on genuine understanding, not memorisation of braindumps.
Courseiva tracks your accuracy per domain and routes you toward weak areas automatically. Free, no account required.