PSM III Developing People and Teams

Developing People and Teams Detailed Explanation

In this section, we will go step by step into how the Scrum Master helps teams develop, with a special focus on leadership, psychological safety, team culture, conflict resolution, and coaching an agile mindset.

Scrum is not just about delivering work efficiently—it is about building strong, self-organizing, and collaborative teams. The Scrum Master plays a crucial role in enabling teams to reach high performance.

2.1 The Role of the Scrum Master in Team Development

A Scrum Master is not a project manager, nor a traditional leader who gives orders. Instead, the Scrum Master enables teams to work effectively by guiding, coaching, and removing obstacles.

A great Scrum Master helps teams evolve from a group of individuals into a cohesive, high-performing unit.

2.1.1 Servant Leadership

One of the most important concepts in Scrum is servant leadership. The Scrum Master is a leader who serves rather than one who commands.

What does a Servant Leader do?

A Servant Leader:

• Removes impediments that block team progress.
• Facilitates collaboration by ensuring team members communicate effectively.
• Provides guidance on Scrum principles while allowing the team to self-organize.
• Creates an environment of trust where the team can grow and take ownership.

What does a Servant Leader NOT do?

A Servant Leader does not:

• Micromanage the team or dictate how work should be done.
• Control the team’s decisions—instead, they empower the team to make decisions.
• Ignore team problems—instead, they proactively address them.

Example: Servant Leadership in Action

A Scrum Team is struggling because their Product Owner is unavailable and backlog items are unclear.
A Servant Leader does not solve this problem alone but facilitates a conversation between the Product Owner and the team to improve backlog refinement.

2.1.2 Coaching vs. Managing

A Scrum Master coaches rather than manages a team. Coaching helps teams become independent thinkers, while managing tells them what to do.

Coaching	Managing
Helps the team grow	Focuses on task completion
Encourages self-organization	Controls and monitors work
Asks open-ended questions	Gives direct instructions
Helps the team find solutions	Makes decisions for the team

Example: Coaching vs. Managing

A Developer is struggling with a technical problem.

• A Manager would say: "Use approach X to fix the problem."
• A Coach (Scrum Master) would say: "What options have you considered? What are the trade-offs of each?"

The goal of coaching is to help the team learn and grow so that they can solve problems on their own.

2.1.3 Enabling Self-Organization

A self-organizing team decides how to do the work without outside direction. This is a key principle in Scrum.

Self-organizing teams:

• Take ownership of their work.
• Decide how to achieve Sprint Goals.
• Distribute tasks among themselves rather than being assigned tasks by a manager.

How the Scrum Master Facilitates Self-Organization

• Encourages autonomy—allows teams to make their own technical decisions.
• Provides guidance when needed—but does not impose solutions.
• Promotes accountability—team members hold each other responsible.

Example: Self-Organization in Action

A Product Owner asks a team to build a reporting dashboard.

• In a traditional setup, a manager would assign tasks to Developers.
• In a Scrum Team, the team decides how to build the dashboard, who will do what, and what approach to take.

The Scrum Master supports but does not direct this process.

2.2 Psychological Safety and Team Culture

A high-performing team requires a culture of trust and openness. Without psychological safety, teams avoid risks, hide mistakes, and do not innovate.

2.2.1 Psychological Safety

A psychologically safe team is one where members feel comfortable expressing ideas, raising concerns, and admitting mistakes without fear of punishment.

Signs of a Psychologically Safe Team

• Members openly discuss mistakes and learn from them.
• Constructive feedback is given without fear of retaliation.
• New ideas are welcomed rather than dismissed.
• Team members ask for help when needed.

How a Scrum Master Fosters Psychological Safety

• Encourages open discussions—asks team members to share opinions in Retrospectives.
• Protects team members from blame—focuses on process improvement instead of personal blame.
• Promotes continuous learning—mistakes are seen as learning opportunities.

Example: Psychological Safety in Action

A Developer accidentally introduces a bug that breaks the application.

• In an unsafe environment: The Developer is blamed, and others become afraid to take risks.
• In a psychologically safe environment: The team discusses how to prevent similar issues in the future and improves the testing process.

2.2.2 Building a Collaborative Team Culture

A strong team culture ensures that members work together rather than in isolation.

Elements of a Strong Team Culture

1. Trust – Team members rely on each other and assume good intentions.
2. Transparency – Work, decisions, and challenges are visible to all.
3. Shared Responsibility – The team owns the outcome, not just individuals.

How a Scrum Master Strengthens Team Culture

• Facilitates team-building exercises to build trust.
• Encourages knowledge sharing between Developers.
• Celebrates team successes and recognizes contributions.

Example: Building Team Culture

A new Scrum Team lacks trust, and Developers prefer to work alone.

• The Scrum Master introduces pair programming and a knowledge-sharing session to improve collaboration.

