Experiential team training
Scrum training.
Experience the mechanics before memorizing the terminology. Use exercises and your own questions to understand how Scrum supports product development, learning and adaptation.
For people who need to use Scrum, not just explain it.
For teams starting with Scrum and people who want to make better sense of their existing practice. The starting point can be a new team, confusing accountabilities, or events that no longer help people make decisions.
Tell me who will take part, how familiar they are with Scrum and what you want them to do differently afterward. We agree the focus before choosing a training format.
Experience, examine, apply.
Scrum is a framework. Exercises help make its purpose and mechanics tangible.
- 01
Experience inspect and adapt
Work in short iterations, compare predictions with results and try improvements. Exercises such as the Ball Point Game make feedback and adaptation visible before we connect them to Scrum.
- 02
Connect events to real decisions
Examine Sprint Planning, the Daily Scrum, Sprint Review and Sprint Retrospective. Discuss what each is for, what decisions it supports and how it relates to the work of the Sprint.
- 03
Clarify accountabilities and artifacts
Connect the Product Owner, Scrum Master and Developers to your product work. Explore the Product Backlog, Sprint Backlog and Increment, together with the Product Goal, Sprint Goal and Definition of Done.
Choose the training that fits your situation.
Private training can focus on your team’s questions and product context. If you want a public Scrum Master or Product Owner course, use the courses overview to explore those separately.
Dates, scope and any certification preparation are agreed for the specific offer. No certification or exam voucher is implied by this private-training page.
What should your team understand or do differently?
Tell me who the training is for, what is happening today and what you want to work on. We can discuss an appropriate starting point.