The Forgotten First Principle of Software Delivery

We have an industry-wide blindspot for the most important metric in software, and now is the time to change that.

Hi. I’m Sam, and I am obsessed with delivering higher quality software, faster.

What does that mean? Well, like you, I’m passionate about innovation. But more specifically, I’m passionate about delivering innovation as quickly as possible, without compromising quality.

Most teams start with the best intentions and deliver features to customers very quickly. But soon they are slowed down by support issues and fixing bugs — one of the 7 wastes of lean — while management continuously increases the pressure to deliver even more features, even more quickly.

Every team in the world wants to deliver faster

And going faster is now easier than ever — or so it seems…

  • Developers are able to release features more quickly than ever, thanks to application frameworks like Meteor, UI frameworks like Semantic, and the flurry of SaaS services that do the heavy-lifting for you like Stripe.
  • Cloud based automated deployments help push out releases faster and more frequently using technologies like Docker and services like Amazon’s BeanStalk.
  • Most critically, Agile practices give us methods for iterating quickly and measuring speed, or rather the flow of work. It’s common to hear management say things like “we need to find a way to increase our velocity” and “let’s scale our development team”.

We have become obsessed with the flow principle

As someone with 10 years of experience as an Agile practitioner and coach, I can tell you that constantly measuring flow is a good thing as it allows you to track your team’s progress. If you are not already doing it, then you should be.

  • If you are a SCRUM team, you are likely measuring velocity with story points, and tracking your progress against this metric.
  • If you are a Kanban team, you might be measuring throughput and analyzing cumulative flow diagrams to spot bottlenecks.

But there’s a problem of only optimizing for flow. Let’s first explore what flow really means.

The Flow principle

Flow is simply units over time. With water, you might use liters per second. In software, the unit is the value. I will discuss the nuances of how to measure value in another post, but for now let’s make it easy and say that a single unit of value is a complete feature that has successfully been deployed to production.

In SCRUM this is known as velocity, eg. 15 story points per iteration, and in Kanban it’s known as throughput, eg. 3 features per week.

With such an intense focus on the flow of value alone, it seems that most teams consider Flow and Value to be first principles of software delivery.

The problem is that when you only optimize for flow, you are encouraging your team to deliver features faster, but you’re not encouraging the team to delivery higher quality features faster.

The missing principle is Quality

Quality is a loaded term. It can mean accuracy, precision, excellence, fit-for-purpose, efficiency, reliability, maintainability and many other terms depending on who you ask. The reality is that quality is not easy to define.

Quality cannot be defined because it empirically precedes any intellectual construction of it.
The Metaphysics of Quality — Robert Pirsig

Quality is hiding in plain sight

Quality does not really have a dedicated measure of its own, however everybody that works in software development instinctively knows that quality is a critical factor of the delivery equation.

This team is not delivering any value

In SCRUM, the velocity measure contains an implicit indicator of quality. For example, if your team were to spend a few sprints fixing bugs and not delivering any story points, the velocity would be zero, which indicates poor quality elsewhere.

Activities flat-lining in the middle — source

In Kanban, cumulative flow diagrams also contain an indicator of quality. A flat line of activities can be an indicator that the team is doing wasteful work, which in turn indicates poor quality.

You can see that quality is not being directly measured above, but the effects of poor quality are being observed through other indicators. Therefore we can measure quality through proxy indicators.

We can do something about the “poor quality” and see if we are improving through the proxy indicators. For example, if the team is constantly being bogged down with regression bugs (proxy indicator), they can apply practices such as automated testing to catch those bugs at development time. After they have applied the practice, they can monitor the number of regression bugs and see an improvement in quality.

The same principle applies further up the product development phase. For example, if the business owners are creating features that users don’t like (proxy indicator), they can employ methods such as user testing and market research to validate their ideas before spending time and money developing them. They can then check back with users and see that the features are being used.

The methods and practices that are put in place in response to the poor quality can be seen as functions that are needed to ensure quality. I call these Quality Functions, which are essential for the continued delivery of value.

Quality is a fundamental function of value

Let’s consider the team from the example above that is getting bogged down with fixing regression bugs. Let’s assume they spend 90% of their time fixing the bugs. This means, the lack of quality functions like automated testing results in the team only working 10% of their time on delivering value. If they had high test coverage, they might only spend 20% of their time fixing regression bugs.

Let’s apply the same principle to the business owners that are creating features that the users don’t want. The lack of quality functions like user testing and market research, is reducing their delivery of value by 100%!

You simply cannot go faster if you don’t prioritize quality.

And when you don’t apply the necessary quality functions to all aspects of your product development lifecycle, the resulting poor quality acts like a giant parachute that drags behind you. As the poor quality builds up, it becomes increasingly difficult to move forward.

We don’t have a holistic measure for quality. And that is a problem.

Does it surprise you that 50% of developer time is spent fixing bugs? (source)

How does that compare to your software team? Do you even know?

We have created an industry-wide blind spot for what in my opinion is the most important first principle of software delivery: Quality

Any battle scarred developer or experienced team already knows this.

We have many great advancements in tools and techniques to help developers create better quality software like TDD, BDD etc. I have started to write about some of these on our automated testing best practices repository on GitHub.

But it is difficult to improve what you can’t measure. And it is even harder to create a business case for investing in quality, if there are no measures to base it upon.

I have built my career and reputation on being the guy that the world’s best companies call when they can’t deliver and don’t know why. I have performed this role for companies like Audi, The BBC, Nike and Sky, working with some of the most respected consultancies in the world.

The underlying theme of the problem is just always the same: Lack of good quality practices, too many bugs and too many impediments to delivering value.

We can work to improve flow, but without improving quality, nothing improves.

Our industry-wide focus on flow is giving diminishing returns.

Throwing more testers at regression bugs, and pushing out features that nobody wants does not make you go faster. It’s just more air trapped in your parachute.

If you only optimize for flow, poor quality will hold you back

And sometimes, you won’t even know why. But,

If you optimize for quality, you will get faster flow for free!

Now is the time to refocus on quality

I have built my company to do exactly this. We are already working with some world-class companies to help them deliver higher quality software, faster. We have a selection of products that make a tangible difference to the cost of their bugs, but more importantly we are working with our clients to rebuild the whole software delivery process with quality, not just flow, influencing everything.

Become a Quality Ninja!

If you would like you and/or your team to learn how to implement a quality-first practice, and how this can benefit you, check out our new book “Quality Faster

This digital knowledge resource combines both theory and practical tutorials to provide everything you need to improve quality (and therefore flow too) across your full stack, and entire team. We start from the very foundations of quality, value and software delivery principles, and apply these to forming your own team process and test strategy. These are then executed through specific code samples for Node.JS, React, Chimp JS, Mocha, Meteor and many more.

Click here to check out the book and become a Quality Ninja!

Want to read More?

This is the first of a series of posts that I have written about measuring and prioritizing quality. In my next post, I cover the relationship between Quality and Value, and doing a deeper dive into the concept of quality functions.

We have also created a Medium Publication called “Quality Faster” as a home for opinions and ideas on the theme of how teams can deliver higher quality software at ever increasing pace.

Please join us by following the “Quality Faster” publication and feel free to suggest your own articles for inclusion if you think they would be good additions to the collection.

I look forward to helping you deliver higher quality software, faster.


Other articles I’ve written: