Description

This curriculum spans the equivalent of a multi-workshop program used to establish and refine Scrum practices across teams, covering role definition, planning, execution, and governance with the level of structural detail found in organizational transformation initiatives.

Module 1: Establishing Scrum Roles and Accountability Structures

Define the Product Owner’s authority over backlog prioritization and enforce boundaries to prevent scope encroachment by stakeholders.
Assign a dedicated Scrum Master to protect team process integrity, including shielding the team from external interruptions during sprints.
Designate cross-functional development team members with T-shaped skills, ensuring at least two individuals can cover critical technical domains.
Resolve dual reporting lines by aligning performance evaluations with both functional managers and Scrum team outcomes.
Implement escalation protocols for when the Product Owner is unavailable during sprint execution.
Formalize decision rights for sprint goal changes, requiring joint agreement between Product Owner and team before mid-sprint adjustments.

Module 2: Backlog Development and Prioritization Techniques

Break down epics into user stories using INVEST criteria, ensuring each meets testability and independence thresholds before refinement.
Apply Weighted Shortest Job First (WSJF) to prioritize backlog items when multiple value streams compete for capacity.
Conduct backlog refinement sessions with stakeholders to validate acceptance criteria and clarify dependencies.
Integrate non-functional requirements into user stories by attaching performance and security benchmarks.
Manage technical debt visibility by allocating a fixed percentage of each sprint to backlog items labeled for refactoring.
Use story mapping to visualize release increments and align backlog structure with customer journey phases.

Module 3: Sprint Planning and Commitment Negotiation

Determine sprint length based on release cadence needs, balancing feedback speed against planning overhead.
Calculate team capacity by adjusting velocity with availability for holidays, meetings, and support duties.
Negotiate sprint goals with stakeholders who demand specific deliverables, ensuring alignment with team capacity.
Decompose selected backlog items into sprint tasks with estimated hours, verifying task granularity supports daily tracking.
Document sprint objectives in measurable terms to enable unambiguous success evaluation at review.
Address mismatched expectations by establishing a pre-planning checkpoint with the Product Owner to validate scope feasibility.

Module 4: Daily Scrum Execution and Progress Transparency

Enforce timeboxing to 15 minutes and require each team member to report progress against sprint backlog items, not general updates.
Track impediment resolution ownership in the daily scrum, assigning follow-up actions with due dates.
Use task board synchronization to ensure physical or digital boards reflect real-time work status before each meeting.
Address off-topic discussions by parking them in a separate follow-up session to maintain meeting focus.
Monitor velocity trends across sprints to identify overcommitment patterns and adjust future planning accordingly.
Integrate automated build and test status into the daily scrum review when CI/CD pipelines are part of the workflow.

Module 5: Sprint Review and Stakeholder Feedback Integration

Demonstrate only completed work that meets the team’s definition of done, excluding partially finished features.
Structure feedback collection using structured templates to categorize input into enhancements, defects, and new requests.
Limit presentation time to allow at least half the session for interactive discussion and Q&A with stakeholders.
Document stakeholder requests and route them to the backlog for formal prioritization, not immediate implementation.
Adjust product roadmap based on feedback trends observed over three or more consecutive reviews.
Manage conflicting stakeholder demands by facilitating a joint prioritization session post-review.

Module 6: Sprint Retrospective and Continuous Improvement

Select retrospective formats (e.g., Start-Stop-Continue, Mad-Sad-Glad) based on team morale and recent sprint outcomes.
Ensure action items from retrospectives are assigned to specific owners with deadlines and tracked in the next sprint.
Balance process improvements with delivery pressure by limiting improvement experiments to one or two per sprint.
Protect psychological safety by enforcing a no-blame policy and moderating dominant voices during discussion.
Validate the impact of implemented changes by measuring outcome metrics (e.g., cycle time, defect rate) post-implementation.
Rotate facilitation responsibility among team members to build shared ownership of process improvement.

Module 7: Scaling Scrum Across Teams and Programs

Coordinate dependencies between Scrum teams using a dependency board updated during synchronized planning events.
Appoint a Chief Product Owner to align backlog priorities across multiple teams working on the same product.
Implement Scrum of Scrums meetings with designated representatives to resolve cross-team blockers weekly.
Standardize definition of done across teams to ensure consistent quality in integrated increments.
Manage integration risk by requiring shared CI pipelines and automated regression testing across teams.
Adopt release train planning for synchronized delivery when regulatory or market events require coordinated releases.

Module 8: Governance, Metrics, and Organizational Alignment

Select leading indicators (e.g., sprint burndown, backlog health) over lagging metrics (e.g., project completion) for course correction.
Report team velocity to management in ranges, not exact numbers, to discourage misuse for performance benchmarking.
Align Scrum artifacts with audit requirements by maintaining version-controlled records of sprint goals and reviews.
Integrate budget cycles with release planning by forecasting capacity-based delivery over fiscal quarters.
Address compliance needs by embedding regulatory checkpoints into the definition of done for relevant features.
Negotiate HR policies to support team-based incentives rather than individual performance metrics.