Developers attach quickly to tools because they are concrete and have well defined behavior. It is easier to learn a tool than to learn best practices or methodology. Tools only assist in solving problems, they can’t solve the problem by themselves.
A developer who understands the problem can use tools to increase productivity and quality. Poor developers don’t invest the time or effort to understand how to code properly and avoid defects. They spend their time learning how to use tools without understanding the purpose of the tool or how to use it effectively.
- defect trackers to help you manage defect tracking
- version control systems to manage source code changes
- tools to support Agile development (Version One, JIRA)
- debuggers to help you find defects
There are many tools out there, but let’s just go through this list and point out where developers and organizations get challenged. Note, all statistics below are derived from over 15,000 projects over 40 years.1
Believe it or not, some organizations still don’t have defect tracking software. I’ve run into a couple of these companies and you would not believe why. The effect of not having a defect tracking system is pretty severe, and there is evidence to prove this.
Inadequate defect tracking methods: productivity -15%, quality -21%
So we are pretty much all in agreement that we need to have defect tracking; we all know that the ability to manage more than a handful of defects is impossible without some kind of system.
Automated defect tracking tools: productivity +18%, quality +26%
The problem is that developers disagree over what might be the best defect tracking system. The real problem is that almost every defect tracking system is poorly set-up, leading to poor results. Virtually every defect tracking system when configured properly will yield tremendous benefits. The most common pitfalls are:
- Introducing irrelevant attributes into the defect lifecycle status, i.e. creation of statuses like deferred, won’t fix, or functions as designed
- Not being able to figure out if something is fixed or not
- Not understanding who is responsible for addressing a defect
The tool vendors are happy to continue to provide new versions of defect trackers. However, using a defect tracker effectively has more to do with how the tool is used rather than which tool is selected.
One of the most fundamental issues that organizations wrestle with is what is a defect? A defect only exists if the code does not behave according to specifications. But what if there are no specifications or the specifications are bad? See It’s not a bug, it’s… for more information.
Smart organizations understand that the way in which the defect tracker is used will make the biggest difference. Discover how to get more out of you defect tracking system in Bug Tracker Hell and How to Get Out.
Another common problem is that organizations try to manage enhancements and requirements in the defect tracking system. After all whether it is a requirement or a defect it will lead to a code change, so why not put all the information into the defect tracker? Learn why managing requirements and enhancements in the defect tracking system is foolish in Don’t manage enhancements in the bug tracker.
Version Control Systems
Like defect tracking systems most developers have learned that version control is a necessary hygiene procedure. If you don’t have one then you are likely to catch a pretty serious disease (and at the least convenient time).
Inadequate change control: productivity -11%, quality -16%
Virtually all developers dislike version control systems and are quite vocal about what they can’t do with their version control system. If you are the unfortunate person who made the final decision on which version control system is used just understand that their are hordes of developers out their
cursing you behind your back.
Version control is simply chapter 1 of the story. Understanding how to chunk code effectively, integrate with continuous build technology, and making sure that the defects in the defect tracker refers to the correct version are just as important as the choice of version control system.
Tools to support Agile
Sorry Version One and JIRA, the simple truth is that using an Agile tool does not make you agile, see this.
These tools are most effective when you actually understand Agile development. One of my most effective Agile implementations only used Google docs in the implementation.
I have written extensively about why debuggers are not the best primary tools to track down defects. So I’ll try a different approach here!
One of the most enduring sets of ratios in software engineering has been 1:10:100. That is, if the cost of tracking down a defect pre-test (i.e. before QA) is 1, then it will cost 10x if the defect is found by QA, and 100x if the defect is discovered in deployment by your customers. Most debuggers are invoked when the cost function is in the 10x or 100x part of the process.
- Planning code, i.e. PSP
- Test driven development, TDD
- Design by Contract (DbC)
- Code inspections
- Pair programming for complex sections of code
You can find more information about this in:
Seldom Used Tools
Tools that can make a big difference but many developers don’t use them:
- Automated static analysis: productivity +21%, quality +31%
- Automated unit testing: productivity +17%, quality +24%
Automated unit testing generally involves using test driven development (TDD) or data driven development together with continual build technology.
- Automated sizing in function points: productivity +17%, quality +24%
- Automated quality and risk prediction: productivity +16%, quality +23%
- Automated test coverage analysis: productivity +15%, quality +21%
- Automated deployment support: productivity +15%, quality +20%
- Automated cyclomatic complexity computation: productivity +15%, quality +20%
Important Techniques with No Tools
There are a number of techniques available in software development that tool vendors have not found a way to monetize on. These techniques tend to be overlooked by most developers, even though they can make a huge difference in productivity and quality.
The Personal Software Process and Team Software Process were developed by Watts Humphrey, one of the pioneers of building quality software.
- Personal software process: productivity +21%, quality +31%2
- Team software process: productivity +21%, quality +31%3
The importance of inspections is covered in:
- Code inspections: productivity +21%, quality +31%4
- Requirement inspections: productivity +18%, quality +27%4
- Formal test plans: productivity +17%, quality +24%
- Function point analysis (IFPUG): productivity +16%, quality +22%
The reality is that learning a tool without learning the principles that underlie the problem you are solving is like assuming you can beat the great Michael Jordan at basketball just because you have great running shoes.
Learning tools is not a substitute for learning how do do something competently.
Competent developers are continually learning about techniques that lead to higher productivity and quality, whether or not that technique is supported by a tool.
- Gilb, Tom and Graham, Dorothy. Software Inspections
- 1Jones, Capers. SCORING AND EVALUATING SOFTWARE METHODS, PRACTICES, AND RESULTS. 2008.
- Jones, Capers. The Economics of Software Quality. 2011
- Radice, Ronald A. High Quality
- 2Watts, Humphrey. Introduction to the Personal Software Process
- 3Watts, Humphrey. Introduction to the Team Software Process