Over time, Developers start asking for help more freely and working together more effectively.

2.3 Conflict Management and Resolution

Conflict in teams is normal. What matters is how the team and Scrum Master handle it. Conflicts, if managed well, can lead to better solutions, stronger collaboration, and improved team dynamics.

2.3.1 Types of Conflict in Scrum Teams

Scrum teams may experience different types of conflict:

Type of Conflict	Definition
Task-related conflicts	Disagreements about how to do the work (healthy).
Interpersonal conflicts	Clashes between team members due to personalities, communication styles, or work ethics (unhealthy if unresolved).

Not all conflicts are bad. Task-related conflicts can drive innovation, while unresolved interpersonal conflicts can damage trust and team performance.

2.3.2 Conflict Resolution Strategies

Conflict Type	Scrum Master’s Approach
Technical disagreements	Encourage experimentation, data-driven discussions, and compromise.
Miscommunication	Facilitate open dialogue to clarify misunderstandings.
Personality clashes	Mediate privately, focus on common goals.

Techniques for Conflict Resolution

1. Active Listening – Ensure everyone is heard before making decisions.
2. Nonviolent Communication – Express concerns constructively.
3. Mediation – Act as a neutral party to facilitate discussions.
4. Focusing on Shared Goals – Redirect attention to the Sprint Goal or product vision.

Example: Resolving a Technical Disagreement

Two Developers disagree on how to implement a new feature.

• The Scrum Master encourages data-driven discussions.
• The team conducts a small experiment (A/B testing).
• A data-based decision is made, reducing unnecessary debate.

Example: Resolving an Interpersonal Conflict

A Developer complains that another team member is too slow.

• The Scrum Master privately discusses the issue with both parties.
• They clarify work expectations and agree on a collaborative approach.

2.4 Coaching and Developing an Agile Mindset

A key responsibility of the Scrum Master is helping teams adopt an agile mindset—a way of thinking that embraces change, learning, and continuous improvement.

2.4.1 The Scrum Master’s Role in Agile Coaching

The Scrum Master helps teams:

• Understand the purpose behind agile values.
• Adopt continuous improvement habits.
• Shift from a fixed mindset to a growth mindset.

Coaching is not about giving solutions but guiding the team to find solutions themselves.

Example: Coaching Agile Thinking

A Developer is frustrated by frequent changes to the backlog.

• The Scrum Master explains the value of responding to change.
• The Developer learns to adapt and see change as an opportunity.

2.4.2 Growth Mindset vs. Fixed Mindset

Growth Mindset	Fixed Mindset
"Failure is a learning opportunity."	"Failure means I’m not good enough."
"I can learn new skills with effort."	"I’m either good at something or not."
"Challenges help me grow."	"Challenges are threats."

How Scrum Masters Foster a Growth Mindset

Celebrate small improvements.
Encourage learning from failure.
Support experimentation and innovation.

Example: Encouraging a Growth Mindset

A Developer struggles with test automation.

• Instead of saying, "I can't do this," the Scrum Master encourages a learning approach.
• They pair-program with another Developer to gain confidence.

2.5 Team Development Stages (Tuckman Model)

Teams evolve over time, and the Scrum Master plays an important role at each stage.

Stage	Characteristics	Scrum Master’s Role
Forming	Team members are polite, roles unclear.	Provide guidance, clarify roles.
Storming	Conflict arises, team members test boundaries.	Mediate conflicts, encourage open discussions.
Norming	Trust builds, team finds rhythm.	Reinforce positive behaviors.
Performing	Team is self-organizing, highly effective.	Step back, support autonomy.
Adjourning	Project ends, team disbands.	Celebrate success, ensure knowledge transfer.

Example: Storming to Norming

A new Scrum Team struggles with disagreements.

• The Scrum Master encourages open feedback.
• Over time, the team learns to communicate effectively and trust each other.

2.6 Measuring and Improving Team Performance

A great Scrum Master tracks progress using agile metrics but ensures the focus remains on delivering value.

Key Agile Metrics for Scrum Teams

Metric	Definition	Purpose
Velocity	Work completed per Sprint (measured in story points or tasks).	Helps forecast future capacity.
Cycle Time	Time taken to complete a task from start to finish.	Measures efficiency.
Lead Time	Time from backlog entry to delivery.	Helps optimize workflows.
Sprint Goal Success Rate	% of Sprints where the Sprint Goal was met.	Assesses team focus and goal-setting.
Happiness Index	Team members' self-reported satisfaction.	Measures morale and engagement.

Caution: Avoid Vanity Metrics

• Velocity is useful, but should not be used as a performance measure.
• The number of story points does not matter as much as delivering value.

Example: Using Metrics to Improve

A team struggles with meeting Sprint Goals.

• The Scrum Master tracks Cycle Time and finds bottlenecks.
• They introduce pair programming to improve efficiency.

