Wednesday, October 28, 2009

Mitton Street closure

My thanks to Steve for the heads-up on the forthcoming Mitton Street closure. Good job he did as although it made number 2 in the Shuttle's most read section, it's about to fall off the end of their first-page news section. Enjoy the justifications for this closure here

"Unforeseen circumstances" what a wonderful phrase; have you ever heard of work taking longer because of 'foreseen circumstances'? Something along the lines of 'We knew there were going to be problems, we just didn't bother to factor them into the plan?'

At least it's taking place during the weekend in much the same way the bridge work was done and at least, unlike the bridge (and Gilgal), there is a simple alternative route for normal traffic. So in that instance no harm, no foul.

However they're better put up signs in a more visible fashion than they have currently as once you head down into Gilgal or come from Harltebury with the intention of heading up Mitton Street there ain't nowhere else you can go. That means turning around and diverting through Kidderminster or the Holts. That means signs at the traffic lights and signs up at both the A449 turns and Wilden Lane.

Now Steve mentions the original plan talking about diverting traffic up Gilgal and down Vale Road if this eventuality came to pass or is he going mad? Hey I'm the only mad one allowed around here ;-)

Trouble is roadwork plans don't get published online I would expect some decisions to show up in the minutes, but nothing appears on the agendas for WCC in the obvious places or times. Oh and as of now neither WCC nor Balfour Beatty have updated the roadworks information to reflect the weekend closures. Also nothing on the WFDC page or the official Stourport Town site.


Dan H said...

"...have you ever heard of work taking longer because of 'foreseen circumstances'?"

Yes, in my industry it's more common than that not happening. Inexperienced managers refuse to believe that a project will take as long as the programmers say it will. Experienced managers may well believe it, but realise that if they say that long the project is less likely to get funding/approval. When the project is so late nobody can deny it any more, there's a meeting to pick a reduced set of functionality to fit in the time available. Again, the manager refuses to accept how long things will take, so the process repeats.

The thing is, the people who invest in or approve budget for software projects don't expect them to be finished on time anyway, because they've seen this happen before. The outcome is that everyone involved knew the project was going to be late, and the reasons are exactly the ones predicted by the programmers.

FlipC said...

heh okay I'll rephrase that "have you ever heard admitting that the work is taking longer because of 'foreseen circumstances'" ;-)