PSM II Developing People and Teams

Developing People and Teams Detailed Explanation

Scrum is built upon the foundation of high-performing, self-organizing teams. A Scrum Team works collaboratively, shares responsibilities, and continuously improves to deliver value effectively. The Scrum Master plays a crucial role in developing people and teams by fostering collaboration, improving team dynamics, and coaching individuals to become more effective in an Agile environment.

This section covers team development in Scrum, including:

• The characteristics of a high-performing team.
• The Scrum Master’s role in building and supporting a strong team.
• Coaching and facilitation techniques.
• Conflict resolution and team development stages.
• Measuring team performance and scaling Scrum Teams in large organizations.

2.1 Characteristics of a High-Performing Scrum Team

A successful Scrum Team demonstrates several key characteristics that allow it to be efficient, collaborative, and resilient.

1. Self-Organization

• Definition:

  • The team takes ownership of their work and does not rely on a manager to assign tasks or make decisions for them.
  • Decision-making is distributed across the team rather than controlled by a single leader.

• Why It Matters in Scrum:

  • Scrum is designed for self-organizing teams, meaning they decide how to do the work themselves rather than waiting for instructions.
  • This creates accountability and motivation, making the team more effective.

• Example:

  • Instead of a manager assigning work, the Developers select tasks from the Sprint Backlog and decide the best way to complete them.

2. Cross-Functionality

• Definition:

  • The team possesses all necessary skills to deliver a Done Increment by the end of each Sprint.
  • Each team member contributes beyond their primary expertise when necessary.

• Why It Matters in Scrum:

  • A cross-functional team can deliver a working product without depending on external teams.
  • It reduces bottlenecks and improves efficiency.

• Example:

  • A developer helps test a feature because the dedicated tester is overloaded.
  • A UI/UX designer collaborates with the developers to ensure a smooth user experience.

3. Collaboration and Shared Responsibility

• Definition:

  • The team works together to achieve the Sprint Goal rather than focusing only on individual assignments.
  • The principle of "we succeed together, we fail together" applies.

• Why It Matters in Scrum:

  • Encourages teamwork over individual contributions.
  • Prevents knowledge silos, ensuring that work does not stop if a specific team member is unavailable.

• Example:

  • If a developer is struggling with a bug, another developer offers help, even if it's not their task.

4. Continuous Learning and Adaptation

• Definition:

  • The team embraces continuous improvement through Sprint Retrospectives and feedback loops.
  • Team members are open to new ideas and willing to experiment with different approaches.

• Why It Matters in Scrum:

  • Scrum is an iterative framework, meaning teams must adapt to changes and learn from mistakes.
  • Continuous improvement ensures that processes evolve, leading to higher efficiency.

• Example:

  • After noticing poor Sprint Review feedback, the team modifies their development process to improve feature quality.

5. Psychological Safety

• Definition:

  • The environment allows individuals to express opinions, admit mistakes, and take calculated risks.
  • The team fosters an open culture where members feel comfortable challenging each other constructively.

• Why It Matters in Scrum:

  • If team members fear making mistakes, they may hide problems, avoid taking risks, or not speak up.
  • Psychological safety promotes honest communication and creative problem-solving.

• Example:

  • A team member admits, "I misunderstood the requirement. Let's fix it together," rather than hiding the mistake.

2.2 The Role of the Scrum Master in Team Development

The Scrum Master is a Servant Leader who supports the team’s growth, ensures smooth collaboration, and helps remove barriers to high performance.

Scrum Master's Focus Area	Key Actions
Building Self-Organizing Teams	Encourage teams to make decisions without waiting for external authority.
Facilitating Collaboration	Use coaching techniques to strengthen teamwork and communication.
Guiding Continuous Improvement	Promote inspection and adaptation in every Sprint Retrospective.
Removing Impediments	Identify and eliminate obstacles that prevent the team from performing effectively.
Promoting Agile Mindset	Educate teams on Agile principles and ensure that they practice Scrum effectively.

Example:

