Description

This curriculum spans the operational intricacies of implementing Scrum across multiple teams in complex organizations, comparable to a multi-workshop program addressing role governance, scaled planning, and process adaptation in regulated, stakeholder-heavy environments.

Module 1: Establishing Scrum Roles and Accountability Structures

Define clear boundaries between Product Owner and project manager responsibilities in organizations transitioning from waterfall.
Resolve conflicts when a senior stakeholder assumes de facto Product Owner duties without attending refinement or sprint reviews.
Implement mechanisms to prevent Scrum Masters from being assigned project coordination or reporting tasks that dilute servant leadership.
Address team resistance when developers perceive the Scrum Master as a process enforcer rather than a facilitator of improvement.
Design escalation paths for Product Owners when stakeholders demand direct access to the development team mid-sprint.
Manage dual-role assignments, such as a team lead acting as both Scrum Master and technical contributor, without creating bottlenecks.

Module 2: Product Backlog Creation and Prioritization Governance

Establish criteria for rejecting stakeholder requests that lack measurable outcomes or business value justification.
Implement a backlog refinement cadence that prevents sprint planning from becoming a discovery session.
Balance technical debt items against feature requests when executives prioritize visible deliverables over system health.
Enforce INVEST principles during backlog grooming when user stories are consistently written as solution directives rather than outcomes.
Document and communicate prioritization decisions when multiple Product Owners compete for shared team capacity.
Integrate regulatory or compliance requirements into the backlog without allowing them to dominate the product roadmap.

Module 3: Sprint Planning and Capacity Modeling

Calculate team capacity by adjusting for known absences, holidays, and recurring operational duties before sprint commitment.
Address overcommitment patterns when teams consistently fail to meet sprint goals due to optimistic velocity projections.
Define "ready" for backlog items to prevent teams from starting work on stories that lack acceptance criteria or design inputs.
Manage stakeholder pressure to include last-minute items in sprint planning after the backlog has been frozen.
Integrate non-functional requirements into sprint planning when performance or security tasks are omitted from story points.
Adjust sprint goals when external dependencies, such as third-party API availability, delay planned work.

Module 4: Daily Scrum and Progress Transparency

Enforce timeboxing and focus when daily stand-ups devolve into problem-solving sessions or status reporting to managers.
Address inconsistent attendance by team members who view the daily scrum as optional or low-value.
Use task board metrics to identify work-in-progress bottlenecks without creating a culture of individual performance tracking.
Respond when stakeholders attend daily scrums and redirect questions to the Scrum Master or Product Owner.
Manage remote team dynamics when time zone differences reduce real-time collaboration during the daily scrum.
Update sprint forecasts in real time when blockers persist beyond one or two days without resolution.

Module 5: Sprint Review and Stakeholder Engagement

Structure sprint reviews to demonstrate working software rather than PowerPoint summaries of progress.
Filter stakeholder feedback collected during reviews to avoid ad hoc changes to the sprint backlog.
Manage expectations when executives demand production-level polish for features demonstrated in a staging environment.
Document decisions made during reviews that influence the product backlog, ensuring traceability to future sprints.
Include user representatives in reviews when feedback from internal stakeholders does not reflect actual end-user needs.
Balance transparency with confidentiality when demonstrating features that involve sensitive data or competitive differentiators.

Module 6: Sprint Retrospective and Continuous Improvement

Facilitate retrospectives that produce actionable process changes rather than recurring complaints without follow-up.
Protect psychological safety when team members raise concerns about leadership decisions or organizational constraints.
Track implementation of improvement items across sprints to prevent retrospective fatigue and disengagement.
Adapt retrospective formats when teams become disengaged with standard techniques like "start, stop, continue".
Escalate systemic impediments, such as tooling limitations or cross-team dependencies, that the team cannot resolve independently.
Integrate retrospective outcomes into the next sprint’s goals without overloading the team with process changes.

Module 7: Scaling Scrum Across Teams and Programs

Coordinate backlog dependencies across multiple Scrum teams when shared components require synchronized delivery.
Implement Scrum of Scrums meetings that focus on integration blockers rather than status repetition.
Align sprint cadences across teams when asynchronous sprints create integration delays and planning complexity.
Assign Product Ownership for multi-team products, deciding between a single Product Owner or a scaled Product Owner team.
Manage versioning and release planning when teams produce components with different stability and deployment frequencies.
Standardize definition of done across teams to ensure consistent quality and integration readiness at scale.

Module 8: Measuring Outcomes and Adapting the Framework

Select metrics such as velocity, lead time, and escape defect rate that inform process improvement without incentivizing gaming.
Interpret trend data over time rather than single-point measurements to assess team performance and predictability.
Adjust Scrum practices based on team maturity, such as reducing ceremony frequency for experienced, self-organizing teams.
Integrate customer feedback and usage data into product decisions without disrupting the sprint cycle.
Modify Scrum events or artifacts when regulatory environments require audit trails not natively supported by the framework.
Decide when to supplement Scrum with Kanban for support or maintenance work that conflicts with fixed-length sprints.