Making the Leap into Agile Testing
You think you have a handle on how to deliver your projects. Super. Then Bam! A mandate comes down that your development team is “going agile”. This is an understandably scary proposition for some people.
The illusion of control and order from traditional waterfall-style projects is over. Let’s be honest: those R&D projects weren’t always orderly at release time, right? I am here to tell you some of the ways how your world of testing is about to get turned upside down. The sooner your team and management let go of the past, the more quickly everyone can progress through their transition to the next level of performance.
Researching the agile world, we may find there are a lot of references and practices for some aspects of development--and scarce or conflicting information for others, such as testing. At an initial glance, going agile may sound like a half-baked idea. When you dive deeper, however, the world of agile development is rich and full of answers to questions you may not have thought about yet.
I am asked many questions on the topic of agile and testing. Some common and key ones include:
- What does “quality” mean since the Agile Manifesto doesn’t seem to use the terms “quality” or “testing” anywhere?
- Do testers need to learn programming skills to do agile testing?
Please log in or sign up below to read the rest of the article.