Problem solve Get help with specific problems with your technologies, process and projects.

Managing software testing processes on an Agile development team

In Agile development, testing processes are addressed by the whole team, according to Lisa Crispin. In this expert response, she highlights techniques for teams to work together to improve their testing and QA, including story mapping and Community of Practice approaches.

What differences between traditional and Agile development are there in the way testing processes are managed?

In Waterfall development, testing is a separate phase done by a separate test or QA team. A project manager or PMO sets standard processes for the whole SDLC that guides everyone in the project. The testing or QA manager establishes the testing processes, and ensures that everyone follows them. Since development cycles are long, the testing processes may only be revisited and improved once or twice per year.

In Agile development, testing is an integral part of software development and is the responsibility of the whole cross-functional team. Testing comes first in Agile development. When teams plan a new project, theme or user story, they start by thinking about how they’ll test the new features. Then they design the code around making the tests pass. There are testing experts on the team who help everyone get a better understanding of ways to do a good job of testing, but all team members are responsible for delivering a high-quality software product.

In Agile development, the whole team addresses issues with the testing processes. This is often done via iteration retrospectives, where obstacles are identified, along with experiments to try to overcome those obstacles and improve the testing process.

For example, if testers are finding a lot of unit-level bugs in the “finished” code, the team might decide to have programmers and testers pair to test the code before checking it in. Or, perhaps the team finds that the customers aren’t happy with the delivered code, it doesn’t really meet their requirements. The team will brainstorm ways to do a better job of working with the customers to really understand the features they need and the business problems they hope to solve. 

Recently my team worked on a theme during which we discovered many features or items had been left out, new user stories had to be written and done. To try to prevent so much unexpected work, we decided to try story mapping, a hands-on way to get the development team and all stakeholders together to model a theme or project and slice it into user stories. We learned a lot from this effort.

A testing Community of Practice is another good way to help a development organization continually improve its testing practices. This is usually led by a test or QA manager. Everyone interested in testing participates in workshops, lunchtime demos and other activities where people from different teams share their testing processes and new techniques that work for them.

Next Steps

Leverage personality to improve software development processes

Dig Deeper on Topics Archive

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Very solid tips. I work in QA on an agile team. At my company, we have not had anyone in a QA or test management role in a couple of years now. We also recently delivered a project during which we were constantly realizing that we were missing pieces of work. I feel like this was a result of QA and stakeholders not  being included earlier in the theme planning. What is a respectful way to insist that QA as well as stakeholders should be included in a story mapping the next time a project is coming up?
Hi Abuell, Thanks for the feedback. This is a great question! I'll see how many expert answers I can round up for you and the rest of our readers.