About the Blog

  • Software is our business, and perfecting the art and science of delivering it is our mission. The contributors to this blog are passionate about the impact that great teams and good software can have on an organization’s bottom line. They bring decades of experience designing, developing and delivering great software, and each is playing a critical role in Borland’s own transformation.

Blogging Authors

« What's missing from the Agile manifesto? | Main | Bootstrapping a Transition to Agility: Looking for a place to start? »

November 26, 2008


Feed You can follow this conversation by subscribing to the comment feed for this post.

Michael Maham


For a long time I heard many QA professionals insist that they were not "just testers" but that Quality Assurance also included things like ensuring the projects were following the proscribed process. While good, in theory, it set QA up as the "bad cop".

Like testing, whether we're doing our work the way we said we'd do it (also known as following our process ;) ) is the responsibility of the whole team. If your process needs outside enforcement, it is probably a bad sign! Of course, this means you need a highly disciplined team (as mentioned here http://borland.typepad.com/agile_transformation/2008/11/whats-missing-from-the-agile-manifesto.html) that includes good "QA specialists"

The comments to this entry are closed.