I'm managing a software project and our management decided to go with new version, which was not communicated before and will derive to change some significant deliverables.
The most important thing is what is the best practice to communicate the change with the customer as it was contracted with different deliverable.
Thank you.
How to Deal With Scope Change
-
begeland
First let me see if I'm understanding the situation correctly. You have a project with a customer based on one version of software/technology and the deliverables that are associated with the project. Your management has implemented a new version of that software or technology and it's affecting your project as such that you'll need to make changes to the customer deliverables or add new ones, meaning more work, time, and costs to the project, correct?
If there is some significant benefit to the customer as a result of this new version, then you may be able to create a change order documenting the benefits and getting them to pay for some of the costs. The probably right thing to do, though, since it was all initiated by your management and not part of the original project, is to do the extra work for the customer for free. You should still document it all in a change order since it is a change to the original requirements of the project. However, there would be no costs to the customer associated with the change order...they would just need to see it, approve of it, and signoff on it so that they show they acknowledge that the work is being done, that it needs to be done and that they aren't being charged for it.
Let me know if I'm understanding this correctly. Thanks!
Brad Egeland
If there is some significant benefit to the customer as a result of this new version, then you may be able to create a change order documenting the benefits and getting them to pay for some of the costs. The probably right thing to do, though, since it was all initiated by your management and not part of the original project, is to do the extra work for the customer for free. You should still document it all in a change order since it is a change to the original requirements of the project. However, there would be no costs to the customer associated with the change order...they would just need to see it, approve of it, and signoff on it so that they show they acknowledge that the work is being done, that it needs to be done and that they aren't being charged for it.
Let me know if I'm understanding this correctly. Thanks!
Brad Egeland
-
RobertBell
- New Member
- Posts: 1
- Joined: Fri 12 Jul 2013 4:37 am
Hi Jim,
I recently wrote an article on how to deal with scope creep. I hope it will help you out in your situation. Here is the link:
http://cobaltpm.com/how-to-avoid-scope-creep/
Take care,
Robert
I recently wrote an article on how to deal with scope creep. I hope it will help you out in your situation. Here is the link:
http://cobaltpm.com/how-to-avoid-scope-creep/
Take care,
Robert