Scrum is all about focus, collaboration, and clear roles—but what about the people and influences surrounding your team? Recognizing the roles outside the core Scrum team can make the difference between confusion and clarity, chaos and high performance.
A person or group, internal or external to the organization, who affects or is affected by the team’s work.
An experienced guide who helps Scrum teams mature, avoid old habits, and stick to best practices for optimal results.
Product owner and scrum master are integral scrum roles created by the founders of scrum. Developer is another role. But like all good things, project management and product development are evolving and growing. Scrum remains a solid framework and foundation. Some common and proven practices can add value.
The following two roles aren’t explicit scrum accountabilities of the scrum team, but we’ve found that acknowledging them adds enormous value and clarity. Consider clarifying these roles in your organization to optimize your scrum team’s success.
Stakeholders
Stakeholders are people who affect or are affected by your work. Internal stakeholders are within your company or organization; they could be from the legal, sales, marketing, management, procurement, a neighbor, or even a friend. External stakeholders could be investors, users, or even your mother-in-law.
Although scrum prescribes only scrum team members, the stakeholder role explicitly interfaces with scrum teams, and we prefer to acknowledge this role so we can manage it. The product owner is the business interface for the scrum team, so stakeholders should work with the developers through the product owner. Stakeholders may communicate directly with the developers during sprint reviews or when a developer contacts them directly for clarification, but stakeholders generally work through the product owner.
Two roles deal with stakeholders:
- The product owner is responsible if the stakeholders are on the business side (such as customers, sales teams, or marketing).
- If the stakeholders are on the nonbusiness side (such as vendors or contractors), the scrum master is usually responsible.
The key to interacting successfully with stakeholders is recognizing and leveraging stakeholders’ influence while shielding the developers from interference.
Many organizations struggle with stakeholder management because roles are not clearly defined, leading to mixed messages and slowed progress. Establishing clear channels of communication, as recommended here, sets successful teams apart.
Think about a recent project you worked on—were all stakeholders clearly identified and engaged at the right times?
Scrum mentors
As we’ve said, scrum is a simple framework in concept, but it’s not easy in practice. The same can be said of golf. Theoretically, you use a stick to whack a motionless white ball into a hole, using the fewest strokes possible. Yet, in practice, golf isn’t easy. Like scrum, it’s a game of nuance. Small factors make an enormous difference in performance.
The mentor, sometimes called a scrum or agile coach, will work alongside the team to help them develop maturity in practicing scrum. The benefit of using a mentor is that mentors are outside the normal politics and focus on getting the product out the door. They can step back and see objectively how the team works. Not only can they identify old habits, but they can also put the brakes on homemade modifications to scrum, which are simply ways to let an old dog do its old tricks.
You’ll have the greatest ease and success with scrum if you stick to it in its truest form. A scrum mentor’s job is to help team members keep good form. Like athletic coaches, they stand aside; see old, unproductive habits; and help you form new habits that make you successful.
Want to go deeper? Why “just following Scrum” is harder than it looks
It’s tempting for teams to invent shortcuts or blend old project habits into Scrum, thinking it’ll speed things up or fit their unique culture. In reality, these “homemade modifications” often undermine the very benefits Scrum was designed to provide. Mentors help teams unlearn these habits and build a disciplined, high-performing culture based on proven principles, not convenience.
SWINGING TO SUCCESS
Years ago, Mark took up golf for business and, in the process, caught the golf bug. He loved it, worked at it, and improved his game. But he always struggled with consistency. So, he hired a golf coach.
The coach teed up a ball in the first session, and Mark hit it. The coach watched that one swing and said, “I know what your problem is.” Mark was incredulous. How could the coach possibly know what was wrong with Mark’s swing by watching him just one time?
Then, the coach said, “You used to play baseball, didn’t you?” Mark had played baseball for years. In fact, the coach could tell right away that Mark’s golf swing was like his baseball swing. Mark had carried an old habit into the new sport.
When you convert to scrum, you, too, will carry habits (even ones that you don’t realize you have) from a lifetime of managing your work differently.
Scrum is a simple framework in concept, but it’s not easy in practice.
Can you identify any “old habits” from past project experiences that might affect your team’s ability to fully embrace Scrum?
In fast-moving tech companies, external stakeholders like investors may pressure teams for updates. Understanding that communication should flow through the product owner avoids misalignment and protects the team’s focus.
Only Scrum team members are important to project success—everyone else is just background noise.
Stakeholders and mentors, though not part of the core Scrum team, profoundly impact the team’s clarity, focus, and long-term effectiveness.
Why is it important for mentors or coaches to remain outside the team’s usual organizational politics?
Identify all stakeholders for a current or recent project and clarify their roles.
- List every person or group who affects or is affected by your team’s work.
- Classify each as internal or external, business or nonbusiness side, and note their primary interest.
- Decide who should interact with each stakeholder: product owner or scrum master?
- Reflect on any gaps or potential overlaps you discover.
Who is the main interface between stakeholders and the development team in Scrum?
Tap to revealThe product owner acts as the business interface for the Scrum team, channeling stakeholder communication.
What is the primary benefit of having a Scrum mentor or agile coach?
Tap to revealA Scrum mentor helps the team mature, avoid ineffective old habits, and stick to best practices objectively.
Who is typically responsible for managing nonbusiness stakeholders?
Tap to revealThe Scrum master usually manages nonbusiness stakeholders, such as vendors or contractors.
Describe a time when having a mentor or outside coach helped you (or could have helped you) break an unproductive habit in your work or team. What changed as a result?
How should stakeholders generally communicate with developers in Scrum?
- Defined the roles of stakeholders and scrum mentors outside the core team
- Clarified how communication should flow between stakeholders and the team
Recognizing and clarifying roles outside the Scrum team—especially stakeholders and mentors—maximizes team effectiveness and shields developers from unnecessary interference.
Sticking to true Scrum principles is challenging but essential, and mentors play a critical role in helping teams avoid unproductive old habits.