Agile test curve
This post is an update to my original post Testing Curve. I've had a few emails asking for a more detailed graphic and some advise on avoiding the unheathly test curve.
Don't allow test debt to build up in your Sprints. Start testing as early as possible. Tips on how to avoid the unhealthy test tidal wave;
As a Team
- Have smaller size stories in your Sprint backlog. Never, ever play an Epic.
- Use BDD to capture all test scenarios, this will help the tester test the right area's as well as the edge cases.
- Automate as much of your testing as possible, reduce the testers manual efforts.
As a Developer
- Manage your WIP; complete a story before working on another so that you release a story for testing sooner rather than later.
- Minimise bounce back in Sprint. Run unit tests to ensure that the testers are testing on test ready code.
As a Tester
- Prepare your test environments at the beginning
- Look at the team task board to see what is going to be ready next for testing and make sure all test cases are in place.
Reap the QA rewards by reducing defects
Reducing software defects has huge rewards for a business. I recently put together a slide on the commercial benefit of reducing defects, to quantify this as a cost to the business I put together a simple demonstration on the cost to the business.
Base
- £58 p/d
- 10 incoming defects p/w
- 2 days per defect to fix
If you reduce the total incoming defects by 40% in the first year you'll save just over £22k, but it is completely feasible to achieve a 99% reduction in your incoming defects and your saving would be £55k p/a.
Any managers reading this will be over the moon, but the developers / testers and release managers will be scratching their heads @ how to achieve this. Defects only occur if you allow them to escape in the first place, look at your testing strategy, automate as much of your testing as possible, achieve continuous integration and aim for continuous delivery. Achieving a 99% reduction would be easier in some environments than others; i.e. a web application is going to be far easier to drastically reduce the incoming defects than a legacy installed application on the desktop (as you may not have the capability to upgrade / update desktop applications as frequently).
I specialise in all things Agile (XP, Kanban, Lean), in particular Scrum. I have a passion for taking on 'problem' projects / teams and turning them into a sucess as well as promoting automated test driven practices.