• A Scrum Master notices that a team relies too much on the Product Owner for technical decisions.
• Instead of answering every question, they encourage the Developers to collaborate and decide on a solution themselves.

2.3 Coaching and Facilitation in Scrum

Scrum Masters coach and facilitate rather than dictate. Knowing when to coach and when to facilitate is crucial.

2.3.1 Coaching Techniques

Coaching in Scrum is about helping teams discover solutions rather than giving direct answers.

Coaching Technique	How It Works
Powerful Questions	Ask thought-provoking questions instead of providing direct solutions.
Active Listening	Repeat back what the team says to confirm understanding.
Encouraging Self-Reflection	Help team members assess their own performance.

Example of Powerful Questions:

• "What do you think is preventing the team from achieving its goal?"
• "How can we make this process more efficient?"
• "What would you do differently next time?"

2.3.2 Facilitation Techniques

Facilitation is about guiding discussions to reach consensus and drive productive conversations.

Facilitation Technique	How It Helps
Liberating Structures	Techniques like 1-2-4-All and Troika Consulting help teams collaborate effectively.
Silent Brainstorming	Allows team members to contribute ideas without bias.
Dot Voting	Helps prioritize solutions democratically.

Example:

• Instead of one person dominating Sprint Retrospective discussions, the Scrum Master introduces silent brainstorming, allowing everyone to write down improvement ideas before discussion.

2.4 Conflict Resolution in Agile Teams

In any team environment, conflicts are natural and often arise due to differences in priorities, perspectives, or misunderstandings. In Scrum, conflict is not necessarily bad—it can lead to better ideas, improved collaboration, and stronger teams. However, unresolved or poorly managed conflict can create tension, reduce productivity, and damage trust.

A Scrum Master’s role is to help the team handle conflicts constructively while ensuring psychological safety and continuous improvement.

2.4.1 Common Causes of Conflict in Scrum Teams

Cause	Description	Example
Lack of Shared Understanding	Team members have different interpretations of requirements or priorities.	Developers disagree on how to implement a new feature due to vague acceptance criteria.
Unclear Roles & Responsibilities	Team members don’t understand their specific contributions.	The Product Owner starts assigning tasks instead of allowing the team to self-organize.
Differences in Working Styles	Individuals prefer different approaches to collaboration and execution.	One team member prefers detailed documentation, while another prefers informal discussions.
Stakeholder Interference	Business leaders push priorities that disrupt the team’s Sprint commitment.	A manager demands a new feature in the middle of the Sprint.
Technical Disagreements	Developers have different opinions on the best tools or architecture.	One developer prefers a new programming framework, while others want to maintain existing code.

2.4.2 Strategies for Managing Conflict

A Scrum Master should not eliminate all conflict but help teams handle disagreements constructively.

Conflict Level	Resolution Approach
Minor Disagreements	Encourage open discussion, active listening, and compromise.
Misalignment on Process	Refer to the Scrum Guide and facilitate a discussion to align on expectations.
Interpersonal Conflicts	Use mediation techniques to ensure both sides feel heard and respected.
High-Level Conflict (e.g., PO vs. Developers)	Bring in leadership or an Agile Coach to mediate.

2.4.3 Nonviolent Communication (NVC) in Scrum

Nonviolent Communication (NVC) is a structured method to express concerns without blaming others. It helps teams navigate difficult conversations productively.

The Four-Step NVC Process

1. Observation – Describe the issue without judgment.

   • Instead of: "You never involve me in Sprint Planning!"
   • Say: "I noticed that I wasn’t included in the last two Sprint Planning meetings."

2. Feelings – Express how the issue makes the person feel.

   • "This made me feel left out and unsure about our Sprint priorities."

3. Needs – Explain the underlying need that is not being met.

   • "I need to be included so I can contribute effectively and ensure my work aligns with the Sprint Goal."

4. Request – Make a clear and actionable request.

   • "Can we make sure that everyone is invited to Sprint Planning?"

Example of Applying NVC in Scrum:

Traditional Communication	NVC Approach
"You always reject my ideas!"	"In the last two discussions, my ideas weren’t considered. I feel discouraged because I want to contribute. Can we explore how we evaluate all suggestions?"

