PadhaikoAll subjects

Agile Roles, Behaviors, and Team Dynamics

Agile Methodologies (ENCT 465)

Open in the Padhaiko app

4.1 Establishing Agile Roles: Responsibilities of Product Owner, Team Member, and Scrum Master

Agile replaces traditional top-down job hierarchies ("Project Manager assigns tasks to coders and testers") with three clear, balanced accountabilities: Product Owner (owns what maximizes value), Team Member / Developers (owns how to build and verify quality), and Scrum Master (owns process health and impediment removal). Separating these accountabilities prevents any single person from sacrificing product quality for schedule pressure or ignoring business priorities for technical preferences.

Definition

The Three Core Agile Roles

  1. Product Owner (PO): The single voice of product value and business priorities. Accountable for crafting the Product Goal, managing and ordering the Product Backlog, clarifying requirements, and accepting or rejecting completed increments against business intent.
  2. Team Member (Developers): The cross-functional group of builders (engineers, testers, UX designers, database specialists, DevOps) who collectively own creating a shippable Increment every Sprint. They estimate work, self-organize task execution, and uphold the Definition of Done.
  3. Scrum Master (SM): The servant-leader and Agile coach accountable for establishing Scrum/Agile practices, facilitating events when needed, protecting the team from external distractions, and removing systemic organizational impediments.

4.1.1 Detailed Responsibilities and Boundaries

Core Responsibilities and Decision Boundaries of Agile Roles
RoleCore ResponsibilitiesDecisions OwnedWhat This Role Does NOT Do
Product OwnerDefine Product Vision & Goal; write and refine backlog items; prioritize by ROI, risk, and dependencies; liaise with stakeholders; review Increments.What gets built and in what order; release timing and scope trade-offs.Does not assign tasks to individual developers or dictate internal code architecture.
Team Member (Developers)Break backlog items into daily tasks; estimate story sizes; design, code, test, integrate, and document; maintain the Sprint Backlog; improve craft.How work is engineered; how much work fits safely in a Sprint; technical design choices.Does not change Sprint priorities unilaterally without consulting the Product Owner.
Scrum MasterCoach team and organization on empiricism; facilitate Sprint events; resolve cross-team blockers; shield team from mid-sprint scope disruption.Process coaching improvements and facilitation structures.Does not act as a boss, task dispatcher, or personal secretary taking notes for the team.

4.2 Stakeholders and Agile Mentors: Their role in the product team

An Agile team does not work in a vacuum. Beyond the core delivery trio sit Stakeholders (those who fund, use, regulate, or support the product) and Agile Mentors / Coaches (experienced guides who accelerate team maturity).

Definition

Stakeholders and Agile Mentors

4.2.1 How Stakeholders Participate Effectively

In Waterfall projects, stakeholders sign off requirements at Month 1 and disappear until User Acceptance Testing at Month 9. In Agile, stakeholder engagement is continuous yet structured so the team is informed without being disrupted mid-sprint:

Key Stakeholder Groups and Agile Touchpoints
Stakeholder GroupWhat They ContributePrimary Agile Touchpoints
Customers & End UsersReal workflow pain points, usability feedback, feature validation.Sprint Reviews, user interviews, beta/MVP usability tests.
Executive SponsorsStrategic funding, business constraints, organizational alignment.Product Vision alignment, Release Planning, Sprint Reviews.
Operations, Security & LegalCompliance rules, deployment readiness, SLAs, data privacy constraints.Definition of Done criteria, Backlog Refinement, Release Readiness.
Subject Matter Experts (SMEs)Specialized domain logic (e.g., banking tax rules, medical protocols).Just-in-time Backlog Refinement and Story workshops with the PO.

4.2.2 Role of the Agile Mentor


4.3 Key Agile Behaviors: Commitment, focus, openness, respect, and courage

Processes and tools fail if team behaviors remain defensive, secretive, or fearful. Scrum and Agile culture rest on five core values/behaviors—Commitment, Focus, Openness, Respect, and Courage—that make empiricism psychologically safe and effective.

Definition

