Quality Assurance. That is a set of interesting words. Many companies use us as 'assurance' engineers. "I assure you this won't work." Then we hear the famous words of "The business accepts the risks." However, when it all breaks, the QA team is blammed, perhaps the developers as well. Something is missing here, something is radically misunderstood.
A simple question is being answered incorrectly, 'Y Agile?" It is written that way for a reason and we will discuss how something so simple is actually very complex. It involves more then process, it is a culture, a generation of people, a morale compass and a set of core beliefs that drive us, or should. When a company adopts the 'silver bullet' of agile, know that a bullet causes damage but with a purpose. What is the damage it can produce, what is the goal, how does it affect customers and business relationships? When we know all those points, we test differently. Quality takes on a new meaning, it takes on the view of the customer which is the power behind every contract, every dollar spent and every failed business. Let's examine 'Y Agile' and see how our beliefs needs to change.
Michael Swansegar currently filling the roles of a Product Manager and Agile Trainer. Michael has over 12 years in IT infrastructure support followed by years in QA and finally Product Management. All along the path he has been trying to answer some simple, humorous and realistic questions going role to role:
1. Why did we ever release this piece of garbage we call a 'product'?
2. Why did we think a customer would want something broken followed by patches?
3. Why did we build to our internal opinion when it is the external customer that pays the bills and defines value?
Michael has a few simple yet critical beliefs:
1. A paying customers is not to be confused with a loyal customer.
2. 'Why Agile? -- The answer is the question.