A Scrum Master should encourage NVC so that discussions remain solution-oriented instead of blame-focused.

2.5 Team Development Stages (Tuckman Model)

Scrum teams evolve through different stages before becoming high-performing. Understanding these stages helps Scrum Masters guide their teams effectively.

Stage	Characteristics	Scrum Master’s Role
Forming	Team members are new, uncertain about roles. Collaboration is low.	Provide guidance, set expectations, and facilitate team bonding.
Storming	Conflicts arise due to different working styles.	Mediate disagreements, encourage open discussions, and reinforce Scrum values.
Norming	The team finds common ground and works more smoothly.	Reinforce best practices and encourage feedback.
Performing	The team is highly effective, self-organizing, and productive.	Empower the team, remove impediments, and sustain high performance.

Example:

• A newly formed Scrum Team (Forming Stage) may rely heavily on the Scrum Master for decisions.
• In the Storming Stage, they disagree on how to estimate backlog items.
• By Norming, they find a consistent approach for estimation.
• By the Performing Stage, they manage their work with minimal intervention from the Scrum Master.

A Scrum Master should identify the current stage and adjust their approach accordingly.

2.6 Measuring Team Performance in Agile

Traditional performance metrics focus on individual productivity (e.g., lines of code written, hours worked). However, in Scrum, we measure team performance based on outcomes.

2.6.1 Effective Scrum Metrics

Metric	What It Measures	Why It Matters
Sprint Goal Achievement Rate	How often the team achieves its Sprint Goal.	Ensures the team is focused on delivering value.
Lead Time	Time from idea to delivery.	Helps optimize time-to-market.
Cycle Time	Average time taken to complete a single work item.	Identifies bottlenecks in development.
Team Happiness Index	Measures team morale.	Helps detect burnout or dissatisfaction.
Escaped Defects	Number of bugs found in production.	Ensures quality control.

2.6.2 Metrics to Avoid

Bad Metric	Why It’s Problematic
Story Points Per Sprint	Leads to gaming the system instead of focusing on real value.
Number of Bugs Fixed	Encourages rushing instead of improving development quality.
Velocity Comparisons Across Teams	Every team is different, so comparing velocity is misleading.

A Scrum Master should help teams focus on value-driven metrics rather than vanity metrics.

2.7 Scaling Scrum Teams in Large Organizations

In large organizations, multiple Scrum Teams often work together. Scaling frameworks provide structured ways to coordinate work across teams.

2.7.1 Common Scaling Frameworks

Framework	Key Features
LeSS (Large Scale Scrum)	Focuses on simplicity, keeping Scrum lightweight across multiple teams.
Nexus	Introduces a Nexus Integration Team to coordinate work across teams.
SAFe (Scaled Agile Framework)	Adds roles, planning layers, and coordination events for enterprise agility.

2.7.2 Challenges in Scaling Scrum

Challenge	Solution
Dependencies Between Teams	Implement cross-team refinement and Scrum of Scrums meetings.
Misalignment of Priorities	Use a shared Product Backlog and regular synchronization.
Too Many Coordination Meetings	Keep only essential events and avoid bureaucracy.

A Scrum Master working in a scaled environment must:

• Ensure alignment between teams.
• Prevent dependencies from blocking progress.
• Facilitate cross-team collaboration.

2.8 Building a Culture of Continuous Improvement

Continuous improvement is at the heart of Scrum. A high-performing team does not settle for "good enough"—it constantly seeks ways to improve its processes, collaboration, and product quality.

A Scrum Master must encourage teams to inspect and adapt frequently, promoting a culture where feedback is valued and experiments are encouraged.

2.8.1 Key Practices for Continuous Improvement

Practice	Description	Example
Sprint Retrospectives	Reflect on what went well and what can be improved.	After each Sprint, the team identifies at least one actionable improvement.
Kaizen Mindset	Encourage small, incremental improvements.	Instead of a complete overhaul, the team improves one process at a time.
Fail Fast, Learn Fast	Promote a safe environment where mistakes lead to learning.	A team experiments with a new deployment process, learns from failure, and improves.
Data-Driven Decisions	Use metrics to track progress and improvements.	The team measures Cycle Time to reduce bottlenecks in the workflow.

