Comments on: On Software Quality

By: Bob Lambert

Bob Lambert — Tue, 27 Jan 2009 13:54:03 +0000

I agree with Jason’s comment if you think of “Everyone has a responsibility for quality” as a slogan, but whoever defines roles for the team (usually the PM but I like it to be a team activity) needs to make sure responsibility for quality is built into each role. For example, the team should define what a good requirement is and then not accept the requirements document until all of the requirements are good. Coders shouldn’t promote from development until their code works. These really sound obvious but I’ve seen way too many projects where this stuff doesn’t get set up and then everyone wonders why the testers are holding everything up at the end.

By: Chris Wash

Chris Wash — Mon, 26 Jan 2009 16:35:59 +0000

@Jason – Agreed. Again, I think it’s in the small stuff that counts here. It requires constant focus and attention to detail from not just a single person but everybody. There really isn’t a great way to get to that without getting the team ‘culture’ right.

By: Jason YIp

Jason YIp — Sun, 25 Jan 2009 03:23:28 +0000

I would tend to avoid “Everyone has a responsibility for quality” as a standalone phrase because, as you suggest, it doesn’t really lead to knowing what to do next. Instead if we think about how together we are are trying to design a system that has built-in-quality then whenever that system fails, it goes even beyond “Good catch – thanks!” to “Why did that happen?” and subsequent adjustment of how we do things.

By: Chris Wash

Chris Wash — Wed, 21 Jan 2009 21:35:11 +0000

Great point, Phil. Excellent example, right on – it’s the little things that foster the attitude needed to produce a quality product.

An outsider might consider it arrogance or competitiveness, at first glance, but we understand that’s not what it’s about.

By: Phil Kirkham

Phil Kirkham — Wed, 21 Jan 2009 15:32:44 +0000

Read this blog just after reading another blog with the title “Genuinely surprised when software fails?”

http://testmuse.spaces.live.com/blog/cns!FCF2D51D333DA1FD!355.entry

In it the author shows off his big red button from the 80′s “TEST then CODE” and relates a tale about how a dev would bet him a dinner that he couldn’t find a bug in his code. Mutual respect and improvement – just like you saying “Good catch”

By: Chris Wash

Chris Wash — Wed, 14 Jan 2009 07:47:05 +0000

Excuse, me, “Rays.” Anyway thanks for the comment.

By: Chris Wash

Chris Wash — Wed, 14 Jan 2009 07:45:58 +0000

Yeah.

If you aren’t aware, that’s relatively easy to deal with. If you don’t accept it or don’t care, aye, there’s the rub. Much harder.

That’s when the lead by example comes in. You just aren’t going to be able to inspire everybody individually. I think, if there is an answer, it has to get back to incrementally trying to improve and grow as team. Becoming the team that attracts good players (not buys them – think Devil Rays, not Yankees).

By: Andy

Andy — Wed, 14 Jan 2009 03:06:26 +0000

Good post, man; couldn’t agree more that “everyone has a responsibility for quality”.

Seems to me the challenge is getting team members who either aren’t aware of that responsibility, don’t accept it, or don’t care – to buy into the concept.