Day 1: Scrum Foundations, Empiricism, and Values

Scrum Framework for Complex Work

• Distinguish framework from linear project plan
• Connect empiricism with learning from results
• Identify conditions suited to iterative delivery
• Analyze a case appropriate for Scrum

Transparency, Inspection, and Adaptation

• Choose information visible to team
• Select purposeful moments for inspection
• Convert inspection findings into practical adaptation
• Diagnose key insufficient transparency

Applying Scrum Values

• Connect commitment, focus, openness, respect, courage
• Analyze how values influence daily decisions
• Expose behavior violating values despite compliance
• Draft team agreement reflecting Scrum values

Day 2: Scrum Team Accountabilities and Product Direction

Product Owner Responsibilities

• Maximize product value through work ordering
• Manage Product Backlog transparently and clearly
• Define Product Goal and maintain coherence
• Simulate a prioritization decision

Scrum Master Responsibilities

• Establish Scrum understanding and correct misuse
• Coach team and organization toward effectiveness
• Address impediments constraining team progress
• Role-play service to a Scrum Team

Developers and the Scrum Team

• Own Sprint plan and Increment quality
• Determine how items become usable Increment
• Self-manage while maintaining goal clarity
• Build collaboration rules for small team

Day 3: Scrum Artifacts and Commitments

Product Backlog and Product Goal

• Write clear orderable backlog items
• Connect work with longer-horizon product objective
• Use Daily Scrum for Sprint progress
• Build an initial Product Backlog

Sprint Backlog and Sprint Goal

• Select work serving the Sprint Goal
• Update plan as Sprint learning occurs
• Protect goal without freezing implementation method
• Design Sprint Backlog for a case

Increment Quality and Definition of Done

• Define what makes an Increment usable
• Apply Definition of Done consistently
• Prevent incomplete work entering the Increment
• Inspect an Increment against agreed quality

Day 4: Scrum Events and Iterative Flow

Applied Sprint Planning

• Discuss why the Sprint is valuable
• Select work achievable within capacity
• Determine how work will be accomplished
• Simulate key Sprint Planning

Applied Daily Scrum

• Use Daily Scrum for Sprint progress
• Adapt upcoming plan when impediments appear
• Prevent event becoming manager status report
• Run a concise Daily Scrum

Review and Retrospective Events

• Inspect Sprint results with stakeholders
• Reorder Product Backlog for stakeholder learning
• Review work quality and team effectiveness
• Conduct Review followed by a Retrospective

Day 5: Sprint Simulation and Organizational Scrum Application

Running a Mini Sprint

• Choose a goal and deliverable items
• Manage changing information during work
• Build Increment meeting Definition of Done
• Record adaptation decisions during the simulation

Measures and Complementary Practices

• Use flow indicators as optional support
• Distinguish useful practices from framework rules
• Choose tools supporting transparency without bureaucracy
• Analyze a team flow board

Organizational Application Challenges

• Address management intervention weakening self-management
• Align governance with Product Owner accountability
• Identify multi-team and dependency barriers
• Prepare improvement plan for Scrum application

• Scrum Team simulation with explicit accountabilities
• Backlogs goals and commitments built from an applied case
• Scrum events practiced with feedback on purpose
• Mini Sprint demonstrating genuine inspection and adaptation