New titles, roles, and responsibilities aren’t the only changes Scrum teams are
asked to make. For a Scrum team to be truly successful, they must go beyond
adopting the basic, highly visible parts of Scrum and commit to real changes in
the way they approach the actual work of creating a product. I’ve observed teams
who work in sprints, conduct good sprint planning and review meetings, never
miss a daily Scrum, and do a retrospective at the end of each sprint. They see solid
improvements and may be as much as twice as productive as they were before
Scrum. But they could do so much better.
Chapter Contents
- Strive for Technical Excellence
- Test-Driven Development
- Refactoring
- Collective Ownership
- Continuous Integration
- Pair Programming
- Design: Intentional yet Emergent
- Getting Used to Life Without a Big Design
- Guiding the Design
- Improving Technical Practices Is Not Optional
- Additional Reading