2.7 Overcoming Common Team Challenges

Scrum teams operate in dynamic environments where challenges frequently arise. The Scrum Master must recognize these challenges and facilitate solutions.

2.7.1 Working with Distributed Teams

In an ideal world, Scrum teams are co-located to maximize face-to-face interactions. However, many organizations have distributed or remote teams working from different locations and time zones.

Challenges of Distributed Teams

Challenge	Impact
Time zone differences	Limited real-time collaboration.
Communication gaps	Delayed responses, misunderstandings.
Lack of team bonding	Reduced trust and collaboration.
Transparency issues	Difficulties tracking work progress.

Best Practices for Distributed Scrum Teams

Solution	Benefit
Define core overlapping hours	Ensures real-time collaboration.
Use video calls for key meetings	Improves engagement and understanding.
Document decisions clearly	Reduces miscommunication.
Encourage virtual team-building	Strengthens relationships.
Use tools like Jira, Miro, Confluence	Enhances transparency.

Example: Overcoming Time Zone Issues

A Scrum team has members in the US, India, and Germany.
To address time zone challenges:

• The team defines core hours from 2 PM to 5 PM GMT for live discussions.
• They use recorded updates and asynchronous discussions for the remaining work.

2.7.2 Dealing with Low Team Engagement

Low engagement can result in missed deadlines, poor collaboration, and reduced motivation.

Signs of Low Engagement

• Team members rarely contribute in Scrum events.
• Developers avoid discussions and work in isolation.
• The team frequently misses Sprint Goals.
• Retrospective action items are ignored.

How the Scrum Master Improves Engagement

Problem	Solution
Lack of ownership	Encourage team-driven decision-making.
Unclear goals	Align work with product vision.
Low motivation	Celebrate team successes.
No time for learning	Allocate learning and innovation time.

Example: Increasing Engagement

A team stops actively participating in Sprint Retrospectives.

• The Scrum Master introduces creative retrospective formats (e.g., Start/Stop/Continue).
• The team now shares feedback more openly, leading to real process improvements.

2.7.3 Handling Cross-Team Dependencies

When multiple Scrum teams work on the same product, dependencies can slow progress and cause misalignment.

Challenges of Cross-Team Work

• Conflicting priorities – Teams may focus on different goals.
• Integration issues – Work delivered by one team may not fit another team's needs.
• Delays due to dependencies – One team may be blocked waiting for another team.

Techniques for Cross-Team Collaboration

Challenge	Solution
Managing dependencies	Use Scrum of Scrums to identify and resolve blockers early.
Aligning priorities	Synchronize Sprint Goals across teams.
Avoiding integration issues	Use continuous integration and automated testing.

Example: Handling Dependencies

• Team A develops the authentication system.
• Team B builds the dashboard.
• Team C handles payment processing.

To ensure alignment, the teams hold a Scrum of Scrums every Monday and Thursday to resolve integration issues before they impact delivery.

2.8 Scaling Agile Teams

When an organization grows, Scrum needs to scale to support multiple teams working on the same product or initiative. Several frameworks help coordinate multiple Scrum teams while preserving agility.

2.8.1 When to Scale Scrum?

Scrum works best in small teams (5-9 people). However, organizations may need to scale Scrum when:

• Multiple teams are working on the same product.
• A single Scrum team cannot handle the complexity.
• Dependencies between teams cause delays.

Not all organizations need scaling frameworks—sometimes, improving team collaboration is enough.

2.8.2 Popular Scaling Frameworks

Framework	Key Features
LeSS (Large-Scale Scrum)	Minimalist approach, emphasizes simplicity and team autonomy.
SAFe (Scaled Agile Framework)	Provides structure for enterprise-wide agility, includes PI Planning.
Scrum@Scale	Uses interconnected Scrum teams for complex projects.

Example: When to Choose LeSS vs. SAFe

• A tech startup with 3 Scrum teams adopts LeSS to remain flexible.
• A large bank with 20 teams uses SAFe to manage regulatory requirements.

2.8.3 How Scrum Masters Support Scaling

When scaling Scrum, Scrum Masters play a critical role in ensuring that teams remain aligned and Agile.

Key Responsibilities of the Scrum Master in Scaling

1. Facilitating cross-team collaboration – Organizing Scrum of Scrums.
2. Ensuring alignment with product vision – Encouraging shared goals.
3. Helping teams remain Agile – Preventing excessive processes from slowing teams down.

Example: Supporting Scaling in a Large Organization

A telecom company introduces SAFe to manage 15 Scrum teams.

• The Scrum Masters align Sprint Goals across teams.
• A Program Increment (PI) Planning event helps prioritize work across teams.
• Teams use Automated Integration Testing to detect cross-team issues early.

Developing People and Teams (Additional Content)

1. Extending the Scrum Master’s Influence Beyond the Team

