Let's say a server is down due to upgrades. It was originally going to be down for 10 business days.
The week after it is supposed to come back up, someone says we should know more next week.
Next Week; "we hope to have it running again next week"
The business can't wait for IT to keep saying next week, so it gets escalated.
Does anyone use a methodology that has written guidelines built in around timelines like that within your PMO's to prevent these kinds of things?
Where people understand timeline deliverables prior to escalation when issues present themselves?
Do you differentiate escalation between the business and IT? If so what does that look like?
IT PM's obviously don't want something to be escalated, but our job is to keep things on schedule. I look forward to your responses Saving Changes...
Sort By:
John DuncanRetired| RetiredLebanon, Tn, United States
Depending on what it's impacting, I would escalate it... The first step would be with the person doing the work, then that person's boss, etc.
In a nice way, and also in a business-like way.
"I thought this was going to be done last week, then I was told it would be this week. And now it's looking like (_maybe_) next week. The issue is going to impact xyz (cost, timing, etc.). How can we get a more firm commitment on resolving it, and when will it be resolved?"
(and how can we get better at this in the future...?) Saving Changes...
