Description

This curriculum spans the design and execution of a multi-workshop agile transformation program, addressing the same scope of challenges faced in enterprise advisory engagements around framework adoption, scaled team coordination, governance alignment, and organizational change leadership.

Module 1: Establishing Agile Foundations in Enterprise Contexts

Decide whether to adopt Scrum as a standalone framework or integrate it within a broader SAFe, LeSS, or DaD framework based on organizational scale and product interdependencies.
Assess existing project management maturity to determine the level of process adaptation required for Scrum implementation without disrupting regulatory compliance.
Negotiate team autonomy versus centralized portfolio oversight when defining sprint goals aligned with strategic roadmaps.
Map legacy waterfall artifacts (e.g., project charters, stage gates) to Scrum equivalents (product vision, release goals) to maintain stakeholder continuity.
Identify and mitigate resistance from functional managers during the transition from command-and-control to servant leadership models.
Establish baseline metrics (e.g., lead time, escape defects) before Scrum adoption to measure transformation impact objectively.

Module 2: Product Backlog Development and Prioritization

Facilitate weighted shortest job first (WSJF) scoring sessions with product owners and business stakeholders to prioritize backlog items across multiple value streams.
Implement backlog refinement rituals that enforce INVEST criteria while accommodating regulatory or audit-driven documentation requirements.
Resolve conflicts between customer-facing features and technical debt reduction when allocating sprint capacity.
Integrate compliance or security requirements into user stories without diluting agility or increasing story complexity unnecessarily.
Manage dependencies across multiple product backlogs in a scaled environment using dependency boards and cross-team syncs.
Enforce backlog transparency by defining standardized acceptance criteria and ensuring non-functional requirements are traceable.

Module 3: Sprint Planning and Team Capacity Management

Calculate team velocity using historical data while adjusting for holidays, planned absences, and organizational disruptions.
Balance sprint commitments between new feature delivery and operational support duties in hybrid project-operations teams.
Facilitate story point estimation sessions using planning poker while addressing anchoring bias and inconsistent sizing across teams.
Negotiate sprint scope with product owners when technical spikes reveal unforeseen complexity mid-planning.
Define sprint goals that are outcome-oriented rather than output-focused to maintain strategic alignment.
Integrate non-developmental roles (e.g., UX, compliance) into capacity planning to avoid bottlenecks in cross-functional delivery.

Module 4: Daily Scrum and Execution Oversight

Enforce timeboxing and focus in daily stand-ups when team members default to status reporting for management visibility.
Identify and log impediments in a visible tracker while distinguishing between team-resolvable issues and leadership-blocked items.
Monitor work-in-progress limits to prevent task switching and maintain flow efficiency in Kanban-integrated Scrum teams.
Address incomplete stories by analyzing root causes (e.g., overcommitment, unclear acceptance criteria) for retrospective improvement.
Coordinate integration timelines across dependent teams to avoid last-minute merge conflicts and deployment failures.
Ensure automated testing and CI/CD pipeline stability are treated as team responsibilities, not secondary concerns.

Module 5: Sprint Review and Stakeholder Engagement

Structure sprint reviews to demonstrate working software while managing stakeholder expectations about incomplete features.
Document feedback from stakeholders and translate it into actionable backlog items without creating unapproved scope expansion.
Balance transparency with confidentiality when demonstrating sensitive features to external or executive audiences.
Integrate user acceptance testing (UAT) cycles into sprint reviews for regulated products without delaying delivery.
Manage political dynamics when senior stakeholders attempt to override product owner prioritization during reviews.
Use demo preparation as a forcing function to enforce definition of done and reduce technical shortcuts.

Module 6: Sprint Retrospective and Continuous Improvement

Facilitate retrospectives using structured techniques (e.g., start-stop-continue, fishbone diagrams) to avoid repetitive or superficial outcomes.
Track action items from retrospectives in a visible improvement backlog and assign ownership for follow-through.
Escalate systemic impediments (e.g., tooling limitations, cross-departmental delays) to leadership with data-driven impact analysis.
Balance team psychological safety with accountability when addressing underperformance or behavioral issues.
Measure the effectiveness of process changes using lagging and leading indicators over multiple sprints.
Adapt retrospective formats based on team maturity, cultural norms, and recent delivery stressors.

Module 7: Scaling Scrum Across Programs and Portfolios

Coordinate sprint cadences across multiple teams to align on integration points and shared release milestones.
Implement Scrum of Scrums or Synch meetings with clear escalation paths and timeboxed agendas to avoid redundancy.
Manage cross-team dependencies using dependency matrices and early risk identification in backlog refinement.
Standardize metrics (velocity, defect rates, sprint goal success) across teams while allowing for contextual interpretation.
Negotiate shared resource allocation (e.g., architects, testers) across multiple Scrum teams without creating bottlenecks.
Integrate Scrum team outputs into enterprise portfolio reporting without reverting to waterfall-style milestone tracking.

Module 8: Agile Governance and Organizational Change Leadership

Design audit-compliant agile artifacts (e.g., sprint reports, risk logs) that satisfy regulatory requirements without burdening teams.
Align Scrum team KPIs with enterprise objectives while avoiding misaligned incentives that encourage gaming metrics.
Lead change communication campaigns to address middle management concerns about role relevance in agile structures.
Develop escalation protocols for when Scrum teams encounter blockers beyond their authority to resolve.
Evaluate and select agile coaching models (internal vs. external, full-time vs. part-time) based on transformation phase.
Institutionalize lessons learned by embedding agile practices into HR processes such as performance reviews and onboarding.