The Music of Agile Testing
Agile testing is commonly mistaken as only referring to the Quality Assurance (QA)/testers on the team. This is a destructive, limited view of this critical agile development piece. That’s why when I conduct my workshops on testing, I always start with the basics:
- Testing is based in the Scientific Method
- People need to collaborate for testing to be most effective
The first part we learned in elementary school. We need gentle nudges to help us recall how to think clearly, scientifically, about how to learn from systems of things. The latter part is trickier and goes against everything we learned in school about independent work. That is, in school we are taught to do our own work independently--or get punished as cheaters. In the real world, that is a recipe for disaster. It is only through collaborative pairing of minds and perspectives that we can hope to succeed in delivering quality products and services in a timely manner.
Great testing requires a whole-team approach. So when I talk about “agile testing”, I think of all the activities that every project team member does to ensure their customers and users are more than happy with the value received. This article places the emphasis on the often neglected, misunderstood and essential collaboration piece.
Symphony or Cacophony?
Development work involves layers and layers of
Please log in or sign up below to read the rest of the article.