I85PREP
⌘ K
SM study materials
SM study resources

SM: Servant Leadership and Stakeholder Engagement

SM · Work through your exam, one topic at a time.

All guide sections

Servant Leadership and Stakeholder Engagement

What you must know

Servant leadership in Scrum means the Scrum Master leads by serving the needs of the team, the Product Owner, and the organization. Concretely, the SM helps the team become self-managing and cross-functional, helps the PO find techniques for effective backlog management and stakeholder collaboration, and helps the organization understand and adopt Scrum. The SM's authority comes from influence, not from a reporting line.

Stakeholder engagement centers on the Product Owner as the single point of contact for product decisions, with the SM supporting productive collaboration. The Sprint Review is the primary formal opportunity to engage stakeholders: showing the Increment, gathering feedback, and adapting the Product Backlog. Stakeholders are not a nuisance to be managed away; their feedback is essential input to empiricism. The SM may coach stakeholders on how to give useful feedback and coach the PO on involving them early and continuously.

Key concepts: servant leadership (remove obstacles, shield from distraction, enable growth), stakeholder collaboration (continuous, not a one-time sign-off), organizational change (the SM influences culture and policy), and value focus (decisions align with the Product Goal and value, not activity).

Traps

  • "The SM shields the team from all stakeholder contact" - stakeholders must be engaged; the SM protects focus, not isolates the team.
  • "Stakeholder feedback is collected only at release" - feedback is continuous and formalized at each Sprint Review.
  • "The SM owns the stakeholder relationship" - the PO does; the SM supports it.
  • "Servant leadership means doing whatever the team asks" - it means serving their growth and effectiveness, which sometimes means saying no.

Rule of thumb

Ask: Does this action increase the team's ability to deliver value and engage stakeholders productively, or does it create dependency on the SM? Choose the option that builds capability and connection, not dependency.

Worked example: A key stakeholder bypasses the PO and asks Developers for new features mid-Sprint. The SM coaches the stakeholder to bring requests to the PO for ordering, and helps the team stay focused on the Sprint Goal - protecting focus while keeping engagement open.