Description

This curriculum engages learners in the same multi-faceted decision-making required in ongoing Agile advisory engagements, addressing real-time team governance, conflict mediation, and structural trade-offs across distributed and scaling environments.

Module 1: Defining Agile Team Structures and Roles

Selecting between dedicated cross-functional teams and shared-resource models based on project criticality and organizational constraints.
Resolving role ambiguity between Product Owner and Business Analyst in organizations with established waterfall governance.
Deciding whether to embed QA engineers full-time within teams or maintain a centralized testing function for compliance purposes.
Addressing dual reporting lines when team members report functionally to department managers and operationally to Scrum Masters.
Establishing decision rights for the Scrum Master in conflict resolution without overstepping functional management authority.
Adjusting team size when scaling beyond the standard 5–9 members due to system architecture or regulatory requirements.

Module 2: Establishing Team Norms and Psychological Safety

Facilitating team charters that define communication protocols, meeting attendance expectations, and escalation paths without creating bureaucratic overhead.
Intervening when dominant personalities suppress input during retrospectives, balancing participation without enforcing artificial turn-taking.
Handling disclosure of personal challenges during team check-ins while maintaining confidentiality and team cohesion.
Managing the tension between transparency and political sensitivity when documenting improvement actions from retrospectives.
Deciding whether to allow anonymous feedback in retrospectives when trust levels are low, and assessing long-term impacts on accountability.
Responding to repeated norm violations (e.g., missed stand-ups) with progressive accountability measures that don’t undermine team autonomy.

Module 3: Conflict Resolution and Decision-Making Protocols

Choosing between consensus, majority vote, or authority decision when technical disagreements stall sprint planning.
Mediating disputes between developers and product owners over scope changes mid-sprint without undermining Agile principles.
Documenting conflict outcomes to prevent recurrence while avoiding excessive process formalization.
Addressing passive-aggressive behavior during planning poker when team members consistently override estimates.
Introducing conflict resolution frameworks (e.g., nonviolent communication) without making sessions feel therapeutic or off-topic.
Escalating unresolved team conflicts to HR or leadership when psychological safety is compromised and internal mediation fails.

Module 4: Integrating Distributed and Hybrid Teams

Designing overlapping core hours for global teams while respecting local labor laws and work-life balance expectations.
Selecting collaboration tools (e.g., Miro, Jira, Teams) that support real-time collaboration without creating information silos.
Rotating meeting facilitation across time zones to distribute inconvenience and promote equity in participation.
Recreating informal “watercooler” interactions in virtual settings using structured social check-ins without wasting productive time.
Managing documentation rigor in hybrid teams to ensure remote members are not disadvantaged in information access.
Assessing the impact of asynchronous communication on decision latency and adjusting sprint length accordingly.

Module 5: Performance Evaluation and Accountability in Agile Contexts

Aligning individual performance reviews with team-based Agile outcomes without diluting personal accountability.
Defining measurable contributions for non-coding roles (e.g., UX, product ownership) in velocity-driven environments.
Handling underperformance in a team member when peer feedback is inconsistent or avoided due to team harmony concerns.
Integrating 360-degree feedback into Agile teams without creating fear of retribution or political maneuvering.
Deciding whether to publish team metrics (e.g., velocity, defect rates) organization-wide and managing gaming risks.
Negotiating bonus structures tied to team delivery when individual motivations vary across career stages.

Module 6: Scaling Team Dynamics Across Programs and Portfolios

Coordinating sprint rhythms across multiple teams when dependencies require synchronized delivery milestones.
Resolving priority conflicts between product owners in SAFe or LeSS environments during PI planning.
Appointing Scrum of Scrums facilitators who maintain neutrality while having sufficient technical credibility.
Managing knowledge silos when specialized teams (e.g., security, integration) become bottlenecks in delivery pipelines.
Standardizing definition of done across teams without suppressing context-specific quality requirements.
Handling resource contention when shared team members (e.g., architects) cannot meet cross-team commitments.

Module 7: Sustaining Team Health and Preventing Burnout

Monitoring sprint churn (e.g., story carryover, scope changes) as an early indicator of team overload or poor planning.
Intervening when teams consistently volunteer for excessive story points to appear high-performing.
Adjusting sprint length or workload after detecting signs of chronic overtime or missed personal commitments.
Revisiting team composition when prolonged collaboration leads to groupthink or innovation stagnation.
Managing stakeholder pressure to increase delivery pace without transparently discussing sustainability trade-offs.
Planning deliberate team downtime (e.g., innovation sprints, learning weeks) without being perceived as unproductive.

Module 8: Leading Agile Team Transitions and Change Management

Phasing out underperforming team members in a way that preserves team morale and adheres to labor regulations.
Introducing new members to established teams without disrupting existing workflows and social dynamics.
Managing resistance when transitioning from command-and-control leadership to servant leadership models.
Rebalancing team responsibilities after reorganization to prevent knowledge concentration in key individuals.
Communicating team restructuring decisions transparently while minimizing speculation and anxiety.
Assessing cultural readiness for Agile adoption in hierarchical organizations and identifying early adopter teams.