Effective Testing in Agile Environments

Publish date:

According to the research conducted for the World Quality Report, more and more organizations are pushed to think about updating and optimizing their testing resources to drive down costs and time-to-market. Most of the 1,500 respondents interviewed recognized that the overall quality of their testing resources must improve in order to satisfy increasingly complex business […]

According to the research conducted for the World Quality Report, more and more organizations are pushed to think about updating and optimizing their testing resources to drive down costs and time-to-market. Most of the 1,500 respondents interviewed recognized that the overall quality of their testing resources must improve in order to satisfy increasingly complex business requirements in the future. Testing departments need to get to grips with smarter testing practices to deliver measurable business value that justifies their spending. Some businesses that I have met with, particularly in the US and in Australia, started to recognize that this overall quality shift will require a transformational journey.
 
Agile software development methods are gaining wider acceptance despite widespread perception that projects can become less organized and controlled compared to the sequential waterfall processes. In the US for example, we’re now seeing 30-40 percent of projects developed in Agile, which is well on the way to the 60-70 percent figure that we expect to see in just a few years.
 
One of the transformational steps increasingly applied by firms is the integration of their developers with testers, where the latter shifts from being the protector of the business from significant software failures to transferring knowledge to the development team so that the responsibility can be shared.
 
We recently published a new book in our TMap NEXT® series developed by Sogeti, TMap NEXT in Scrum, which aims to shed light to the adaptation of TMap NEXT methodology to the Scrum approach. Even though it sounds like they would not suit each other, a structured testing approach can highly benefit agile environments. It can provide valuable insight into any risks that may arise in relation to the quality of the system and into how defects can be found at an earlier stage, or even how they can be prevented from arising. In our experience, it is especially necessary for testing to be fully integrated in the scrum approach for it to become as agile as possible. It can increase business agility, result in more effective planning and decrease time-to-market.
 
If you are seeking help on how to integrate testing into your Agile development, I would certainly recommend TMap NEXT in Scrum as a good read.

Related Posts

ADMnext

Engaging in Agile – the more the merrier?

Christo Martens
Date icon December 1, 2020

Here’s why adding the right engagement manager can help your Agile teams better focus on...

ADMnext

No nonsense Agile: Why true agility is simplicity

Rik Pennartz
Date icon October 30, 2020

When faced with increasing complexity, simplicity is still your key to agility

agile

Eliminating work silos to drive business value in your customer experience programs

David Salguero Kuiters
Date icon October 16, 2020

Introducing Agile within your (digital) organization means that new processes, practices and...