Overcoming Agile Testing Inertia with Mind Maps
Imagine you need to run a race or obstacle course. Now imagine that you were told that every step you take requires that you come to a full and complete stop. While possibly highly entertaining to watch, it will be frustrating for the runner who knows they won’t be winning the race.
That’s what I see when teams transition to agile development and the QA/testers continue to follow the same testing processes and tools they used before joining the agile team. There are two general reasons we see this recurring failure-inducing anti-pattern:
- Management expects and demands that the testers continue to work the same way as before so that they can continue to get their reports on the quality of the system in development. 
- The testers don’t know any other way of doing things, so they do what they did before they joined an agile team.
In this article, I’ll contrast agile and traditional testing. And then, I’ll give an example of how a mind map can facilitate the testing process.
The Heart of Agile Testing
Change is difficult. It takes time to build trust in new approaches. It is all too common for companies to continue doing testing the same way even though the business and developers are changing everything about how they work.
Please log in or sign up below to read the rest of the article.