Hacker News new | past | comments | ask | show | jobs | submit login
The Zero-Bug Policy in Software Development (medium.com/quality-functions)
9 points by samhatoum on May 9, 2016 | hide | past | favorite | 24 comments


Have a "zero bug policy" in 1 simple step:

Re-classifies bugs you don't want to fix as "improvements".


... Seriously? That's ridiculous click-bait crap. You didn't implement a zero-bug policy, you just redefined what you call a bug. This is no different than everyone else's policies, except that now you're screwing with terminology.

Perhaps I am wrong here, but I got a much different message out of the post.

It's not about actually having ZERO bugs as it is about enforcing a strict and logical classification system.

I think this quote resonated with me the most:

> ...but much more so, the bugs were a result of incorrect specification or missing specifications.

The argument being made is that if you hand a developer a specification, the developer implements the specification _as specified_, then you discover the specification was incorrect or that in practice you want a change would you classify that as a _BUG_? No. But a lot of shops _do_, so they end up with _too_ many tasks classified as a "Bug" which makes it impossible to prioritize since being a "Bug" is a binary descriptor.

By enforcing a classification system means you have the ability to then enforce a prioritization system...and really the prioritization system is key for maintaining consistent output and forward progress.

At least that what I felt the argument of the post was...and I see some reasonability to it. Especially since, as the author mentioned, this is not a new idea.

I'm in the business of building complex software systems, and I think another way to improve software development is to fire all the agile coaches, use the money saved to hire more developers, and use those developers to give the team more help to fix defects and add features. I really cringe when a project management type comes in and points out the obvious. This kind of stuff only works if you are building simple software like a CMS system or a basic CRUD app. Building complex software is an exploration in and of itself. In the old telecom days, months would be spent writing precise feature specifications and design documents. That's how much time it takes. Does ANYONE have that time today? Aside from safety critical systems where you have no choice but to put in the time, I think the answer is no. The software development process has shrunk significantly, and as an industry we have decided to meld design, architecture, feature specification, coding and testing. Bugs are a necessary end product of this stupidity.

FYI, I'm not a project management type. I've build numerous continuous delivery pipelines for enterprise clients and helped them deliver multiple features per week. I have current skills in writing Java, C# and Node.js. I've written my own testing frameworks (Check out Chimp.js), I coach developers on how to write better code, as well as business people on how to create better specs.

I typically try to stay away from CRUD applications where possible as I find them too simple. I prefer to work on meaty domain-driven applications using CQRS and Event sourcing, but that's just my tech preferences.

I too worked in telecoms and was part of the development team that did the AOL LLU from BT in the UK. The old-world you speak about has a ton of wisdom in it, that much I agree with you on, however it was also riddled with stupidity of its own.

The amount of time you put into the specs is not where the trick is in my view, it's about splitting the specs down into manageable chunks (something the old world never understood) and then making sure those chunks get the necessary time (something often missed these days).

If you think the solution for your company is not to have any advisors, and that you have all you need, then by all means hire more developers. They are the smartest people around ;)

I didn't mean a personal attack on you btw. Your track record suggests you know your stuff and would likely be an asset on a large/complex project. My comment is informed by my bad experiences at two previous employers - both parachuted agile coaches to "help" when the problems were obviously a runaway feature list and not enough developers. Surely, you must know of charlatans in connection with agile. I think we all need to educate management that agile is not a silver bullet or a panacea. It is a process with good and bad. Great if welded by adults but very easy to abuse by non-grownups. To many of my developer friends, agile is a synonym for daily status updates, which is absolutely not what it is supposed to be.

Thanks for the clarification and totally agree. I have seen project managers turn their gantt-chart sideways, have 1 hour standup meetings and call themselves Scrum Masters! So I know exactly what you mean.

Nowadays I never say the A word in a companies for the exact reasons you mention. Now I say "let's start producing higher quality, faster" and go from there.

> about enforcing a strict and logical classification system.

But that is something so common place that even pretty poorly run software organizations which ship crap do it.

The rhetorical Everyone has a bug database with features, enhancements, low priority bugs and "blockers". That plus version control is the bare minimum requirement for having any kind of process distinguishable from total chaos.

This is an article about water being wet.

Perhaps, but having worked for a government sub-contractor that had precisely this problem, I don't think it's as universally true as you would think.

At that particular company, everything was a "task" and tasks were just thrown at employees as they came. This wasn't just limited to software development either...this applied to customer support and service as well.

Their solution, and the solution the customer (government contractors) was to schedule numerous and regular meetings in order to touch base and monitor progress...which only contributed to the problem.

Also the article itself is actually a case study...

You missed the part about making them the top priority after you reclassify them.

After that, you are right, it's that simple. I even state that in the article that it's not complicated. Yet, not many seem to do it.

Click-bait? Not quite. I'm someone that is writing to genuinely provide my experience to others. In the article I discuss why it works and what it does in the long run. Where the origins of Zero-Defect comes from etc etc.

Sorry you didn't find it useful, I hope that some do, and I hope that you and your team are the type that don't need this advice.

It's a useful classification system, but calling it "zero bugs" is basically a lie. Whether something is labeled critical/bug or not is based on importance, not whether it's actually a bug.

It's not really a lie when you think about it. It's very true to its name.

It's saying, after you've classified the bugs, you're not to do any other work until the bug list is cleared. This will lead you to zero-bugs (of the known ones of course).

I've implemented and seen this first-hand in 4 different companies.

That's not the part I'm calling a lie.

Let me word it differently.

You classify tickets into categories A,B,X,Y. You always clear out A and B before doing anything else. As a strategy to have "zero unresolved important issues", it's valid.