2.8.2 Encouraging Experimentation in Scrum Teams

A Scrum Master should help teams move away from fear of failure by encouraging safe-to-fail experiments.

Examples of Encouraging Experimentation:

• Technical Experimentation: Trying new development frameworks or tools in a controlled environment.
• Process Experimentation: Running a Kanban-Scrum hybrid for one Sprint to test efficiency.
• Collaboration Experimentation: Using pair programming to see if it improves code quality.

2.9 Handling Resistance to Agile Transformation

Adopting Scrum often challenges traditional ways of working, and resistance is common. Resistance can come from:

1. Developers – Fear of change or misunderstanding Scrum’s purpose.
2. Product Owners – Hesitation in embracing iterative planning and flexibility.
3. Managers & Executives – Fear of losing control due to self-managing teams.

Types of Resistance and How to Address Them

Type of Resistance	Typical Behavior	How to Overcome It
Passive Resistance	Avoiding discussions about Agile, refusing to engage.	Involve them in Agile events, show success stories.
Active Resistance	Complaining, arguing against Scrum practices.	Address concerns openly, provide Agile coaching.
Lack of Understanding	Misinterpreting Scrum as a rigid set of rules.	Conduct workshops, clarify why Agile is valuable.
Micromanagement Culture	Managers resist self-organizing teams.	Educate leadership on Servant Leadership and Agile roles.

2.10 Best Practices for Leading Agile Change

2.10.1 Key Principles for Agile Leadership

Principle	What It Means	How It Applies in Scrum
Servant Leadership	Leaders support the team rather than controlling it.	The Scrum Master removes impediments rather than assigning tasks.
Outcome Over Output	Success is measured by value delivered, not just tasks completed.	Focus on business impact rather than the number of completed story points.
Empowerment	Trust teams to make decisions.	Developers choose how to build a feature rather than following orders.
Transparency	Open communication and trust.	The Product Backlog is visible to all stakeholders at all times.

2.10.2 Strategies for Leading Agile Transformation

Strategy	How It Works	Example
Start with a Pilot Team	Test Agile with one team before scaling.	Run Scrum in one department before organization-wide adoption.
Show Quick Wins	Deliver small successes to build trust.	Release a small feature quickly to demonstrate Agile value.
Engage Leadership Early	Gain executive support for Agile.	Invite managers to Sprint Reviews so they see progress.
Train and Mentor Teams	Educate teams on Agile best practices.	Offer Scrum training sessions for teams new to Agile.

2.11 Supporting Leadership in an Agile Organization

Scrum Masters play a key role in helping leaders understand Agile and transition to Agile-friendly leadership styles.

2.11.1 Common Leadership Challenges in Agile Transformation

Challenge	Traditional Leadership Approach	Agile Leadership Approach
Command & Control	Managers make all decisions, teams follow orders.	Leaders guide teams rather than control them.
Measuring Success by Hours Worked	Success is based on employee hours.	Success is measured by value delivered.
Risk Avoidance	Focus on detailed upfront planning to prevent failure.	Accept short-term failures to drive long-term learning.

2.11.2 The Scrum Master’s Role in Agile Leadership Development

1. Educate Leaders on Agile Principles
   • Organize workshops to explain Agile Mindset to leadership teams.
2. Encourage Outcome-Based Thinking
   • Help leaders focus on value delivered, not just effort spent.
3. Introduce Agile Metrics for Leadership
   • Use Lead Time, Customer Feedback, and Business Outcomes instead of effort-based metrics.
4. Promote a Safe-to-Fail Culture
   • Help leaders understand that small failures lead to bigger learning.

Developing People and Teams (Additional Content)

1. Evaluative Thinking and Judgment Skills in Team Development Scenarios

PSM II-style questions often require you to evaluate nuanced team situations, especially around team maturity and conflict. These are not about knowing facts, but about making the best professional judgment, often in line with Scrum values and the Servant Leadership model.

