At HP Discover, we allowed the attendees of our session a preview of our new 6D methodology. Today, we’re formally announcing it to the world.
Those of you following my columns know that I have laid out in some detail how to begin building a Center of Excellence (COE) around performance testing, and centralizing it. Now I want to expound on three models that performance testing groups generally follow. Encapsulation refers to a silo approach. Enablement means allowing resources from other groups to self-govern their performance.
Up to this point we have separated the Mercury product from the concept of a Center of Excellence (CoE). Now what about this term? What does it really mean for IT and how can you implement this into your organization?
The first thing we have to do is separate the terms “Center of Excellence” from “Performance Center”. In the past these were used interchangeably , which may have been confusing. An “Center” is a product offering that would be used in a customer’s own Center of Excellence. Centers are considered to be product branding from a marketing aspect.
It is unfortunately clear that everyday more and more people enter our quality assurance profession with very little software architecture of engineering background to draw from. This is bad enough on the functional side, but is getting darn near catastrophic on the performance side. And, by the way, this is for all vendors, not just Mercury. It just may be more apparent here due to Mercury’s dominant market presence in this arena.
In 2002, after reviewing the new launch of the Business Technology Optimization (BTO) initiative by Mercury at their Worldwide User Conference, I had the same feeling as when I first heard about .NET or “web services”. It was supposed to change the world, but no one could really explain what it was. I could parrot what I had heard, but it was not a revelation to me. This year, at the 2003 Mercury conference, the clouds lifted and I see the light.