Understand who the Developers really are in a Scrum Team, what they are accountable for, and how self-management turns a group of specialists into a team that owns its plan. Learn to run Sprint Planning so the Developers, not a manager, drive the work.
Watch the free preview
The problem with treating Developers as task-takers — free to watch, no account needed.
What you'll learn
- Define who the Developers are in a Scrum Team and the four things they are accountable for
- Explain self-management and why the Developers, not the Scrum Master or Product Owner, own the plan
- Describe how the Definition of Done embeds quality into every Increment
- Redesign Sprint Planning so the Developers self-organise the Sprint Backlog themselves
- Build a self-management checklist that keeps the Developers driving the plan each Sprint
Syllabus
Who the Developers Really Are
The problem with treating Developers as task-takersFree preview
Developers, one of three accountabilities
Self-Management and Quality
Self-management — who does what, when, and how
Quality and the Definition of Done
Self-Management in Real IT Work
How the Developers own Sprint Planning
Case study — the team that waited to be told
Making Self-Management Stick
Building a self-management checklist for Sprint Planning
Common traps and anti-patterns to avoid