Skip to main content
Wednesday, October 2, 2013 - 11:30am - 12:30pm
Agile Testing

Working Testing Tasks into the Product Backlog

If you've worked on an agile project, delivering to production on a regular basis, then you've struggled with the challenge of fitting in all the big tasks—performance, security, usability, and compatibility testing. To make matters worse, over time it becomes more and more challenging just to fit in all the functional testing that needs to take place, and that's even with rigorous unit and acceptance test automation. So how do you fit all that testing into the backlog when it doesn't tie nicely to one specific feature? Michael Kelly explains that by writing specific stories for each testing activity and understanding when to coordinate the timing of those activities with overall project and iteration goals, you can make the testing tasks more visible and acceptable. Backlogs are where teams work out priority, scope, and set expectations for levels of effort. Make sure testing is a part of your project’s backlog.

Michael Kelly, DeveloperTown

A partner at DeveloperTown, a venture development firm, Michael Kelly spends most of his time working with teams to deliver ridiculously high quality solutions faster than they could without rigorous testing practices. Michael regularly writes and speaks about topics on software testing, and is a contributing author of two books, How to Reduce the Cost of Software Testing and 5 Minutes to Process Improvement Success.

read more