10 Minute Build is the idea that we should be able to build a system and run its test suites in 10 minutes or less. Fast build-and-test provides quicker feedback to the developers who wrote the code. It allows them to move on to the next thing – a new feature or improving the current one. Fast builds allow for multiple check-ins per person/pair a day, which in turn makes small check-ins practical. These smaller check-ins reduce the risk of team members stepping on each other’s virtual toes and, with a bit of practice, allow them to develop a rhythm that results in continuous small improvements.
In comparison, when builds are slow, Developers wander off to do new things while waiting (See: Multitasking), which results in increased cost to go back and fix defects when they’re found later in the build, especially since longer builds are run less often so it will take longer to find errors.
- 10-Minute Build – Extreme Programming Practice
- ContinuousIntegrationCertification – Martin Fowler
- Crazy fast build times (Or when 10 seconds starts to make you nervous) – Yesterday I was wrong
- Ten-Minute Build – The Art of Agile Development
- The Ten Minute Build – Roger Hughes
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index