Agile Testing Myths – Q & A

This content is syndicated from Agile Testing | Tester Troubles by Ray Claridge. To view the original post in full, click here.

agile testing myths"Agile is an excellent opportunity for QA to take leadership of the processes. Rather than take a back seat while developers drive the ship, testers can now take the lead".

"Who else is better placed to bridge the gap to understand … what is required, how it can be achieved and how it can be assured prior to deployment? This requires tester to be fluent in agile themselves".

With bold statements like these, I receive quite a few emails from testers with concerns about switching to agile. Continue to see TesterTroubles Q & A.

Do Agile teams need a dedicated tester?

Most definitely - Experienced testers bring something unique to the table. At the very least they: a) are familiar with methods and tools for testing that aren't strictly related to TDD. b) have spent a lot of time thinking about how to break things and where things might be likely to break. c) understand how to think about and communicate about quality.

How do I plan testing with no documentation?

In agile we do have less documentation, but to say NO documentation, is simply not true. Requirement Specs are replaced with a Product Backlog, Functional Specs are replaced with User Stories (bite size) and all other documentation is created as and when it's needed. As for planning your tests, hopefully you'll be involved in the requirement analysis process where you can include your test conditions that form part of the User Story.

I've heard that functionality and designs evolve during the sprint. If this is true, can I still use traditional step by step test scripts?

It is true that in some cases the functionality and design will evolve during the sprint. This would invalidate any step by step test scripts that you might of written. However, the key elements of the requirements should remain as captured in the User Story. With this in mind, I would suggest you focus on writing quality test conditions. If the requirements do change, it's easier to update these as you go along.

My tests are audited before the software is allowed to be release. How will this work in agile?

I suggest using a test management tool if you have a requirement to capture test results for audit purposes. As previously mentioned, this might not included step by step scripts, but should include the all important test conditions along with any data entered. Standard defect tracking tools are still used to assist your auditing.

Is it true that agile testers need to become more technical and fix bugs as and when they find them?

I agree tester should become more technical aware. As for fixing bugs, a tester could probably fix some minor defects (e.g typos). However, I still see this as a developer task.

I already work as a tester in an agile team, and in every sprint the developed code is only released to QA with a couple of sprint days remaining. What changes can be made to improve the process?

You need to ensure the user stories are passed onto QA as soon as development is complete. If you find there's never enough time to complete all the test tasks, you could enforce a code freeze before the end of the sprint and get developers to assist you with your testing. Remember, QA in agile should not just be the responsibility of the tester but all of the team. As long you manage this correctly, I can't see this as being too much of a risk.

How do you see the role of the tester changing?

The role of the tester is still crucial to development success. However, I believe the analytical skills of a tester will be used more as agile matures, where they're involved in the requirement capturing process. In smaller teams, I can see the tester role evolving into a hybrid one where QA, product and project managing become one.

Leave a Reply

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

5 × four =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch