Monday 5 January 2009

Damming/damning the waterfall

The conversion is hitting its first snag - the backlogged projects are clogging up resources and making it impossible for us to "get finished and move on." My group (QA) is the one that's most committed for getting work finished up so it can make it out the door - and with everyone split up into their new teams I'm suffering from not being able to pick up spare resource (usually found when a project had been held up for one reason or another) and drop it into another one to help it get finished up.

It's looking like the projects that we were "committed" to finishing before we transitioned to Agile are going to be holding up our transition, in part because over the month of December none of them managed to get deployed slash handed off for testing. (Rumor: QA is the bottleneck. Truth: just because we haven't tested it doesn't mean we're being slow or holding things up!)
The other option for managing this is to somehow shoehorn them into Agile, but what's bad about that is that it will guarantee they're delivered far later than promised (always our problem - there should never be these promises!) and that the people who have been working on them aren't available to do so (as they're on different teams), which will lead to a big flustercluck of trying to do handoffs and dealing with Ye Olde Learning Curve. Bleah. Time to hit the box of Vosges Haut Chocolat.

No comments:

Post a Comment