Description

This curriculum spans the design and coordination of enterprise Agile systems across governance, portfolio, architecture, and compliance functions, comparable in scope to a multi-phase internal transformation program addressing interdependent teams, regulatory constraints, and legacy operating models.

Module 1: Establishing Agile Governance Frameworks

Decide whether to adopt a centralized PMO model or decentralized team autonomy, weighing control against agility in cross-functional delivery.
Implement a lightweight governance board to review portfolio-level Agile initiatives, ensuring strategic alignment without introducing waterfall-style delays.
Define escalation paths for impediments that span multiple Agile teams, including criteria for when issues require executive intervention.
Balance compliance requirements (e.g., SOX, HIPAA) with Agile delivery by embedding audit checkpoints into sprint reviews rather than phase-gates.
Select metrics for governance reporting—such as velocity trends, release predictability, and defect leakage—while avoiding misuse that incentivizes gaming.
Integrate enterprise risk management practices into backlog refinement by requiring risk spikes for high-impact, uncertain features.

Module 2: Scaling Agile Across Business Units

Choose between SAFe, LeSS, or custom frameworks based on organizational complexity, legacy dependencies, and change readiness.
Map value streams to Agile release trains or feature teams, ensuring minimal handoffs and maximum end-to-end ownership.
Coordinate integration points across teams using synchronized sprint boundaries or continuous integration pipelines with automated contract testing.
Negotiate shared resource allocation for cross-cutting concerns like security, data, and platform engineering without creating bottlenecks.
Address misalignment between Agile teams and non-Agile departments (e.g., legal, procurement) by establishing liaison roles or embedded representatives.
Manage dependencies across geographically distributed teams by implementing standardized Definition of Done and shared artifact repositories.

Module 3: Product Ownership at Enterprise Scale

Distribute product ownership using a hierarchy of Product Owners and Chief Product Owners to maintain strategic coherence across large backlogs.
Implement backlog slicing strategies that balance customer-centric outcomes with technical enablers and regulatory requirements.
Facilitate backlog prioritization across competing business units using weighted shortest job first (WSJF) or cost of delay assessments.
Establish backlog governance rules to prevent scope creep, including change control thresholds and stakeholder approval workflows.
Train non-technical stakeholders to write outcome-based epics rather than solution-prescriptive requirements.
Integrate customer feedback loops into backlog refinement through structured user research cadence and embedded UX validation.

Module 4: Agile Portfolio Management

Classify portfolio investments into exploratory, growth, sustainment, and compliance categories to guide funding allocation and review frequency.
Replace annual budgeting cycles with quarterly capacity-based funding aligned to value streams rather than project line items.
Implement portfolio Kanban systems with explicit work-in-progress (WIP) limits to manage flow and prevent overcommitment.
Conduct regular portfolio reviews to terminate underperforming initiatives using objective criteria like ROI, market fit, or technical feasibility.
Align portfolio priorities with enterprise architecture roadmaps to ensure technology investments support long-term scalability.
Integrate environmental, social, and governance (ESG) criteria into portfolio decision filters for strategic initiatives.

Module 5: Integrating Agile with Enterprise Architecture

Embed architecture runway planning into program increments to ensure non-functional requirements are addressed proactively.
Define architecture decision records (ADRs) as living artifacts maintained by system architects and reviewed in iteration demos.
Negotiate trade-offs between rapid delivery and technical debt by establishing architecture review gates for high-risk changes.
Coordinate API and data contract evolution across teams using consumer-driven contract testing and versioning policies.
Align Agile teams with domain-driven design (DDD) bounded contexts to minimize coupling and improve ownership clarity.
Integrate security and compliance architecture concerns into definition of done for all user stories and enabler work.

Module 6: Measuring and Improving Agile Performance

Select leading indicators (e.g., cycle time, deployment frequency) over lagging metrics (e.g., project completion) to enable real-time course correction.
Implement telemetry pipelines to collect and visualize team-level data without creating surveillance culture or punitive reporting.
Conduct value stream mapping exercises to identify and eliminate non-value-adding activities in the delivery lifecycle.
Standardize metric definitions across teams to enable benchmarking while allowing context-specific adaptations.
Use retrospective insights to trigger targeted improvement experiments rather than generic process mandates.
Link performance data to team health checks to assess sustainability of pace and psychological safety.

Module 7: Leading Organizational Change for Agile Adoption

Identify formal and informal influencers to co-lead Agile transformation, ensuring credibility across hierarchical levels.
Design pilot programs in low-risk but visible business units to demonstrate tangible outcomes before enterprise rollout.
Negotiate revised performance evaluation criteria for managers to reward coaching and team enablement over command-and-control behaviors.
Address resistance from middle management by redefining their role as value stream facilitators rather than task supervisors.
Implement change communication cadence using multiple channels to address different stakeholder concerns and learning styles.
Establish communities of practice to sustain knowledge sharing and prevent regression to legacy processes post-launch.

Module 8: Sustaining Agile in Regulated and Legacy Environments

Adapt sprint documentation practices to meet regulatory audit requirements without reverting to pre-Agile artifact bloat.
Integrate validation and verification activities into Definition of Done for systems requiring FDA, FAA, or similar approvals.
Manage coexistence of Agile teams with waterfall-managed legacy systems using bridging roles and interface control documents.
Implement dual-track development for regulated products, separating innovation sprints from compliance stabilization sprints.
Negotiate change control board (CCB) processes to accept Agile artifacts like sprint logs and test automation reports as evidence.
Train quality assurance teams to shift from post-development testing to continuous testing embedded in CI/CD pipelines.