Skip navigation.

"Quality Architect"

perspectives
[textile]A colleague, Kerry Jones, brought "this article":http://www.theserverside.com/tt/articles/article.tss?l=ArchitectAppQuality to my attention today. It discusses the necessity of a role called "Quality Architect". I found it especially interesting since it describes a role that is similar to the one I fulfil on Agile teams or organisations adopting Agile methods (although often with the title 'Test Lead'). I don't entirely support some of the underlying emphasis on planning and design, but the general idea of the "Quality Architect" (translated to an 'Agile' environment) is a role that I can relate to. The author, Allen Stoker, affirms that
...large teams with diverse skill sets need a Quality Architect - a highly skilled technical person on your team who has no assignment but to support or 'enable' the other team resources. Such a resource can mean the difference between project success and failure.
Although Allen's article isn't backed by statistical evidence that such a role is the difference between success or failure, I could cite 11 years worth of anecdotal evidence that would suggest that he has a point.

I could be wrong but....

[textile]Brent Strange wrote:
I filled the Quality Architect role in a previous QA group
I could be wrong but I'm not sure that is what was meant by the original article. It isn't what I meant. The term 'team' is in reference to the entire project team, not a separate testing team. The role of the 'Quality Architect' in this context is someone who would be a peer to, say, a technical architect. This person would need broad skills in software processes, tools, approaches to testing, approaches to development and much more. That's what I meant by saying that I've fulfilled such a role. Antony Marcano

No assignment when..

"has no assignment but to support or ‘enable’ the other team resources"...I filled the Quality Architect role in a previous QA group I was in and my experience was that it definately was not a full time roll. With a team of 12 test engineers the role took up an average of 35% of my time. I totally agree this role is a must have when:
1. You have a team of test enginees greater than 8.
2. The QA Manager is so busy he/she knows little about the products you are testing, has little time to audit work, or even worse, isn't very technical.

Comment viewing options

Select your preferred way to display the comments and click 'Save settings' to activate your changes.