Agility and Quality Start with No Manual Test Cases
When I start coaching an agile development team, there are two anti-success patterns that I look for right away:
- Too many testers on the team
- Testers writing test cases to manually check quality at a later date
These traditional views of testing will break your agile journey, and there are powerful alternatives that you should be encouraging instead. Here is the manager’s guide to kicking off your agile development team on the right foot.
What is testing?
This might seem like a silly question, but you will be amazed at the range of answers you get. Before we can appreciate the role of good agile testers on a team and how we expect them to provide value, we need to align on how we achieve success.
Testing is not about finding bugs. It is a mechanism for rapidly aligning stakeholders and development team members with the desired customer experience. We call this alignment “quality,” and it is a fluid concept that shifts with time and each person’s needs.
The trick here is in understanding who your customers are, and clarifying their expectations. I have written before on how to identify your internal and external stakeholders, and some ways you might manage their expectations and needs throughout your development program. Testers are ideal people to track these stakeholders and their expectations, so they can provide you with
Please log in or sign up below to read the rest of the article.