He describes how they do
- Product backlogs (including user and tech stories)
- Sprint planning (using planning poker :)
- Communicate sprints
- Sprint backlogs (taskboard, burndown chart,...)
- Daily Scrums
- Sprint demos
- Sprint retrospectives
- ...
and gives tips and tricks about
- Slack time between sprints
- Organising - distributed - teams
- Estimated velocity
- Fixed prices and release planning
- eXtreme Programming practises
- Testing and quality
- ...
- and other suggested reading
