HeptaMS Agile foundation
Leads to certification: HeptaMS Certified Skill – Agile foundation
The course conveys agile principles and the mechanics of scrum through a simulation.
- Scope
- ½ day (~4 h) – 1 h fundamentals plus 3 h simulation 1 blocks of 4 hours
- Formats
- Live Online · In person
- Exam
- Multiple choice, 10–15 questions, 70 % to pass, 3 attempts included
- Prerequisites
- none
What it covers
The course conveys agile principles and the mechanics of scrum through a simulation. After a compact introduction to origins, principles, roles, events and artefacts, the team builds a city out of Lego across three sprints, going through planning, delivery, review and retrospective. In the closing debrief, the experience is traced back to the underlying principles and complemented with the limits of agile approaches.
Agile practices can be explained without it becoming clear what they are for. As a result, events are carried out correctly without having any effect.
What you can do afterwards
- Name the three principles of manageability, localized decision making and interaction, and test an approach against them.
- Name the roles, events and artefacts of scrum and explain the separation of roles.
- Explain why the sprint limits the size of work packages.
- Explain why a shared definition of done is required.
- Explain why small increments reduce risk.
- Determine for a concrete event whether it serves its purpose.
- Name the limits of agile approaches.
Who this course is for
Whole teams who are meant to work in an agile way and do not know what that means. Newcomers without agile experience. Leaders who want to understand what their teams are talking about.
Anyone growing into an agile role. Mixed groups from business and IT who need a shared experience. Team events with learning content.
Learning objectives in detail
- 1 Name the three principles of manageability, localized decision making and interaction, and test any approach against them.
- 2 Name the roles, events and artefacts of scrum and explain why the separation of roles is a separation of powers.
- 3 Explain why the sprint is a batch-size limit and what follows from that for the size of work packages.
- 4 Explain why a shared definition of done is necessary, from their own experience rather than from theory.
- 5 Explain why small increments are risk protection and not merely a methodological ideal.
- 6 Determine at a concrete event whether it serves its purpose or is merely held (action versus content).
- 7 Name the limits of agile approaches and that agility is a means rather than an end.
Dates & demand pools
No date yet - express interest in a demand pool and we will set one when enough peers join.
No date that fits? Express non-binding interest in a demand pool - once enough peers join, we set a date and place and get in touch.
Name your preferred date and start a pool for this course. Once enough people join we schedule it and get in touch – you only book after that.
Is this course right for your situation?
If no date fits or you need the course in-house: drop us a line and we will come back with a proposal.