The Five Key Agile Behaviors (Scrum Values)

  1. Commitment: Team members dedicate themselves to achieving the team's shared Sprint Goal and supporting one another—not blindly promising fixed future scope under impossible pressure, but committing to professionalism, quality, and shared goals.
  2. Focus: Concentrating team energy on the current Sprint Goal and finishing started items before pulling new work, minimizing multitasking and distractions.
  3. Openness: Being honest and transparent about progress, technical debt, missed estimates, and blockers so problems surface early when they are cheap to fix.
  4. Respect: Treating every teammate, Product Owner, and stakeholder as a capable, well-intentioned professional—valuing diverse perspectives and constructive disagreement.
  5. Courage: Doing the right thing even when uncomfortable—raising bad news early, pushing back on unrealistic deadlines or quality shortcuts, refactoring messy code, and admitting "I don't know; I need help."

4.3.1 Healthy Behaviors vs. Anti-Patterns

Agile Behaviors in Daily Action vs. Anti-Patterns
BehaviorHealthy Agile ActionCommon Anti-Pattern
CommitmentDevelopers swarm on the last unfinished story on Day 8 so the Sprint Goal succeeds.Each person finishes "their own ticket" and ignores the rest of the Sprint Backlog.
FocusTeam enforces WIP limits and defers unrelated ad-hoc requests to the Product Backlog.Team juggles 4 side-projects and leaves 6 half-done stories at Sprint end.
OpennessA developer flags a major API blocker on Day 2 in Daily Scrum.Developer says "90% done, all good" for 5 days out of fear of blame.
RespectJunior tester questions an architect's assumption in Refinement and is heard seriously.Senior engineers dismiss UX or QA concerns as "non-technical noise."
CourageTeam refuses to ship unverified code just to hit a demo date, protecting the DoD.Team disables failing automated tests to force a green build before release.

4.4 Team Philosophy: Dedicated teams, cross-functionality, and self-organization

Traditional organizations group specialists into functional silos (a Frontend department, a Backend department, a QA department) and split individuals across multiple projects simultaneously. Agile team philosophy replaces that model with dedicated, cross-functional, and self-organizing product teams.

Definition

Three Pillars of Agile Team Philosophy

  1. Dedicated Teams: Team members are assigned 100% to one product team rather than fractionalized across two or three concurrent projects. Keeping work flowing to a stable team eliminates context-switching waste and preserves deep domain memory.
  2. Cross-Functionality: The team collectively holds all skills needed to turn a Product Backlog item into a tested, potentially shippable Increment (analysis, UI/UX, coding, testing, integration, deployment)—requiring zero external handoffs inside a Sprint.
  3. Self-Organization (Self-Management): The team itself decides who does what, when, and how to accomplish the Sprint Goal, rather than waiting for a project manager to assign daily tasks.

4.4.1 Why Dedicated Teams Beat Multi-Project Splitting

