Module 4Optional
Developer campaign
Craft the Increment. Own the how. Hold the line on quality.
19 lessons ~93 min 6 games Certificate included This role module opens once you finish Foundations and pass its quiz. That way every learner shares the same Scrum baseline before specialising.
What you'll learn
- Your role as Developer
- Anatomy of the Sprint Backlog
- Building a Definition of Done that holds the line
- What self-management actually looks like
- Technical excellence is a Scrum concern
- Pairing and mobbing as a Sprint tool
Full lesson list
- 1Your role as Developer3 min
- 2Game: Sprint Planning under capacity9 min
- 3Anatomy of the Sprint Backlog3 min
- 4Building a Definition of Done that holds the line4 min
- 5Game: Is it really Done?10 min
- 6What self-management actually looks like3 min
- 7Technical excellence is a Scrum concern3 min
- 8Checkpoint: Plan to your capacity8 min
- 9Pairing and mobbing as a Sprint tool3 min
- 10Refactoring inside the Sprint3 min
- 11Estimation, lightly3 min
- 12Checkpoint: Is it really Done?9 min
- 13Your job in the Daily Scrum3 min
- 14Code review as a team habit3 min
- 15Checkpoint: Replan mid-Sprint8 min
- 16A test strategy for a Sprinting team3 min
- 17Managing technical debt honestly3 min
- 18Checkpoint: DoD under real pressure9 min
- 19Ship the smallest useful thing3 min
- Developer quizEarn certificate