Description

This curriculum spans the breadth of a multi-workshop organizational change program, addressing the same systemic challenges encountered when embedding Agile practices across teams, governance structures, and enterprise functions.

Module 1: Establishing Agile Foundations and Organizational Readiness

Assess current project management maturity by auditing existing workflows, documentation practices, and team autonomy levels across departments.
Identify resistance points in hierarchical reporting structures when introducing self-organizing team principles.
Define scope for initial Agile pilot teams based on project complexity, stakeholder engagement, and delivery urgency.
Negotiate team access to product owners who can commit 10–15 hours per sprint to backlog refinement and feedback.
Map legacy waterfall governance checkpoints to Agile milestones without reintroducing phase-gate bottlenecks.
Develop a communication plan to align HR, finance, and legal teams on Agile’s iterative delivery model and its impact on budgeting and compliance.

Module 2: Facilitating Effective Sprint Cycles and Ceremonies

Adjust sprint duration from two to three weeks based on regulatory review cycles in highly controlled industries like healthcare or finance.
Enforce timeboxing in daily standups by redirecting detailed technical discussions to follow-up huddles with relevant contributors.
Structure sprint planning to include capacity planning that accounts for team members’ non-project responsibilities like production support.
Implement a physical or digital sprint board with explicit work-in-progress (WIP) limits to prevent task overload.
Facilitate sprint reviews with stakeholders who expect formal presentations, adapting content to show incremental value without overpromising.
Lead sprint retrospectives using anonymized input tools when team members express concerns about psychological safety in open forums.

Module 3: Backlog Management and Prioritization Techniques

Apply weighted shortest job first (WSJF) to balance feature delivery against compliance or technical debt items in regulated environments.
Break down epics into user stories with clear acceptance criteria while avoiding premature technical specification.
Resolve conflicts between product owner priorities and architectural constraints raised by system architects during backlog refinement.
Maintain a visible "parking lot" for stakeholder requests that do not align with current sprint goals.
Integrate non-functional requirements (e.g., performance, security) into user stories without bloating the backlog.
Conduct backlog grooming sessions with distributed teams across time zones using asynchronous collaboration tools.

Module 4: Scaling Scrum Across Teams and Programs

Coordinate sprint start dates across interdependent teams to synchronize integration points and reduce merge conflicts.
Implement Scrum of Scrums with rotating representatives to avoid creating a de facto management layer.
Manage dependencies between Scrum teams using a dependency board updated during cross-team sync meetings.
Adapt Definition of Done to include integration testing when multiple teams contribute to a single product increment.
Address misalignment in team velocity metrics by focusing on outcome delivery rather than story point comparisons.
Integrate external vendors using hybrid ceremonies when their internal processes do not support full Scrum adoption.

Module 5: Removing Impediments and Coaching Teams

Escalate infrastructure provisioning delays by engaging with operations leadership and tracking resolution in impediment logs.
Coach teams on conflict resolution when disagreements over technical implementation stall story completion.
Identify skill gaps during sprint retrospectives and coordinate with functional managers for targeted training or pairing.
Intervene when product owners treat the backlog as a task dump without prioritization or business context.
Address burnout signals by reviewing team velocity trends and advocating for sustainable pacing with stakeholders.
Mediate disputes between team members and external auditors over documentation requirements in Agile artifacts.

Module 6: Metrics, Reporting, and Agile Governance

Select leading indicators like sprint burndown and cycle time over vanity metrics such as velocity trends for executive reporting.
Customize dashboards for different stakeholder groups—technical leads receive flow efficiency data, executives see release forecasts.
Justify scope changes mid-sprint to compliance officers by referencing empirical data from backlog re-prioritization sessions.
Balance transparency with confidentiality when sharing team performance data under data privacy regulations (e.g., GDPR).
Report on technical debt reduction using trend lines in automated test coverage and defect escape rates.
Defend Agile delivery timelines to finance teams by correlating sprint outputs with quarterly business objectives.

Module 7: Leading Organizational Change and Agile Transformation

Redesign performance review criteria with HR to reward collaboration and adaptability over individual task completion.
Replace fixed quarterly budgets with rolling funding allocations tied to value delivery milestones.
Train middle managers to shift from directive oversight to servant leadership and team enablement roles.
Address union or labor agreements that define work assignments in ways incompatible with cross-functional teams.
Measure transformation progress using adoption rates of Agile practices, not just delivery speed or defect counts.
Sustain momentum post-initial rollout by establishing a community of practice with rotating facilitation roles.