A Case of Software Data Collection
Television has done a fine job of glamorizing the job of an investigator. Whether you fancy the classic Sherlock Holmes, the affable Colombo, or even perhaps enjoy the suspense associated with cracking the case on television shows like “The First 48,” Hollywood has tried to make us believe the search for clues is always exciting. However, those who have searched thousand row spreadsheets for software data collection efforts, may beg to differ with that sentiment. The needle in a haystack analogy may seem more fitting, if only the haystack was bigger!
Although most folks will never get the chance to track down a villain like Sherlock’s nemesis, Professor Moriarty, there still is a need in many professions to find “clues.” In software estimation, those clues can be thought of as software project data. What information do I need to solve this software project estimation case and how do I obtain it? In that search for information, perhaps we can utilize some basic investigation steps to find the software data needed to produce good software project estimates. Honestly, why would one embark on the often daunting quest of collecting project data for future estimation without at least a basic approach? Well, there are many reasons. However, let’s focus on a way to proactively look at an approach using the analogy of an investigation.