Project Management

Please login or join to subscribe to this thread

ISO tips to avoiding testing burnout with agile...

linkedin twitter facebook  
avatar
Samara Richardson Program Manager| Social Security Administration Owings Mills, Md, United States
How do other agile practitioners avoid the overhead of having to regression test all of the functionality in a complex application (with web/mainframe/batch software) when there are never-ending builds of the Internet software on an almost daily basis... Users are conducting "acceptance testing" concurrent with validation and everyone's suffering from test burnout...
avatar
Russell Geake Project Management Consultant| Deciduous Partners Ltd Lostwithiel, Cornwall, United Kingdom
Hi Samara, how long have you been going with Agile? I think this is a fairly common trait among transition organisations - the idea of iterative development works well until you need to test the whole set of requirements. We've been improving our agile activities over the last 6 months or so...we've doubled the flow rate, but you're right, it's the bit at the end that glues it all together that is lacking and needs focus. There's no point developing at pace to be held up at the end ... likewise with beaurocracy.

You're not alone.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Nobody can make you feel inferior without your consent."

- Eleanor Roosevelt

ADVERTISEMENT

Sponsors