If you're like me you hate to give the project customer bad news. Especially if things seem to be going well on the project. If they aren't, then what's one more bit of bad news? You can probably just
Scope issues = be careful
However, when you play with scope issues then you are definitely playing with fire. Why? Because scope issues can have such far-reaching and devastating
One change order can make a big difference
So many things can
The moral of the story
So what's the moral of this story? Yes, it only takes one change order. We could see how it was only going to take one big giveaway piece of work to throw the budget off by another 14% making it a big failure financially. And then we saw how the project manager who wisely documents the needed change, creates a change order for that work and gets the change order approved by the customer actually raises the budget for the project and brings it in only 8.7% over and turns it into a success sorry. Don’t be afraid to manage scope closely and put change orders in front of the project customer for approval. You can be nice and fail, or you can be proactive, wise, and a good leader and succeed. You choose.
Choosing the right tool is crucial for the success of your project. Telerik TeamPulse allows you to define the scope of your
A Business Solution Designer and IT/PM consultant and author with over 25 years of software development, management, and project management experience leading initiatives in Manufacturing, Government Contracting, Gaming and Hospitality, Retail Operations, Aviation and Airline, Pharmaceutical, Start-ups, Healthcare, Higher Education, Non-profit, High-Tech, Engineering and general IT. Brad is married, a father of 9, and living in sunny Las Vegas, NV.
Subscribe to be the first to get our expert-written articles and tutorials for developers!
All fields are required