Agile Testing: Budgeting, Estimation, Planning and #NoEstimates
We’re a broken record when it comes to software testing. As we’ve made clear time and time again, testing is undervalued in IT. It is one of the most important steps in the software development process, yet it’s often a hurried step, in an effort to produce a final project. As Agile adoption continues to increase (which it will), it’s even more important to emphasize the value of testing.
But, testing is routinely overlooked, or organizations don’t understand how to prioritize testing within the frameworks in use, like Agile. This is what Tom Cagley, our VP of Consulting and Agile Practice Manager, spoke about at this year’s QUEST conference: How to utilize Agile in testing environments. He discussed the difference between budgeting, planning and estimation as applied to testing in an Agile environment – and when they make sense, when they don’t and in what combination for testing. He also explained the #NoEstimates movement and its role in Agile testing.
You can download his presentation, “Budgeting, Estimation, Planning and #NoEstimates – They ALL Make Sense for Agile Testing!,” here. If you have any thoughts we’d love to here them; just leave a comment below or contact Tom directly.