I recently saw a graph from The Standish Group quantifying that only 20% of all delivered software features are “often or always used.” This is a pretty staggering statistic to take in, considering when I think of this in light of what my client is building right now for their customers. Could it be said that only 20% of our effort is used??? Think about that for a minute!
What we could do is to completely elaborate, build, test, or document our releases so we can, when looking back, see what was most important to the user… but this would be too late…
What we could do is to focus on value and risk. In order to spot and eliminate fat and waste we need to make sure that we have a prioritized backlog based on the value the stories bring or the risk they address. Remember, this list is a collaboration between the team and the product owner!
So what can we do to make sure we’re on target?
- Keep the backlog prioritized by value and risk
- Do not help the most important user persona in our domain to monopolize our utilization
- Create features that have proven metrics to decrease issues with quantifiable savings
- Work first on bugs that have been shown to be a root cause of costly issues and bottlenecks (i.e. performance, exceptions, long downtimes, etc)
- Fix what’s broken
- The feature is a proven innovation that has been prototyped and tested
- The feature opens a new market that is quantified and targeted
[Image Source: icanhascheezburger.com]