The QA process in agile differs greatly from QA in traditional testing, such as in Waterfall. Agile has changed the way we think of software quality. In fact, I have read rumblings in the blogosphere that Agile has killed QA. I promise you Quality Assurance is alive and well on agile teams. It just looks different than what most of us are used to. I think people who have promoted the “death” of QA in agile are not looking closely enough at what is really happening. Traditionally, testing was the only task people associated with measuring quality.
Once again, I have the pleasure of welcoming October. Soon it will be cooler and more colorful here in North Carolina. The holidays are coming, and many of my neighbors have already decorated for Halloween. I have been pondering what sort of ghoulish surprise I could cook up this year, and decided to go with one of my favorite creatures… ZOMBIES! Nothing says horror like a good old zombie movie (or TV show), and nothing brings misery to the otherwise happy-go-lucky people that I work with than Zombie Scrum.
There is some confusion around what agile is versus what agile methodologies are, and often people lump them together. Agile is a mindset (not a methodology) that encompasses a set of values and principles that were compiled by a group of software gurus in 2001. These values focus on customer collaboration, flexibility, a short iterative cycle, value delivery, people centricity, sustainability and simplicity, among other things. These values and principles are not to be confused with the frameworks that have been developed to assist teams in “becoming agile.”
I love my wife. No big surprise that I would say that publicly, on the record. We have been together for over 32 years, have 3 amazing daughters, and have managed to partner with each other through the good and bad times. Valentine’s Day is a great time to reflect on our great loves, smell the roses, and consume copious amounts of candy. When I think of who and what I love, I have to put Agile on the list, not so much because it pays my bills, but because it contains a lot of concepts that have made my best relationships possible. So, for the sake of this blog “agile love” is a real thing.
Once upon a time, in the land of Waterfall, the business analysts wrote the requirements, the developers coded the requirements and the Testers tested the requirements. Each of these people sat in his/her ivory tower, um, silo and did that which they had always done since the beginning of time. Quality was thought to be synonymous with testing, and therefore was considered to exist solely in the Tester’s realm.
Are you an experienced tester who has recently joined an agile team? Maybe you have testing experience but until now it has only been on traditional waterfall projects. Are you going through the motions with this new way of doing things but don’t feel like you’re completely invested? Do you even feel like you’re adding value to your team?