Description

This curriculum spans the technical and organisational challenges of embedding Agile practices into DevOps workflows, comparable to a multi-workshop program that addresses pipeline integration, team coordination, and enterprise scaling across diverse operational contexts.

Module 1: Integrating Agile Frameworks with DevOps Pipelines

Selecting between Scrum, Kanban, or SAFe based on team size, release frequency, and organizational structure while ensuring compatibility with CI/CD tooling.
Aligning sprint planning cycles with automated deployment windows to prevent merge conflicts and environment contention.
Implementing work-in-progress (WIP) limits in Kanban systems that reflect actual deployment capacity of staging and production environments.
Mapping user story acceptance criteria to automated test gates in the pipeline to enforce Definition of Done.
Coordinating backlog refinement sessions with infrastructure teams to account for provisioning lead times in sprint commitments.
Resolving misalignment between Agile velocity metrics and deployment success rates by introducing deployment stability KPIs.

Module 2: Continuous Integration and Agile Delivery Rhythms

Configuring CI triggers to respect sprint boundaries while enabling trunk-based development without blocking integration.
Enforcing mandatory peer review policies in pull requests without introducing delays that violate Agile timeboxing.
Managing test suite execution time to fit within sprint iteration feedback loops, including parallelization and test selection strategies.
Integrating static code analysis tools into CI pipelines with failure thresholds that balance code quality and developer throughput.
Handling flaky tests in automated suites by defining quarantine procedures and ownership accountability within Agile teams.
Coordinating feature branch strategies with release planning to avoid long-lived branches that contradict Agile integration principles.

Module 3: Automated Testing in Agile-Driven DevOps

Allocating testing responsibilities across QA, developers, and product owners within sprint planning to ensure test coverage alignment.
Designing test pyramid implementation strategies that prioritize unit and integration tests over end-to-end in fast feedback cycles.
Managing test data provisioning in automated pipelines to support repeatable test execution without violating data privacy policies.
Integrating contract testing into CI to enable independent service development in microservices environments with Agile teams.
Defining ownership of test maintenance when test failures block pipeline progression during active sprints.
Adjusting test environment availability to match sprint cadence, including on-demand environment provisioning.

Module 4: Release Management and Agile Governance

Implementing feature flags to decouple deployment from release, enabling Agile teams to deliver incrementally without coordination overhead.
Establishing change advisory board (CAB) processes that accommodate frequent releases without reintroducing waterfall bottlenecks.
Defining rollback procedures and ownership for failed releases that occur during or immediately after sprint demos.
Aligning release documentation updates with sprint deliverables to maintain compliance without disrupting flow.
Managing regulatory or audit requirements for release sign-offs in environments with continuous deployment practices.
Coordinating multi-team release trains in scaled Agile frameworks while maintaining independent deployment autonomy.

Module 5: Monitoring, Feedback, and Iterative Improvement

Instrumenting production monitoring to capture user behavior that informs backlog prioritization in sprint planning.
Configuring alerting thresholds to avoid alert fatigue while ensuring rapid feedback for issues introduced in recent deployments.
Integrating customer support ticket data into sprint retrospectives to prioritize technical debt and usability fixes.
Linking deployment metadata with incident tracking systems to identify root causes tied to specific sprint deliverables.
Establishing service-level objectives (SLOs) that influence sprint goals for reliability and performance improvements.
Using lead time and deployment frequency metrics to assess team agility without incentivizing risky deployment behaviors.

Module 6: Cross-Functional Team Dynamics and DevOps Culture

Defining clear ownership boundaries between development, operations, and security roles in Agile teams to prevent task silos.
Rotating on-call responsibilities across team members to distribute operational load and reinforce shared accountability.
Facilitating blameless postmortems after production incidents while maintaining sprint commitments and team morale.
Integrating security champions into Agile teams without creating bottlenecks in development throughput.
Managing knowledge sharing across distributed Agile teams using documentation standards and asynchronous handoff protocols.
Addressing skill gaps in infrastructure-as-code or observability tools through just-in-time training within sprint capacity planning.

Module 7: Scaling Agile DevOps Across the Enterprise

Standardizing CI/CD templates across business units while preserving team-level customization for domain-specific needs.
Implementing centralized observability platforms that aggregate data from independently operated Agile teams without imposing uniformity.
Managing dependencies between Agile teams working on interdependent services using contract-first development and API governance.
Establishing platform teams to provide self-service DevOps tooling that reduces cognitive load on delivery teams.
Balancing local team autonomy with enterprise compliance requirements for data protection and audit trails.
Measuring cross-team value stream performance without creating misaligned incentives or competition for metrics.

Module 8: Technical Debt and Sustainability in Agile DevOps

Allocating sprint capacity for infrastructure modernization without compromising feature delivery commitments.
Tracking technical debt in product backlogs with clear ownership and measurable resolution criteria.
Enforcing architectural guardrails in CI/CD pipelines to prevent accumulation of anti-patterns in code and configuration.
Managing legacy system integration in Agile delivery when full refactoring is not feasible within current sprint cycles.
Using codebase health metrics to trigger refactoring spikes or dedicated hardening sprints based on objective thresholds.
Negotiating trade-offs between rapid feature delivery and long-term maintainability during release planning sessions.