Description

This curriculum spans the breadth of an enterprise agile transformation engagement, addressing governance, scaling, innovation integration, and technical execution with the same granularity seen in multi-team DevOps and product delivery overhauls.

Module 1: Establishing Agile Governance in Enterprise Environments

Define escalation paths for sprint impediments that span multiple departments, ensuring accountability without bypassing team autonomy.
Implement lightweight compliance checkpoints within sprint reviews to satisfy audit requirements without disrupting flow.
Negotiate release approval thresholds with legal and risk teams to allow continuous deployment while maintaining regulatory alignment.
Balance centralized architecture standards with team-level technology choices through a federated governance model.
Document architectural decisions using ADRs (Architecture Decision Records) to maintain traceability across distributed teams.
Integrate security and privacy reviews into the definition of done for user stories involving PII or financial data.

Module 2: Scaling Agile Across Multiple Teams and Domains

Coordinate dependencies between teams using a scaled event calendar that aligns sprint planning, reviews, and retrospectives.
Implement feature toggles to decouple deployment from release, enabling independent team delivery despite shared codebases.
Select between LeSS, SAFe, or Nexus frameworks based on organizational size, product complexity, and legacy integration needs.
Design cross-team API contracts early in the release train to minimize integration conflicts during hardening sprints.
Appoint product owners for subsystems to manage local backlogs while aligning with an overarching product vision.
Use dependency mapping to identify and resolve inter-team blockers before sprint initiation.

Module 3: Integrating Innovation Cycles with Stable Delivery Pipelines

Allocate dedicated capacity in each sprint for technical spikes addressing emerging technologies or experimental features.
Run parallel innovation tracks using dual-track agile, separating discovery from delivery without fragmenting team focus.
Integrate proof-of-concept code into the main branch behind feature flags to enable early feedback and reduce rework.
Establish criteria for promoting experimental features to production, including performance, supportability, and monitoring readiness.
Measure innovation throughput using lead time from idea to validated learning, not just deployment frequency.
Rotate team members into innovation pods to prevent siloing and transfer knowledge across product domains.

Module 4: Continuous Delivery and DevOps Integration

Standardize infrastructure provisioning using IaC (Terraform, CloudFormation) to ensure environment parity across stages.
Enforce automated testing gates in CI/CD pipelines, requiring unit, integration, and security scans before promotion.
Implement blue-green deployments in production to reduce rollback time and mitigate customer impact during failures.
Monitor pipeline stability by tracking build success rate and mean time to recovery for failed deployments.
Negotiate SLAs with operations teams for incident response when automated rollbacks trigger in production.
Manage configuration securely using encrypted parameter stores instead of hardcoding in deployment scripts.

Module 5: Product Ownership and Backlog Management at Scale

Break down epics into independently testable user stories using story mapping sessions with stakeholders.
Apply weighted shortest job first (WSJF) to prioritize backlog items across competing business objectives.
Conduct backlog refinement with UX and operations teams to include usability and supportability criteria early.
Manage stakeholder expectations by publishing roadmap updates tied to objective outcomes, not feature lists.
Use outcome-based metrics (e.g., user engagement, error reduction) to validate backlog item success post-release.
Resolve conflicting priorities from business units by aligning backlog items to measurable KPIs in the product charter.

Module 6: Measuring and Optimizing Agile Performance

Track cycle time and work-in-progress limits to identify bottlenecks in the delivery workflow.
Use burn-up charts with scope change annotations to communicate progress transparently to executives.
Correlate team velocity with defect escape rates to assess trade-offs between speed and quality.
Implement team health checks quarterly to evaluate psychological safety and process adherence.
Normalize metrics across teams by focusing on flow efficiency rather than team-level velocity comparisons.
Integrate customer feedback loops into sprint retrospectives using NPS or CES collected post-release.

Module 7: Managing Technical Debt and Architecture Evolution

Conduct architecture kata sessions to evaluate system evolvability under anticipated load and feature growth.
Allocate sprint capacity for refactoring based on static code analysis findings and technical debt ratio trends.
Use strangler fig pattern to incrementally replace legacy components without system-wide rewrites.
Enforce modular design through automated architecture conformance tests in the build pipeline.
Document component ownership and SLIs to clarify accountability for performance and uptime.
Balance reuse and redundancy by evaluating cost of shared services against team delivery autonomy.

Module 8: Leading Agile Transformation and Change Management

Identify and engage middle managers early to redefine their roles in an outcome-oriented delivery model.
Redesign performance reviews to reward collaboration and system-level outcomes over individual output.
Address resistance from legacy project management offices by co-developing hybrid reporting mechanisms.
Train Scrum Masters to facilitate conflict resolution in cross-functional teams with competing incentives.
Align incentive structures with agile KPIs, such as time-to-market and customer satisfaction, not just budget adherence.
Conduct value stream mapping workshops to expose process waste and prioritize transformation initiatives.