The disconnect is between the "Bug" ticket category, and the actual definition of what a bug is.

"Web font is being downloaded when it should be embedded in the app" is clearly a bug, by the normal definition of bug.

This system classifies by priority to get Critical/"Bug"/Other, and it further divides the lowest priority into new features vs. changing features. At no point does it ask if something is a mistake. It doesn't care. So it shouldn't use the word 'bug'. It tricks people into thinking it's something it's not.

Actually this is where you can be flexible with a specification. If the ticket was initially specified as embedding the fonts, then technically it's an implementation defect since it was already specified. However, as a team you might decide it's not too bad to download fonts instead of embedding them. This is where you can be flexible with the solution. Instead ob being rigid with expectation when the reality is the bug can comfortably be re-classified.

If however the loading time with downloading the fonts is something the team is not as per the team's quality standards and they are not willing to live with it, then it should absolutely remain as a bug.

Now that the classification portion is out of the way, the team priority is to work on bugs first no matter what.

So I'm saying that "the actual definition of what a bug is" should be stated as a guideline and the team can decide on an ongoing basis. Some guidelines might be rigid, others not so much.

You can make whatever categories you want. But if your definition of "bug" is in disagreement with the rest of the world, don't tout it as having "zero bugs". Just pick a different word, one that doesn't mislead.

I don't think the world has an agreed definition of a bug, or at least I've not seen it!

I understand that the issue people have is with the wording of the zero-bug. As I've mentioned elsewhere it's still true that it is a striving towards zero-bug and I've seen it first hand where we get to 0 known bugs.

I'll meditate on this a little and see what I come up with. I really do appreciate this feedback :)

Definitions very somewhat, but I think very few people would say that the business impact of a problem changes whether it's a 'bug'.

The article is only about known bugs that are sitting in a bug database, which makes the entire piece trivial.

The main concern in software quality turning unknown bugs into known bugs, not with reshuffling the type and priority fields in a bug database (which is of course important).

"Zero bugs" means "exhaustively tested or else proved correct" (given a perfect set of high level requirements and detailed specification to begin with).

Any other use of "zero bugs" in a headline is clickbait.

The bugs that screw you are the unknown ones. Like security exploits that the Bad Guys find in the field before you do.

As gshulegaard has mentioned, I think you're taking the name Zero-Bug to mean something different than what I intended.

Zero-Bug does not mean writing software without defects - that's impossible, instead it means correctly classifying bugs and then striving to keep the bug-count at 0.

I've written another article on the three types of bugs, and one of those is the "unknown ones" you refer to. There are things you can do to tease out some unknowns, but of course there's no cure for bugs as a whole. It's here if you're interested: https://goo.gl/TlvNcY

On the clickbait, I assure you it's not. I labelled the approach Zero-Bug long before writing the article. It creates an attitude in a team. After I've worked with teams to clarify what Zero-Bug really means, they strived towards doing more checks before even pushing out code. We celebrated Zero-Bug days when we were actually down to 0 and believe it or not, I've seen up to 2 iterations at a go be free of bugs. Coincidence? I don't think so.

You're working with a definition of "Zero Bug" that doesn't arise from the meanings of "bug" and "zero" combined together in the obvious, orthogonal way.

There are such compounds entrenched in the English language (like "new wave" or "blackboard") but they take decades to enter general use.

I don't think we need "zero bug" to be a non-compositional compound of this type. The terms "bug" and "zero" are too significant in computing for us to allow them to be hijacked like this.

For instance, we wouldn't redefine "zero latency" as being 5 seconds (say, in a situation in which we can't get it any shorter for the given span, due to the distance and the speed of light). Latency is latency, zero is zero, and five seconds isn't zero.

I urge you to reconsider your use of technical language.

I like you're reasoning!

There is no situation where zero latency actually means a latency of zero, whereas in the description I've provided there is a situation where you end up with zero bugs.

Out of interest, what would you call the action of striving towards zero bugs?

I'm not sure about what glib phrase I would use (say, consisting of just two words) but the main idea in the overall approach is that we stay on top of critical bugs. If we have critical bugs, we don't do anything else until they are solved. We don't polish the chrome on some shiny new feature, while a fire is raging. So this is "Bugs First" or something. Except it's not all bugs first, just the showstoppers. "Fires First?" Hmm, what's a glib word that clearly means "show-stopper defect"?

Another way to approach this is from the angle of: no customer is left to dangle in a situation where they aren't getting value from the product, where they are faced with an issue for which there is no feasible workaround, or some security breach. What's a glib phrase which quite precisely conveys the idea that try to prevent this situation at all costs, and get them out of it ASAP if it happens?

It's not just about critical bugs though. Those are "stop what you're doing and get on it". ANY bug that is not critical gets worked on next no matter what. So it's about all bugs getting priority over other work.

It's akin to an immune system. When a bug is found, it's attacked until it's dead.

I really appreciate this feedback. As there are a few people that the phrase is rubbing up the wrong way, I'll meditate on it a little and see what I come up with.

I understand; but it's hard for some convenient phrase to cover every aspect of the process. So in the end there has to be some understanding that it's the name of some process that has more aspects than just the literal meaning. (Just like "Zero Bugs").

Again, I responded elsewhere, but I don't think the article was about actually having ZERO bugs. It was about enforcing a strict classification system so you can implement a reasonable prioritization scheme (Critical issues and Bugs are fixed FIRST by distinguishing what are actually bugs and what are Improvements).

So it's an article on the development lifecycle and how to get consistent forward progress with some organizational improvements. It's not actually about writing software with "Zero" bugs.

Applications are open for YC Summer 2021

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact