Quality Standards

An aside prompted by studying for the PMI exam…

Isn't it odd that the term “quality standards” is common? A “standard” is voluntary by its very nature (ANSI goes so far as to say “voluntary consensus standard”) and is generally developed by mutual agreement. One does not have to comply with a standard but it is strongly encouraged. One hopes that complying with a standard would make a product compatible with another, but that's not always the case. I'll avoid the usual discussion of the “embrace and extend” strategy for now.

So, when it comes to specifying quality, one shouldn't call it a “quality standard” one should call it a “quality requirement.” A product or project must meet a specified level of quality to be acceptable. It's no wonder people often forget that quality is part of a project's constraints when changes have to be made.

Josh Poulson

Posted Thursday, Oct 26 2006 09:51 AM

Adjacent entries


« SEFORA Commercials





To track back to this entry, ping this URL: http://pun.org/MT/mt-tb.cgi/941

There are no trackbacks on this entry.


There is one comment on this entry.

Just try coming up with a quality assurance process for a program that has a lack of well-defined user requirements....

Good luck on PMP.

I did my CAPM a few months ago; I think they are the same except I don't have a degree yet so I couldn't go for PMP.

James G

Posted Sunday, Nov 5 2006 07:40 AM

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)



Affiliate advertising

Basecamp project management and collaboration

Backpack: Get Organized and Collaborate