Navigating Organizational Barriers

Scrum Masters must recognize that team issues often stem from systemic organizational dysfunctions, such as:

• Functional silos (e.g., separate QA, Dev, Ops departments).

• Budgeting processes that favor upfront scope commitments.

• Inflexible HR/performance policies that reward individual output over team collaboration.

Scrum Master’s Organizational Leverage

• Influence change through transparency: Share data from Sprint Reviews and Retrospectives with leaders.

• Facilitate system-level conversations: Organize cross-functional improvement workshops.

• Challenge legacy structures: Raise impediments caused by rigid structures to agile champions or leadership.

Example:
If QA is not integrated with the Development Team, the Scrum Master can advocate for cross-functional teams, presenting data on delays caused by handoffs.

2. Strengthening Collaboration Between Scrum Master and Product Owner

Aligning Goals and Backlog Health

The Scrum Master and Product Owner have complementary responsibilities. However, misalignment often causes:

• Sprint Goals lacking focus or clarity.

• A backlog that reflects stakeholder noise rather than product vision.

• Conflicts over “business vs. technical priorities.”

Collaboration Tactics

• Sprint Goal Workshops: Co-facilitate goal-setting aligned with value and technical feasibility.

• Backlog Health Reviews: Regularly inspect backlog clarity, DoR adherence, and prioritization logic.

• Conflict Coaching: Mediate when PO decisions are resisted by Developers due to technical constraints.

Example:
A Product Owner keeps pushing for flashy features. The Scrum Master introduces customer feedback data and helps reframe backlog priorities based on value, not opinion.

3. Using Failure Cases to Develop Critical Thinking

Scrum Masters are often evaluated by how they respond to dysfunction, not just how they promote best practices. Failure patterns are great coaching moments.

3.1 Example Failure: Team Lacks Ownership

Symptoms:

• Team waits for task assignments from the PO.

• Retrospectives are superficial or skipped.

• Velocity stagnates or fluctuates wildly.

Scrum Master Interventions:

• Run a self-organization workshop to reintroduce Scrum values.

• Introduce task board ownership exercises (e.g., letting the team rewrite the Sprint Backlog).

• Coach PO to stop micromanaging “how” work is done.

3.2 Example Failure: Blame Culture

Symptoms:

• Developers avoid reporting blockers.

• Mistakes are hidden.

• Retrospectives turn into finger-pointing sessions.

Scrum Master Interventions:

• Facilitate a blameless Retrospective using the “What/So What/Now What” method.

• Model vulnerability by acknowledging your own coaching mistakes.

• Introduce the Five Dysfunctions of a Team model to open up trust discussions.

4. Deepening Scaling Awareness: SAFe vs. Scrum@Scale

Scaling Scrum is not simply applying Scrum to more teams—it involves trade-offs in autonomy, coordination, and structure.

4.1 Scrum@Scale

• Lightweight, modular.

• Promotes Decentralized decision-making through MetaScrums and Executive Action Teams.

• Better for startup environments or adaptive cultures.

4.2 SAFe (Scaled Agile Framework)

• Structured, enterprise-aligned.

• Supports Portfolio-level governance, budgeting, and architecture roles.

• Better suited for regulated or legacy-heavy organizations.

Scrum Master Role Differences:

Aspect	Scrum@Scale	SAFe
Decision-making	Local team-driven	Often centralized in ARTs (Agile Release Trains)
Coach focus	System-wide	Team + Release Train Engineer
Planning cadence	Sprint-based	Includes Program Increments (8–12 weeks)

5. Introducing Coaching Frameworks (GROW, ORID)

PSM III often involves explaining how you coach others, not just what Scrum says.

5.1 GROW Coaching Model

Phase	Description	Example
G – Goal	What do you want to achieve?	“We want to improve backlog refinement effectiveness.”
R – Reality	What’s happening now?	“Most PBIs are unclear during Sprint Planning.”
O – Options	What could we do?	“Split stories, add DoR, pair refinement.”
W – Way Forward	What will you do?	“Adopt INVEST + create checklist for next refinement.”

5.2 ORID Facilitation Model (for discussions & retros)

Stage	Purpose	Sample Questions
O – Objective	Facts, data	“What did we deliver last Sprint?”
R – Reflective	Feelings, reactions	“What frustrated or excited you?”
I – Interpretive	Meaning, root cause	“Why did this issue occur?”
D – Decisional	Commitment to act	“What should we do differently next time?”

Using these models allows the Scrum Master to structure conversations without dominating them, encouraging team ownership of solutions.

Conclusion

To succeed in PSM III and real-world leadership roles, a Scrum Master must be able to:

• See the system, not just the team.

• Collaborate laterally and upward, not just coach down.

• Think critically about failure and dysfunction.

• Communicate frameworks and principles clearly under pressure.