The Agile path is clearly set for the industry as a whole; it’s taken a while for Agile to penetrate the market and improve the upstream part of the application development life cycle, but it’s not going to take that long to get Agile to improve. We have gathered four articles you can read on the future of Agile testing and where it’s heading.
Testers, pay attention.
1. How Agile Testing Can Prevent Project Failures
Many of us can remember the technology projects that were embarrassing to say the least, like Windows Vista and Google Wave. Have you ever wondered how these projects could have been salvaged? Is there something that could have saved these projects? To have a definite answer, you have to look at the drawbacks of traditional project management and testing methodology.
The testing phase should begin as early as the development life cycle. It also involves the customer and begins testing code as soon as it’s available. This is essential for two reasons:
- It prevents the loss of time caused by expectations
- It keeps development on track with the big picture
To get a better idea of successfully implementing Agile testing, this article looks at the phases of Agile testing, the benefits and why you should stick to Agile testing in the first place.
Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. His blog was awarded the UK Agile Award for The Best Online Publication in 2010.
Most of his articles focus on Agile testing. This post in particular, looks at the need to change the Agile testing quadrants in order to clearly outline the separation of business-oriented tests and technology-oriented tests.
“The Quadrants don’t fit well with all the huge changes that happened in the last five years, including the surge in popularity of continuous delivery, DevOps, build-measure-learn, big-data analytics obsession of product managers, exploratory and context driven testing. Because of that, a lot of the stuff teams do now spans several quadrants. The more I try to map things that we do now, the more the picture looks like a crayon self-portrait that my three year old daughter drew on our living room wall.”
James Bach calls himself the consulting software tester and in this post he talks about the power of looking. Simple as it may sound, Bach emphasizes that most testers don’t watch their check as it runs. Bach decided to do the opposite, watch his output flow.
“As I watched the output flow by in this particular example, I noticed that it was much slower than I expected. Moreover, the speed of the output was variable. It seemed to vary semi-randomly. Since there was nothing in the nature of the program (as I understood it) that would explain slowness or variable timing, this became an instant focus of investigation. Either there’s a bug here or something I need to learn.”
There’s a lot of people talking about Agile 2.0. But when you look at what’s happening in the application development and delivery space, you see that many organizations are just now starting to experience Agile’s true benefits. However, they are not leveraging the benefits completely or consistently.
Diego Lo Giudice’s blog, a Forrester analyst serving Application Development and Delivery Professionals, looks at the need to stop talking about Agile 2.0 and start focusing on what the current Agile process brings us today.
“What I see is that app-dev leaders want to understand how they can optimize existing use of AD&D Agile practices like Scrum, XP, Kanban, improve the practices around the more advanced ones like TDD, continuous testing, CI and CD and leverage all with what they’ve learned over the years (including waterfall). Scaling the whole thing up in their organization in order to have a bigger and more consistent impact on the business is what their next key goal is.”