Mentoring Individuals and the Organization – A Comprehensive Guide for PSM II
Introduction
Mentoring Individuals and the Organization is a critical competency area within the Developing People and Teams domain of the Professional Scrum Master II (PSM II) certification. As a Scrum Master operating at an advanced level, your role extends far beyond facilitating Scrum events. You are expected to be a mentor, coach, and servant-leader who helps individuals grow, teams mature, and the broader organization evolve in its understanding and adoption of Scrum and agile principles.
Why Is Mentoring Individuals and the Organization Important?
Mentoring is one of the most powerful levers a Scrum Master has for creating lasting, sustainable change. Here is why it matters:
1. Sustainable Agility: Without mentoring, teams and organizations often adopt Scrum mechanically — following the framework's ceremonies without truly embracing the underlying values and principles. Mentoring helps people internalize why Scrum works, not just how it works.
2. Individual Growth: Every person on a Scrum Team has different strengths, weaknesses, and learning styles. A Scrum Master who mentors individuals helps them unlock their potential, develop new skills, and become more effective contributors. This includes Product Owners, Developers, stakeholders, and even other Scrum Masters.
3. Organizational Transformation: Organizations do not transform by decree. They transform when people at every level understand and embrace new ways of working. Mentoring at the organizational level helps leadership understand empiricism, helps HR departments rethink performance management, and helps managers shift from command-and-control to servant leadership.
4. Building Self-Managing Teams: The goal of a Scrum Master is ultimately to develop teams that can function effectively with minimal intervention. Mentoring is how you gradually transfer knowledge, build confidence, and develop the team's capability to self-manage.
5. Removing Systemic Impediments: Many impediments are organizational in nature — policies, structures, and cultural norms that hinder agility. Mentoring organizational leaders helps them see these impediments and empowers them to take action.
What Is Mentoring in the Context of a Scrum Master?
Mentoring, in the Scrum Master context, is the practice of guiding, advising, and supporting individuals and the organization based on your experience and knowledge of Scrum, agile principles, and effective team dynamics. It differs from other stances a Scrum Master might take:
- Mentoring vs. Coaching: While coaching is about asking powerful questions to help people discover their own answers, mentoring involves sharing your own experience, knowledge, and advice more directly. A mentor says, "In my experience, here is what has worked…" A coach asks, "What do you think would work?" Both are important, and a skilled Scrum Master knows when to use each approach.
- Mentoring vs. Teaching: Teaching is about transferring knowledge in a structured way (e.g., explaining the Scrum framework). Mentoring is more relational and ongoing — it involves walking alongside someone as they apply what they have learned in real-world situations.
- Mentoring vs. Facilitating: Facilitation is about creating an environment where productive conversations and collaboration can happen. Mentoring is more one-on-one or small-group focused and involves personal guidance.
The Scrum Guide describes the Scrum Master as serving the Scrum Team, the Product Owner, and the Organization. Mentoring cuts across all three of these service areas.
How Does Mentoring Individuals Work?
Mentoring individuals involves tailoring your guidance to each person's unique context, needs, and growth trajectory. Here are the key aspects:
1. Mentoring Developers:
- Help individual Developers understand their role within a self-managing team
- Guide them in adopting technical practices that support agility (e.g., continuous integration, test-driven development, pair programming)
- Support them in developing collaboration skills, giving and receiving feedback, and resolving conflicts
- Help them understand how to break work into small increments and deliver value iteratively
- Encourage a growth mindset and help them see failures as learning opportunities
2. Mentoring the Product Owner:
- Help the Product Owner understand how to maximize the value of the product
- Guide them in effective Product Backlog management techniques
- Support them in stakeholder engagement and communication strategies
- Help them develop skills in ordering the Product Backlog based on value, risk, and dependencies
- Mentor them on how to create clear, concise Product Goals and communicate the product vision
- Help them understand empiricism and how to make data-driven decisions
3. Mentoring Other Scrum Masters:
- Share experiences and lessons learned from your own practice
- Help less experienced Scrum Masters navigate complex team dynamics
- Guide them in developing their own coaching, mentoring, teaching, and facilitating skills
- Support them in understanding when to use which stance
4. Mentoring Stakeholders and Managers:
- Help managers understand the shift from managing individuals to supporting self-managing teams
- Guide them in understanding how to create an environment that supports agility
- Help stakeholders understand how to engage effectively with Scrum Teams
How Does Mentoring the Organization Work?
Mentoring at the organizational level is about helping the broader organization understand and embrace Scrum values, empiricism, and lean-agile thinking. This is often the most challenging and impactful aspect of the Scrum Master role.
1. Leading the Adoption of Scrum and Empiricism:
- Help the organization understand why Scrum works, not just the mechanics
- Guide leadership in understanding transparency, inspection, and adaptation as organizational principles
- Help the organization understand the importance of delivering working product increments frequently
2. Helping the Organization Restructure:
- Mentor leadership on how organizational structures (e.g., siloed departments, matrix management) can hinder or support agility
- Guide conversations about moving toward cross-functional, product-oriented teams
- Help the organization understand the impact of dependencies between teams and how to reduce them
3. Addressing Organizational Impediments:
- Identify policies, processes, and cultural norms that impede agility
- Mentor leaders and decision-makers on alternative approaches
- Help the organization understand concepts like reducing batch size, limiting work in progress, and reducing handoffs
4. Evolving HR and People Practices:
- Guide the organization in rethinking performance reviews (from individual-focused to team-focused)
- Help HR understand career paths in agile organizations
- Mentor leadership on creating incentive structures that support collaboration rather than competition
5. Building a Learning Organization:
- Help the organization create communities of practice
- Guide the creation of knowledge-sharing mechanisms
- Encourage experimentation and help the organization become comfortable with failure as a learning mechanism
- Model and promote the Scrum values of Commitment, Focus, Openness, Respect, and Courage at every level
6. Helping with Product Thinking:
- Mentor the organization on shifting from project-based thinking to product-based thinking
- Help leadership understand the value of long-lived, stable teams working on products rather than short-lived project teams
- Guide conversations about funding models that support agility (e.g., funding teams rather than projects)
Key Principles to Remember
- Meet people where they are: Effective mentoring requires understanding the current level of understanding and maturity of the individual or organization. You cannot force growth — you can only create the conditions for it and guide people along the path.
- Be patient and persistent: Organizational change is slow. Mentoring is a long-term investment, not a quick fix.
- Use the Scrum values as your guide: Every mentoring interaction should be grounded in Commitment, Focus, Openness, Respect, and Courage.
- Lead by example: The most powerful mentoring happens when you model the behaviors and mindset you are trying to develop in others.
- Adapt your approach: Different individuals and organizations need different types of support. Sometimes you need to be directive (mentoring/teaching), sometimes you need to be facilitative (coaching/facilitating). The key is knowing when to use which approach.
- Focus on root causes, not symptoms: When mentoring individuals or the organization, always look for the underlying causes of problems rather than just addressing surface-level symptoms.
Exam Tips: Answering Questions on Mentoring Individuals and the Organization
The PSM II exam tests your ability to apply Scrum Master knowledge in complex, real-world scenarios. Here is how to approach questions related to mentoring:
1. Understand the Scrum Master's Service to Three Groups:
The Scrum Guide explicitly describes how the Scrum Master serves the Scrum Team, the Product Owner, and the Organization. Many questions will test whether you understand the nuances of these three service areas. Know the specific ways a Scrum Master serves each group as described in the Scrum Guide, and understand how mentoring is woven into each.
2. Choose Answers That Empower, Not Control:
When faced with a scenario question, always prefer answers that empower individuals and teams to grow and solve their own problems. Avoid answers that have the Scrum Master solving problems for people, making decisions on their behalf, or taking a command-and-control approach. The best answer usually involves the Scrum Master guiding, mentoring, or coaching rather than directing or dictating.
3. Know When to Mentor vs. Coach vs. Teach vs. Facilitate:
The exam may present scenarios where you need to choose the right stance. Remember:
- Mentor when someone would benefit from your experience and advice
- Coach when someone needs to develop their own understanding through self-discovery
- Teach when someone lacks foundational knowledge
- Facilitate when a group needs to collaborate and reach shared understanding
If a scenario describes a person who is new and struggling, mentoring or teaching may be appropriate. If the person has the knowledge but is not applying it, coaching might be better.
4. Think Organizationally, Not Just at the Team Level:
PSM II is an advanced certification. Many questions will test your understanding of the Scrum Master's role beyond a single team. Be prepared for questions about how a Scrum Master mentors management, leadership, HR, and other parts of the organization. The correct answer often involves helping the organization understand the impact of its structures, policies, and culture on agility.
5. Look for Answers Grounded in Empiricism:
Scrum is founded on empiricism — transparency, inspection, and adaptation. When mentoring individuals or the organization, the Scrum Master should always promote empirical thinking. Prefer answers that emphasize making things visible (transparency), reviewing outcomes (inspection), and making adjustments based on what is learned (adaptation).
6. Avoid Prescriptive or Mechanical Answers:
The PSM II exam rarely rewards rigid, by-the-book answers. Instead, look for answers that demonstrate understanding and contextual awareness. If an answer sounds like a checkbox exercise (e.g., "implement all Scrum events exactly as described"), it is probably not the best choice. The better answer will usually acknowledge the complexity of the situation and suggest a mentoring or coaching approach to help people understand and adapt.
7. Remember That the Goal Is Self-Management:
The ultimate goal of mentoring is to help teams become self-managing and individuals become more capable. Prefer answers that move people toward independence rather than dependence on the Scrum Master. A great Scrum Master works to make themselves less needed over time.
8. Pay Attention to Who Needs Mentoring:
Read scenario questions carefully to identify who needs mentoring. Is it a Developer who does not understand cross-functionality? Is it a Product Owner who is not engaging stakeholders effectively? Is it a manager who is assigning work to team members? The correct answer will target the right person or group with the right type of support.
9. Consider the Scrum Values:
Many correct answers on the PSM II exam align with the Scrum values. If you are unsure between two answer choices, consider which one better promotes Commitment, Focus, Openness, Respect, and Courage. Mentoring should always reinforce these values.
10. Practice Scenario-Based Thinking:
The PSM II exam is full of scenario-based questions that describe complex organizational situations. Practice reading these scenarios carefully, identifying the core issue, determining who needs support, and selecting the approach that best aligns with the Scrum Master's role as a mentor and servant-leader.
11. Understand the Difference Between Mentoring the Individual vs. the Organization:
Some questions will test whether you can distinguish between individual-level mentoring and organizational-level mentoring. Individual mentoring is about helping a specific person grow. Organizational mentoring is about helping the broader system evolve. Both are essential, and the Scrum Master must be able to operate at both levels.
12. Do Not Confuse Mentoring with Micro-Managing:
If an answer choice has the Scrum Master closely overseeing, controlling, or managing someone's work, that is not mentoring — that is micro-management. True mentoring involves guidance, support, and encouragement while respecting the autonomy of the individual or team.
Summary
Mentoring Individuals and the Organization is a foundational competency for an advanced Scrum Master. It involves guiding people and organizational systems toward deeper understanding and adoption of Scrum, empiricism, and agile principles. On the PSM II exam, demonstrate your ability to choose the right stance at the right time, empower others to grow, think beyond the team level, and always ground your approach in the Scrum values and empiricism. The best Scrum Masters are those who create lasting change through patient, persistent, and thoughtful mentoring.
