Description

This curriculum spans the design and coordination of multi-team agile programs, addressing governance, scaling, and technical integration challenges comparable to those encountered in enterprise agile transformations supported by internal coaching and cross-functional advisory teams.

Module 1: Establishing Agile Governance in Enterprise Environments

Define escalation paths for impediments that span multiple agile teams without reverting to waterfall-style command structures.
Select which enterprise policies (e.g., security, compliance) require mandatory adherence versus those that allow team-level interpretation.
Implement lightweight audit trails for sprint reviews and backlog changes to satisfy internal audit requirements without burdening teams.
Negotiate dual reporting lines for team members who report to both functional managers and product owners.
Decide whether to mandate a single Definition of Done across all teams or allow context-specific variations.
Integrate agile delivery metrics into existing enterprise risk dashboards without distorting team incentives.

Module 2: Scaling Frameworks: SAFe, LeSS, and Custom Hybrids

Map existing portfolio management gates to PI (Program Increment) planning events in SAFe without introducing waterfall delays.
Determine team boundaries in LeSS when shared dependencies include legacy systems maintained by non-agile units.
Customize the number of teams per Agile Release Train based on domain coupling and release coordination needs.
Align architecture runway planning with PI objectives while maintaining emergent design principles.
Resolve conflicts between centralized product management and decentralized team autonomy in large-scale backlogs.
Train Scrum Masters to facilitate cross-team synchronization without becoming de facto project managers.

Module 3: Product Ownership at Scale

Allocate a single Product Owner across multiple teams when the product spans distinct customer segments.
Break down epics into team-specific backlog items without losing strategic alignment to the product vision.
Manage stakeholder demands for fixed scope and date commitments while maintaining backlog flexibility.
Implement backlog refinement sessions that include customer representatives without slowing team velocity.
Balance technical debt reduction against feature delivery in roadmap prioritization under executive pressure.
Use weighted shortest job first (WSJF) in a way that doesn’t deprioritize critical platform improvements.

Module 4: Agile Metrics and Performance Monitoring

Select leading indicators (e.g., cycle time) over lagging ones (e.g., velocity) for executive reporting to avoid gaming.
Set thresholds for cycle time and throughput that trigger process reviews without mandating targets.
Expose team-level burn-down anomalies to leadership without enabling micromanagement.
Correlate deployment frequency with production incident rates to assess true delivery health.
Use control charts for lead time to distinguish common-cause from special-cause variation in delivery delays.
Integrate customer satisfaction metrics (e.g., NPS) into sprint review artifacts without politicizing feedback.

Module 5: Integrating Agile with Non-Agile Functions

Coordinate release schedules with operations teams that follow ITIL change advisory board (CAB) processes.
Align agile development timelines with annual budgeting cycles managed by finance departments.
Negotiate contract terms with vendors who require fixed scope and deliverables despite internal agile practices.
Integrate compliance testing into sprint cycles when legal review operates on a quarterly cadence.
Translate user stories into regulatory documentation requirements without creating redundant artifacts.
Manage procurement processes for cloud services that require purchase orders despite on-demand scaling needs.

Module 6: Distributed and Remote Agile Teams

Structure daily stand-ups across three time zones without requiring core overlap of more than two hours.
Choose collaboration tools that support real-time editing and auditability without introducing license sprawl.
Standardize Definition of Ready criteria when teams in different regions interpret acceptance differently.
Conduct virtual retrospectives that produce actionable outcomes despite cultural reluctance to speak up.
Rotate meeting facilitation across regions to prevent dominance by a single location’s working hours.
Address discrepancies in internet reliability and hardware provisioning that impact remote pairing effectiveness.

Module 7: Agile Coaching and Organizational Change

Identify informal leaders within teams to champion agile practices without formal authority or titles.
Design pilot programs that demonstrate agile value in measurable terms to skeptical middle management.
Manage resistance from project managers transitioning to Scrum Master roles with reduced control.
Develop internal agile coaching capacity without creating a siloed “agile police” function.
Adjust transformation pace based on organizational readiness without conceding to status-quo inertia.
Measure coaching effectiveness through team autonomy and problem-solving capability, not just ceremony compliance.

Module 8: Technical Practices for Sustainable Agility

Mandate automated testing coverage thresholds for mission-critical services while allowing flexibility in test types.
Enforce continuous integration discipline across teams with varying levels of technical maturity.
Balance investment in CI/CD pipeline improvements against feature delivery in quarterly planning.
Standardize infrastructure-as-code templates without constraining team-level innovation.
Introduce pair programming in teams with high bus factors despite resistance from senior developers.
Integrate security scanning tools into the build pipeline without increasing false positives that erode trust.