Description

This curriculum spans the design and coordination of multi-team Agile adoption in complex application environments, comparable to a multi-workshop operational transformation program that integrates DevOps, compliance, and portfolio governance across interdependent systems.

Module 1: Assessing Organizational Readiness for Agile Transformation

Conducting stakeholder interviews across IT, business units, and support teams to map existing workflows and identify resistance points.
Mapping current application support SLAs against Agile delivery cadences to assess compatibility and identify conflicts.
Reviewing legacy system dependencies that constrain iterative deployment and determining technical debt thresholds for transition.
Establishing baseline metrics for incident volume, change failure rate, and mean time to resolution to measure Agile impact.
Identifying which application portfolios are candidates for Agile adoption based on business criticality and team autonomy.
Defining escalation protocols for production issues during sprint cycles to maintain service stability.

Module 2: Designing Hybrid Operating Models for Application Support and Development

Allocating team capacity between BAU (Business-As-Usual) support and sprint-based development using weighted allocation models.
Integrating incident and problem management processes with sprint backlogs to prioritize technical fixes.
Creating dual-track planning cycles where one track manages urgent patches and the other handles feature development.
Defining handoff procedures between Level 3 support engineers and development teams during defect resolution.
Implementing service-level agreements between Agile teams and service desk for response and resolution time commitments.
Establishing a change advisory board (CAB) process that accommodates both scheduled sprint releases and emergency fixes.

Module 3: Structuring Agile Teams within Application Management Frameworks

Assigning product owner roles from business-facing application managers to ensure backlog alignment with operational needs.
Embedding SREs or operations engineers within Scrum teams to improve observability and deployment reliability.
Defining team boundaries for applications with shared components to prevent ownership ambiguity.
Rotating on-call responsibilities within Agile teams while protecting sprint focus and minimizing context switching.
Designing team incentives that reward both feature delivery and system stability metrics.
Integrating offshore or vendor resources into sprint ceremonies with adjusted communication protocols for time zone variance.

Module 4: Integrating DevOps Practices into Agile Application Lifecycles

Implementing automated build and deployment pipelines for legacy applications with limited CI/CD support.
Configuring monitoring dashboards to feed real-time performance data into sprint retrospectives.
Using feature toggles to decouple deployment from release, enabling controlled rollouts in production.
Standardizing environment provisioning across development, testing, and production to reduce configuration drift.
Enforcing infrastructure-as-code practices for application configurations to support repeatable deployments.
Integrating security scanning tools into the pipeline without introducing unacceptable build delays.

Module 5: Governing Agile Delivery in Regulated Environments

Documenting sprint decisions and backlog changes to meet audit requirements for SOX or HIPAA compliance.
Mapping user stories to regulatory controls to demonstrate traceability during audits.
Implementing approval gates for production deployments that satisfy compliance without disrupting flow.
Archiving sprint artifacts including standup notes, retrospectives, and demo recordings per data retention policies.
Coordinating with internal audit teams to define acceptable evidence formats for Agile processes.
Managing third-party vendor changes within sprints while ensuring contractual and compliance obligations are met.

Module 6: Managing Technical Debt and System Stability in Agile Cycles

Allocating sprint capacity specifically for refactoring and infrastructure improvements using a debt backlog.
Setting thresholds for code coverage and technical debt ratio that trigger mandatory remediation sprints.
Using production incident root cause analysis to inform backlog prioritization for reliability improvements.
Balancing new feature requests against stability initiatives when under business pressure to deliver.
Implementing canary releases and dark launching to reduce the risk of introducing instability.
Establishing service health scores that influence sprint planning and team performance reviews.

Module 7: Scaling Agile Across Multiple Application Portfolios

Coordinating release trains across interdependent applications with misaligned sprint schedules.
Standardizing backlog taxonomy and estimation practices across teams without stifling autonomy.
Resolving resource contention when shared platform teams support multiple Agile squads.
Implementing a centralized program management office (PMO) to track cross-portfolio dependencies and risks.
Using dependency mapping tools to visualize integration points and prevent integration bottlenecks.
Adapting SAFe, LeSS, or Nexus frameworks based on organizational size and application coupling complexity.

Module 8: Measuring and Optimizing Agile Performance in Operations

Defining and tracking lead time for changes, deployment frequency, and change failure rate across applications.
Correlating sprint velocity with production incident rates to identify overcommitment risks.
Using burn-down charts and cumulative flow diagrams to detect bottlenecks in the delivery pipeline.
Conducting quarterly value stream mapping to identify waste in application change processes.
Adjusting sprint length based on deployment windows, release cycles, and business demand patterns.
Aligning team OKRs with business outcomes such as user satisfaction, system uptime, and cost per release.