In my workshops, I often have people who are focused on the question: “How can I help my team go faster?”, or “How can we deliver this Product sooner?” Whenever anyone asks, my answer is always the same: “You must slow down to go fast.” I then often get some puzzled looks.
In software development, the single best way to improve quality, and eventually speed, is writing less code. Most of the time spent writing code should be to understand the problem and then find the simplest solution to it. The practices used to facilitate this in Agile software development are popularly known as Agile Engineering Practices.
See Also:
- Behaviour Driven Development
- Collective Code Ownership
- Continuous Delivery
- Continuous Integration
- Just Enough Design Upfront
- Mob Programming
- Pair Programming
- Refactoring
- 10 Minute Build
- Test Driven Development
- Trunk-Based Development
- Unit Testing
Resource Book Link:
- Agile Technical Practices Distilled – Pedro Moreira Santos, Marco Consolaro, and Alessandro Di Gioia
- Software Engineering at Google – Titus Winters, Tom Manshreck and Hyrum Wright (Caveat: we think Pair Programming and Ensemble Programming trump Code Reviews)
*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.
Synonyms:
Engineering Practices, Software Engineering Practices
