Description

This curriculum spans the breadth of an enterprise agile transformation, comparable to a multi-phase advisory engagement, addressing team-level practices, cross-team coordination, governance integration, and organizational change leadership across complex, regulated environments.

Module 1: Establishing Agile Foundations in Enterprise Contexts

Selecting between Scrum, Kanban, and SAFe based on organizational scale, product type, and delivery cadence requirements.
Defining cross-functional team composition with clear role boundaries for product owners, scrum masters, and developers in matrixed organizations.
Aligning sprint cycles with enterprise fiscal reporting and stakeholder review calendars without compromising delivery flow.
Integrating compliance and audit requirements into sprint planning for regulated industries such as finance or healthcare.
Mapping existing waterfall governance gates to agile milestones to maintain executive oversight without introducing bottlenecks.
Implementing Definition of Done (DoD) standards that include security, performance, and accessibility criteria enforceable at scale.

Module 2: Product Ownership and Backlog Governance

Prioritizing backlog items using weighted scoring models that balance business value, technical debt, and regulatory risk.
Managing dependencies across multiple product backlogs in a portfolio setting using dependency tracking tools and integration points.
Conducting backlog refinement sessions with distributed stakeholders across time zones using asynchronous collaboration techniques.
Handling conflicting priorities from multiple business units by establishing transparent escalation paths and decision rights.
Enforcing backlog hygiene through mandatory story slicing, acceptance criteria definition, and estimation practices.
Integrating customer feedback loops into backlog management using telemetry data and user research insights.

Module 3: Sprint Execution and Delivery Engineering

Structuring daily stand-ups to highlight blockers without devolving into problem-solving sessions.
Implementing automated build and test pipelines that trigger on story completion, not just code commit.
Managing in-sprint scope changes by defining change thresholds that require sprint cancellation or renegotiation.
Coordinating integration testing across interdependent teams using feature toggles and environment management.
Tracking velocity across teams while adjusting for team maturity, story point calibration, and external dependencies.
Enforcing technical practices such as pair programming or code reviews as part of the team’s working agreement.

Module 4: Scaling Agile Across Teams and Programs

Choosing between LeSS, SAFe, and Nexus based on inter-team coupling and product architecture.
Establishing synchronization mechanisms such as Scrum of Scrums with defined attendance, agenda, and output expectations.
Managing shared resources (e.g., architects, security specialists) across multiple teams using capacity allocation models.
Aligning PI (Program Increment) planning outcomes with enterprise roadmap commitments and budget cycles.
Resolving cross-team impediments through dedicated integration teams or rotating coordination roles.
Standardizing definition of ready (DoR) across teams to reduce handoff delays and rework.

Module 5: Agile Metrics and Performance Monitoring

Selecting leading indicators such as cycle time and throughput over lagging metrics like velocity for performance insight.
Designing dashboards that differentiate team-level metrics from portfolio-level outcomes for different stakeholder audiences.
Using control charts to identify systemic delays rather than attributing variation to individual team performance.
Calibrating metrics collection frequency to avoid burdening teams with excessive reporting overhead.
Addressing metric gaming by auditing data sources and aligning incentives with delivery outcomes, not output volume.
Integrating quality metrics such as defect escape rate and test coverage into sprint review discussions.

Module 6: Agile in Regulated and Legacy Environments

Documenting audit trails for user story changes, approvals, and test results in alignment with SOX or HIPAA.
Integrating gated approvals into CI/CD pipelines without creating deployment bottlenecks.
Phasing agile adoption in legacy systems by isolating bounded contexts for iterative modernization.
Managing long-lived branches for regulatory releases while maintaining trunk-based development practices.
Adapting sprint reviews to include compliance officers and legal stakeholders as required reviewers.
Mapping user stories to regulatory requirements in traceability matrices without reverting to waterfall documentation.

Module 7: Change Leadership and Organizational Adoption

Identifying formal and informal influencers to champion agile practices in resistant departments.
Redesigning performance evaluation criteria to reward collaboration and delivery outcomes over individual output.
Conducting readiness assessments before rollout to identify structural barriers such as budgeting or HR policies.
Managing dual operating models during transition where agile and waterfall projects coexist.
Facilitating leadership workshops to shift management behavior from command-and-control to servant leadership.
Addressing team burnout by auditing sprint commitments against sustainable pace and capacity planning.

Module 8: Continuous Improvement and Agile Maturity

Conducting structured retrospectives with action tracking and follow-up verification in subsequent sprints.
Implementing improvement backlogs with prioritization and resource allocation separate from feature work.
Using maturity models to benchmark agile practices without creating compliance-driven checkbox behaviors.
Rotating facilitation responsibilities for retrospectives to build team ownership and facilitation skills.
Integrating post-release reviews with production incident data to inform backlog improvements.
Evolving agile practices based on team feedback, not prescribed frameworks, to maintain relevance and adoption.