Description

This curriculum spans the design and sustainment of Scrum practices across multi-team application management programs, comparable in scope to an enterprise agile transformation initiative involving coordinated workshops, cross-functional process integration, and ongoing alignment with IT governance, architecture, and operations functions.

Module 1: Establishing Scrum Governance in Enterprise Environments

Define escalation paths for impediments that cross departmental boundaries, particularly when infrastructure, security, and application teams operate under separate leadership.
Align sprint review attendance requirements with stakeholder availability, balancing inclusion of senior leaders against team productivity and meeting fatigue.
Negotiate sprint duration (2 vs. 4 weeks) based on release cycles of interdependent systems, especially when external vendors control downstream environments.
Implement change advisory board (CAB) integration with sprint planning to satisfy ITIL compliance without disrupting agile flow.
Document sprint goals and outcomes in a format consumable by audit and risk management teams unfamiliar with agile artifacts.
Standardize backlog taxonomy across multiple Scrum teams to enable portfolio-level reporting without constraining team autonomy.

Module 2: Backlog Management for Complex Application Portfolios

Break down legacy enhancement requests into vertical slices that deliver measurable user value while maintaining backward compatibility.
Apply weighted shortest job first (WSJF) scoring to prioritize technical debt reduction against new feature development in shared components.
Manage dependencies between epics owned by different product owners by establishing cross-team refinement sessions with defined output templates.
Enforce INVEST criteria during backlog refinement while accommodating regulatory-driven work that does not deliver immediate customer value.
Track and report on non-functional requirements (e.g., performance, accessibility) as backlog items with testable acceptance criteria.
Integrate user feedback from production support tickets into the backlog without allowing incident-driven work to dominate sprint capacity.

Module 3: Sprint Execution in Regulated and Hybrid Environments

Structure sprint tasks to include documentation updates required for compliance (e.g., SOX, HIPAA) as part of the definition of done.
Coordinate parallel testing efforts across QA, UAT, and security teams when environments are shared and provisioned on fixed schedules.
Manage scope changes mid-sprint when legal or compliance mandates require immediate implementation, including impact assessment and stakeholder notification.
Track time spent on unplanned production support during sprints to adjust future velocity projections and capacity planning.
Use sprint burndown charts to identify task-level bottlenecks while avoiding misinterpretation by management unfamiliar with agile metrics.
Integrate automated build and deployment pipelines into the sprint workflow to ensure every increment meets release readiness standards.

Module 4: Cross-Functional Team Design and Sustainment

Define team membership when specialized skills (e.g., mainframe, cybersecurity) are shared across multiple Scrum teams, including rotation and allocation rules.
Address skill gaps in legacy system knowledge by embedding SMEs in teams on a time-boxed basis without creating dependency bottlenecks.
Manage dual reporting lines for team members who report to functional managers while being committed to Scrum team delivery goals.
Establish team norms for handling production incidents, including on-call rotations and post-mortem integration into retrospective actions.
Negotiate team size and composition when scaling beyond the ideal 5–9 members due to application complexity or regulatory staffing requirements.
Measure and report team health using structured surveys and turnover metrics to inform retention and coaching strategies.

Module 5: Integration with Enterprise Architecture and Operations

Map user stories to enterprise architecture layers (data, integration, security) to ensure non-functional requirements are addressed during implementation.
Coordinate deployment windows with operations teams that follow fixed change freeze periods, adjusting sprint demo and release timing accordingly.
Embed infrastructure as code (IaC) tasks into sprints to maintain parity between development, testing, and production environments.
Align product backlog items with enterprise technology roadmaps, especially during platform decommissioning or migration initiatives.
Design monitoring and alerting requirements as part of user story acceptance criteria to support post-release operational stability.
Integrate incident response data into backlog refinement to prioritize reliability improvements based on production failure patterns.

Module 6: Scaling Scrum Across Multiple Application Teams

Implement Scrum of Scrums with time-boxed updates focused on active dependencies, avoiding status reporting drift.
Assign dependency owners to track and resolve cross-team blockers, with escalation protocols for unresolved interface issues.
Coordinate PI (Program Increment) planning events across teams with differing sprint start dates by aligning on common milestones.
Standardize definition of done across teams while allowing customization for application-specific compliance or technical constraints.
Use feature toggles to decouple deployment from release, enabling teams to merge code independently while maintaining coordinated go-live schedules.
Manage shared component backlogs by establishing clear ownership and versioning policies to prevent breaking changes.

Module 7: Measuring and Reporting Agile Performance

Calculate team velocity using normalized story points while adjusting for team composition changes and external interruptions.
Report escaped defects to business stakeholders using root cause analysis, distinguishing between testing gaps and requirement ambiguity.
Track lead time from backlog entry to production deployment to identify bottlenecks in approval or environment provisioning stages.
Balance transparency with data sensitivity by redacting team-specific performance metrics in enterprise-wide dashboards.
Use cumulative flow diagrams to diagnose workflow constraints, particularly in testing and deployment stages with limited capacity.
Map sprint outcomes to business KPIs (e.g., transaction volume, error rates) to demonstrate value delivery beyond completion metrics.

Module 8: Continuous Improvement and Organizational Adaptation

Structure retrospectives to produce actionable process changes, assigning owners and deadlines to improvement items.
Rotate facilitation of agile ceremonies to build team ownership and reduce reliance on a single Scrum Master.
Adapt Scrum practices in response to organizational restructuring, such as mergers or divestitures affecting application ownership.
Integrate lessons from post-implementation reviews into backlog refinement and future sprint planning cycles.
Evaluate the need for agile coaching support based on team maturity assessments and delivery consistency metrics.
Update team working agreements when introducing new tools, compliance requirements, or remote collaboration models.