Agile, DevOps & Testing: Methods: Tools Revisited

The sixty-eight words in the Agile Manifesto, written in 2001, revolutionised software development and also business in general. Almost every business sector is “doing Agile” in some form or another. But there has also been criticism of the approach and some have struggled and failed. Twenty years on, a recent survey shows a high level of Agile immaturity as it appears that the simple principles are hard to do well. One reason could be the uncertainty in the current work world, so organisations need to change the Agile ways of working and investigate how they adopt and use new agile practices. They also need to examine the practices of others and see the values that could be adapted to suit their particular needs. Based on that, they can decide and define their technical needs and methods.

The term DevOps is about eight years old, but it continues to gain momentum as big organisations have made validating investments in it. This isn’t exactly new. Many industry watchers believe it’s no longer a question of if your organization will adopt these practices, but when. And yet DevOps is still evolving, as are the tools and technologies that support it. DevOps encompasses a number of technologies that weren’t initially considered, but that have now become quite essential. Industry analyst Gartner says that this evolving discipline “demands a linked tool chain of technologies to facilitate collaborative change”. So, the question to you is “What will you be adopting?”

Testers have always been at the coal face of ensuring that “stuff works as it should”. Is there anything different in the actual testing of new digital products, new interfaces with clients which must always provide the optimum user experience? How are testers coping? What are the stories coming in? What is working well and what can be done better?