Five Practices for Building Software with Scrum
This session focuses on five key development practices from Extreme Programming (XP) that are sometimes overlooked but are essential for successful Scrum software development. These five practices include automating the build for continuously integrating software as it is written, collaborating with team members through pairing and mobbing, practicing agile design skills that enable testability, using test-first development to make code independently verifiable, and refactoring code to reduce technical debt. Together, these five technical practices are proving to be essential for sustained success when building software with Scrum. But many teams have not been exposed to the benefits of these practices or how to use them effectively.
In this session, we explore why these engineering practices are essential for building software in sprints, and how to use them to reduce risk and build quality in at every level of the development process. These practices are key to automating software validation and address the inherent risks and challenges in designing, building, and verifying software.
Outline/Structure of the Keynote
- Overview of XP practices essential to Scrum and why they are not what they seem
- Use continuous integration to the reduce risk of building software
- Employ pairing and mobbing to propagate knowledge throughout the team
- Recognize five code qualities that make software independently verifiable
- Adopt test-driven development techniques to rapidly build testable software
- Work faster by reducing technical debt through refactoring legacy code