The latest expert opinions, articles, and guides for the Java professional.
Developer Productivity Report 2013 – How Engineering Tools & Practices Impact Software Quality & Delivery
Part II – Practices: How the things you do affect Quality & Predictability
Ok, you’re probably ready for some numbers and good-looking graphs now, so let’s get into it. In this section, we look at how the methodologies (i.e. these so-called “best practices”) affect the quality and predictability of software releases.
When looking at Practices, we want to know what methods and team activities work best to improve productivity for the team as a whole. So we’ll be looking into things like communication methods, testing and reviews, branching etc. We asked questions to give is a good view on each of the following:
- Code quality
- Technical debt
- Test coverage
- Pairing up
- Code reviews
- Task estimation
- Code testing
- Communication methods
Next you’ll find the questions as the respondents saw them, with our analysis of the responses. So let’s go!
“Do you monitor and fix code quality problems? (e.g. with Sonar)”
Code quality coverage is often a hot-debated topic among developers. Based on the responses of over 1000 engineers, we see half of those asked don’t fix code quality issues, and most of those people don’t even monitor code quality.
When applying this question to differences in predictability and quality, we see a clear increase in both with teams that fix code quality issues. A nearly 10-point increase in predictability comes with fixing all code quality issues–seems kind of like a no-brainer now, huh?
Leave a comment