1.1 Intervention During the Storming Stage – Yes or No?

The Storming stage (from the Tuckman model) is characterized by conflict, uncertainty, and power struggles.

Typical Exam Question:

A Scrum Team in the Storming stage has frequent disagreements and lacks focus. Should the Scrum Master intervene?

Judgment Strategy:

Ask:

• Will the intervention preserve or hinder self-management?

• Will the team learn from the conflict or become dysfunctional?

Best Practice:

• The Scrum Master should intervene, but not to control.

• Their role is to facilitate conversations, coach in conflict resolution, and create psychological safety.

Wrong Approaches (trap answers in the exam):

• Avoiding intervention completely (interpreted as “let them learn on their own”)

• Solving problems directly for the team (anti-pattern of servant leadership)

Correct approach in line with PSM II expectations:

"Guide the team to resolve their own conflicts by coaching communication and reinforcing Scrum values."

2. Mapping Concepts to the Scrum Guide

To avoid traps in PSM II, it's important to connect team behaviors and Scrum Master actions directly to the Scrum Guide. Let’s explore two key examples:

2.1 Scrum Values and Team Dynamics

Scrum Value	Behavioral Reflection in Teams	Scrum Master’s Role
Courage	Team members speak up about risks or poor practices	Create safety for honesty
Respect	Junior and senior members support each other	Model inclusive behavior
Commitment	Team aligns on Sprint Goal and follows through	Reinforce Sprint purpose
Focus	Avoids unnecessary WIP and distractions	Protect the team from interruptions
Openness	Shares progress and setbacks honestly	Facilitate transparent discussions

PSM II Question Trap Example:
A developer hides a blocker to avoid delaying the Sprint Goal. Is this a problem? Yes. It violates Openness and undermines Inspection and Adaptation.

2.2 Servant Leadership — What It Is and Isn’t

Is Servant Leadership	Is NOT
Coaching and asking open questions	Assigning tasks
Removing impediments with team input	Making technical decisions alone
Promoting learning and experimentation	Avoiding conflict for harmony
Modeling Agile values	Enforcing process compliance

In PSM II, Servant Leadership is NOT passive — it's proactive facilitation.

3. Identifying "Pseudo-High Performance Teams"

Many teams may appear “high-performing” on the surface but lack true agility. This is a frequent exam scenario designed to test your understanding of psychological safety, collaboration, and empiricism.

3.1 Common Symptoms of Pseudo-High Performance

Symptom	Why It’s a Problem
Lack of healthy conflict	Suppression leads to stagnation, innovation loss
Always agreeing instantly	Suggests fear of disagreement or groupthink
Over-reliance on Scrum Master	Not truly self-organizing
Obsessive adherence to velocity or metrics	Focus on output over value
Avoiding Retrospective improvements	Indicates complacency or fear of change

3.2 Scrum Master’s Response to Surface-Level Performance

• Introduce techniques like silent brainstorming to draw out hidden feedback.

• Ask powerful questions, such as:

  • "What’s one thing we’re not talking about but should?"

  • "What would you challenge if there were no consequences?"

• Observe meeting dynamics:

  • Who speaks?

  • Who remains silent?

  • Are people simply “reporting status” or discussing value?

3.3 Exam Strategy for These Scenarios

If a team seems “too perfect,” ask:

• Is transparency really happening?

• Are difficult conversations being avoided?

• Is the team truly self-managing?

Right Answer Pattern:
Choose the option where the Scrum Master challenges the team constructively, opens up space for reflection, or asks them to inspect their assumptions.

Summary Table

Focus Area	Scrum-Aligned Action
Conflict in Storming Stage	Facilitate, don’t solve — enable healthy dialogue
Scrum Values in Practice	Tie every behavioral issue back to a specific value
Servant Leadership	Empower, support, and remove blockers — don’t dictate
Fake High-Performance	Look beyond harmony — promote inspection, feedback, challenge
Exam Answer Strategy	Filter each choice by: Empiricism, Self-Management, Scrum Values, Servant Leadership