What is it?: an IT project is sold and a delivery date is set. Now at some point during the project, people (the management, the client, the shareholder) realize that they might be better off if the deadline moves forward a couple of days or weeks, so it better aligns to other departments (finance, marketing, HR)...
Pros: better alignment, thus adhering to client's new constraints
Cons: greatly increased stress on project team (unless of course, the project can defer some of the deliverables to after the deadline)
The thing is, after this entire project ends and is handed-over, the message to the outside world is going to be that the project was completed on time and under budget. The subtext is of course, original time and budget.
And if you get deeper into this discussion, you end having to match every single deliverable to every single sub-deadline defined, and you have a huge mess. People generally just don't bother (unless they're auditing).
Now having a house built is cool. There's this acquisition contract that says the buyer pays for the material and labor costs, for an expected number of days needed to complete the construction. If the contractor goes over the alotted number of days, any additional costs are on his account. But, there's no deadline.
Mind you, this can only be done for mature projects.
No comments:
Post a Comment