Skip to main content


How to implement agile testing on a non-agile project

Often, people think agile testing only can be implemented on an agile project. Actually agile testing is a set of engineering practices, and it can be implemented on any kind of project.

shutterstock_143577256For example, as a typical agile testing practice, test-driven requirements can be leveraged in any kind of project. Even for a traditional waterfall project, we can do test case/script development with requirement development in parallel. All unclear points for preconditions, scenarios, testing data will be found and clarified earlier. It is easy to help a team to make requirements ready as early as possible, and it will avoid a lot of costs caused by bad quality in the requirements.

Then which kind of agile testing practice can be leveraged for any kind of project? It will include but not be limited to the following:

  • Involves all members for testing, with special expertise contributed by testers
  • Testing from the customer perspective as early as possible
  • Test-driven requirement
  • Test-driven development
  • Pair testing
  • Automated regression testing
  • Continuous integration with automated testing

For those teams with less testing and automated testing experience, I recommend you try item 1, 2 and 3 first. Please feel free to try the left ones, especially automated ones, if your team has strong automation skills. You will gain value quickly due to automation.

I am not requesting that you implement all of above practices. But it will be very helpful to improve your project’s quality if you can try several of them. And I will post a separate blog post soon about those agile testing practices one by one if you are interested.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Follow Us