When a developer is split across multiple teams or projects, every switch forces mental reloading of codebases, meetings, and priorities. Empirical industry models (such as Gerald Weinberg's context-switching rule) show how rapidly productive capacity collapses as concurrent project count rises:

Weinberg's Context-Switching Penalty on Productive Time
Concurrent Projects AssignedProductive Time per ProjectContext-Switching Overhead LostNet Productive Capacity
1 (Dedicated)100%0%100%
2 Projects40% each20%80%
3 Projects20% each40%60%
4 Projects10% each60%40%

4.4.2 Cross-Functionality, T-Shaped Skills, and Optimal Team Size

4.4.3 Guardrails of Self-Organization

Self-organization does not mean "no rules" or "everyone does whatever they feel like." It means autonomy within clear boundaries:


4.5 Team Development Phases: Forming, Storming, Norming, Performing, and Adjourning

Even with the right roles and skills, a newly assembled team does not operate at peak velocity on Day 1. Psychologist Bruce Tuckman (1965, expanded with Mary Ann Jensen in 1977) modeled five predictable stages every group passes through as people learn to trust one another and work together.

Definition

Tuckman's Five Stages of Team Development

  1. Forming: Team members come together, behave politely and cautiously, seek clarity on roles, goals, and ground rules, and depend heavily on leadership or the Scrum Master for structure.
  2. Storming: Real differences in working styles, technical opinions, and priorities surface. Conflicts, frustration, or resistance to Agile practices often appear, and apparent productivity may dip temporarily.
  3. Norming: The team resolves early friction, establishes shared working agreements, respects individual strengths, and develops psychological safety and predictable sprint rhythm.
  4. Performing: The team operates as a cohesive, high-trust, self-organizing unit—solving complex problems smoothly, swarming on bottlenecks, and achieving peak, sustainable velocity.
  5. Adjourning (Mourning): When a temporary initiative ends or major team membership changes, the group wraps up deliverables, documents lessons learned, celebrates achievements, and transitions—or re-enters Forming if new members join.
Leadership and Scrum Master Strategy Across Tuckman's Phases
PhaseObservable Team SignalsVelocity & Trust LevelBest Scrum Master / Coach Focus
1. FormingPolite meetings, unclear boundaries, waiting for direction, silent stand-ups.Low-to-moderate; guarded trustClarify Product Vision, Agile roles, and basic team Working Agreements; provide clear facilitation.
2. StormingDebates over coding standards, missed sprint forecasts, friction between roles.Volatile; testing boundariesCoach conflict resolution without taking sides; reinforce Respect & Openness; protect psychological safety.
3. NormingConstructive peer reviews, shared DoD ownership, open retrospectives.Rising and stabilizingStep back from heavy facilitation; encourage peer-led problem solving and cross-training.
4. PerformingSelf-correcting flow, seamless swarming, high empathy, proactive improvement.High and predictableFocus on organizational obstacles outside the team and continuous mastery/innovation.
5. AdjourningProject handoff or team reorganization; sense of loss or transition anxiety.Winding down / resettingRecognize contributions, capture retrospective learnings, and support smooth transition.

Example 4.1

4.1

An engineering director considers two ways to staff a complex product:

Using the pairwise communication channels formula C = n * (n - 1) / 2:

  1. Calculate the number of communication channels inside a 5-person team versus a 12-person team.
  2. Compute the ratio and percentage increase in communication channels when growing from 5 members to 12 members, and explain why Agile prefers small cross-functional teams.

Calculating Pairwise Communication Channels:

  • For a 5-person team (n = 5): C_5 = 5 * (5 - 1) / 2 = 20 / 2 = 10 communication channels.
  • For a 12-person team (n = 12): C_12 = 12 * (12 - 1) / 2 = 132 / 2 = 66 communication channels.

Ratio and Percentage Increase:

  • Ratio: 66 / 10 = 6.6 times as many channels.
  • Percentage increase: ((66 - 10) / 10) * 100 = 560.0% increase in communication overhead.
  • Agile insight: Small 5–9 person teams keep coordination lightweight (face-to-face alignment in 15-minute Daily Scrums), whereas 12+ person groups fragment into sub-teams and spend excessive time in status synchronization.
Answer:
  1. 5-person team: 10 communication channels; 12-person team: 66 communication channels.
  2. Increasing headcount from 5 to 12 creates 6.6 times as many channels (a 560.0% increase), which is why Agile caps teams at small sizes (typically 5–9 people) for high-bandwidth collaboration.
Example 4.2

4.2

A 5-developer team works a standard 40-hour week each (200 total nominal team hours per week). Compare their weekly net productive hours under two staffing policies using Weinberg's context-switching model:

  1. Dedicated Agile Team (1 project each): 100% productive capacity (0% context-switching loss).
  2. Matrixed Multi-Project Staffing (3 concurrent projects each): 20% productive capacity per project (60% net productive across the 3 projects, 40% lost to context switching).

Compute the net productive hours per week under each policy, the weekly hours lost to context switching, and the percentage of total team capacity wasted.

Dedicated Team Weekly Capacity (1 Project):

  • Total nominal hours = 5 * 40 = 200 hours/week.
  • At 100% effective focus, net productive hours = 200 * 1.00 = 200.0 hours/week.

Matrixed Staffing Capacity (3 Concurrent Projects):

  • Across 3 projects, each developer yields 3 * 20% = 60% net productive capacity and loses 40% to task switching.
  • Net productive hours across all 3 projects combined = 200 * 0.60 = 120.0 hours/week.
  • Hours lost every week = 200 - 120 = 80.0 hours/week (equivalent to losing 2 full-time developers!).
  • Percentage of capacity wasted = (80 / 200) * 100 = 40.0%.
Answer:
  • Dedicated Team: 200.0 productive hours/week (0 hours lost)
  • 3-Project Matrixed Team: 120.0 productive hours/week total across projects
  • Weekly Capacity Lost: 80.0 hours/week (40.0% of total team capacity wasted on context switching)
Example 4.3

4.3

Exam-Style Scenario Question: A newly formed 6-person Scrum team completed Sprint 1 smoothly and politely, but during Sprint 2 two senior engineers argued sharply in Sprint Planning over database vs. microservice design, the QA engineer felt excluded from architecture decisions, and the Product Owner bypassed the team to tell a junior developer directly to skip unit tests for an urgent executive demo. Identify the Tuckman stage, diagnose the role/behavior violations, and outline how the Scrum Master should respond.

1. Identifying the Tuckman Stage: The team has moved from polite Forming (Sprint 1) into Storming (Sprint 2), where technical disagreements, role friction, and stress-induced boundary violations emerge.

2. Diagnosing Role and Behavior Violations:

  • PO telling a junior developer to skip unit tests: Violates Developer ownership of how work is built and quality (DoD), plus the Agile values of Courage and Respect.
  • Excluding QA from architecture discussions: Violates Cross-functionality and Acting as a unified team.
  • Unresolved design conflict: Normal in Storming, requiring structured facilitation rather than avoidance.

3. Scrum Master Intervention Plan:

  1. Coach the PO privately: Remind the PO that they own what is prioritized, while Developers own how it is engineered and must never compromise the Definition of Done.
  2. Facilitate a Working Agreement workshop: Help the team agree on architecture decision norms (e.g., short technical spikes, inclusive design reviews with QA present) to guide them from Storming into Norming.
  3. Reinforce Psychological Safety & Behaviors: Model Respect and Openness in Retrospectives so constructive technical debate strengthens design rather than creating personal factions.
Answer:

The team is in Tuckman's Storming stage, compounded by a Product Owner overstepping into technical quality decisions and team silos excluding QA. The Scrum Master should protect the Definition of Done by coaching the PO on role boundaries, facilitate inclusive team Working Agreements to resolve design friction, and foster Respect and Courage to help the team transition into Norming.


Exercises

Practice Exercises — Agile Roles, Behaviors, and Team Dynamics

Question 1

Compare the responsibilities and authority boundaries of the Product Owner, Team Member (Developers), and Scrum Master, and explain why one individual should not combine the Product Owner and Scrum Master roles.

Role Responsibilities and Boundaries:

  • Product Owner: Maximizes product value, owns Product Goal and Product Backlog ordering, clarifies requirements, and collaborates with stakeholders. Does not micromanage tasks or technical design.
  • Team Members (Developers): Cross-functional builders who own Sprint Backlog execution, effort estimation, technical architecture, and meeting the Definition of Done.
  • Scrum Master: Servant-leader coaching the team and organization on Agile empiricism, facilitating events, and removing impediments without line-management authority.

Why PO and SM Should Remain Separate: The PO focuses on external business urgency ("what can we ship sooner?"), while the SM protects internal team health, empiricism, and sustainable pace ("are we compromising quality or hiding blockers?"). Merging them removes this essential check and balance.

Answer:

The PO owns what maximizes value, Developers own how to build shippable quality, and the Scrum Master coaches process health and removes blockers. Keeping PO and SM separate prevents business deadline pressure from overriding engineering sustainability and honest inspection.

Question 2

Explain the distinct contributions of Stakeholders and an Agile Mentor to a product team, and describe how a team prevents stakeholder involvement from turning into mid-sprint chaos.

Roles of Stakeholders and Agile Mentors:

  • Stakeholders (users, sponsors, ops, security, SMEs) bring business needs, domain rules, compliance constraints, and real-world feedback on working increments.
  • Agile Mentors coach team members, Scrum Masters, and leadership on Agile practices, mindset shifts, and continuous improvement while gradually transferring ownership to the team.

Preventing Mid-Sprint Disruption: All new stakeholder requests and priority shifts flow through the Product Owner into the Product Backlog, while formal increment inspection and feedback happen in scheduled Sprint Reviews and Backlog Refinement—protecting the team's Sprint Goal focus.

Answer:

Stakeholders supply domain expertise, business alignment, and increment feedback, whereas Agile Mentors guide the team's process maturity and self-correction. Routing requests through the Product Owner and centering feedback on Sprint Reviews prevents mid-sprint disruption.

Question 3

State the five key Agile behaviors (Commitment, Focus, Openness, Respect, Courage) and illustrate how a breakdown in any two of them damages empirical process control.

The Five Key Agile Behaviors:

  1. Commitment (to shared Sprint Goals and quality)
  2. Focus (finishing high-priority work before starting new tasks)
  3. Openness (honesty about progress and blockers)
  4. Respect (valuing teammates' skills and viewpoints)
  5. Courage (speaking up, challenging shortcuts, asking for help)

Impact of Breakdowns on Empiricism:

  • Loss of Openness: Developers hide delays or technical debt in Daily Scrums, destroying Transparency and delaying Adaptation until the sprint fails.
  • Loss of Courage: Team members stay silent when pressured to skip testing, eroding the Definition of Done and corrupting Inspection of real software readiness.
Answer:

The five behaviors are Commitment, Focus, Openness, Respect, and Courage. Without Openness, blockers remain hidden (breaking Transparency); without Courage, teams accept quality shortcuts (corrupting Inspection and Adaptation).

Question 4

Define dedicated teams, cross-functionality, and self-organization, and describe Tuckman's five team development phases explaining how a Scrum Master's support changes across them.

Three Pillars of Team Philosophy:

  • Dedicated teams: Members work 100% on one team to prevent context-switching loss.
  • Cross-functionality: The team holds all skills needed (UX, dev, QA, ops) to deliver Done increments independently.
  • Self-organization: The team decides internally how to break down and execute work within Sprint and DoD guardrails.

Tuckman's Five Phases and Shifting Support:

  1. Forming: Polite and uncertain -> SM provides structure, clear roles, and Working Agreements.
  2. Storming: Internal conflict and friction -> SM coaches healthy conflict resolution and psychological safety.
  3. Norming: Shared trust and rhythms -> SM steps back to let peer accountability grow.
  4. Performing: High-trust self-correction -> SM removes external organizational blockers.
  5. Adjourning: Wrap-up or reorganization -> SM facilitates knowledge capture and transition.
Answer:

Agile teams are dedicated (100% single-team focus), cross-functional (end-to-end delivery skills), and self-organizing (autonomous execution). Across Tuckman's Forming, Storming, Norming, Performing, and Adjourning phases, the Scrum Master shifts from active structuring and conflict coaching to light-touch systemic obstacle removal.

Question 5

An organization currently has an 8-person cross-functional team working 40 hours/week per person (320 nominal hours/week):

  1. Calculate the number of pairwise communication channels in the 8-person team. If management merges a second 6-person group into it to form a 14-person mega-team, how many communication channels exist, and how many extra channels are added?
  2. Separately, compare the 8-person team's weekly net productive hours when split across 2 concurrent projects (80% net productive capacity, 20% context-switching loss) versus 4 concurrent projects (40% net productive capacity, 60% context-switching loss). How many productive hours/week are lost by moving from 2 projects to 4 projects?

Part 1: Communication Channels (C = n * (n - 1) / 2):

  • 8-person team: C_8 = 8 * 7 / 2 = 28 channels.
  • 14-person mega-team: C_14 = 14 * 13 / 2 = 91 channels.
  • Extra channels added: 91 - 28 = 63 additional communication channels.

Part 2: Net Productive Hours Under Multi-Project Splitting: Total nominal hours = 8 * 40 = 320 hours/week.

  • At 2 projects (80% net capacity): 320 * 0.80 = 256.0 productive hours/week.
  • At 4 projects (40% net capacity): 320 * 0.40 = 128.0 productive hours/week.
  • Additional productive hours lost moving from 2 to 4 projects: 256.0 - 128.0 = 128.0 hours/week.
Answer:
  1. 8-person team: 28 channels; 14-person team: 91 channels (63 extra channels added).
  2. 2 projects: 256.0 productive hrs/week; 4 projects: 128.0 productive hrs/week (128.0 productive hrs/week lost by overloading to 4 projects).
← Agile ApproachesAgile Planning: Vision to Release →