A couple of weeks ago, I addressed the importance of your PLM requirements document. In that blog I did mention scope creep, but it deserves more attention.
One result of your PLM requirements document should be a project plan. The project plan will have a time frame. Let’s assume for a moment that you did a pretty good job with your plan. You will have a start date and a finish date [I suggest a target of 6 months or less].
Without any changes to your project plan, you will:
– Finish the project on time
– Finish within budget
– Maintain employee enthusiasm
– Receive kudos from management
With changes, you will likely encounter any or all of the following:
– The project will not finish on time
– The project will go over budget
– Employees involved in the project may get frustrated
– Management won’t be happy
– Warning, one disgruntled employee can sabotage an entire project
The longer a project takes; employees will begin to lose enthusiasm. Enthusiasm is the glue that keeps the project on track and increases the chance for success. Management will begin to lose patience as well.
Reality says that you may not have thought of everything needed in your project plan. Keep the changes minor so that the project can finish as close to the original time as possible.
A project roll out on time (or near to it) is important. Management will be watching the project from the 20,000 foot level and will see this as a success. Your second project can be to clean up what you missed in the original plan. Your initial success should help you get support for the clean up (polishing of the solution). Everyone should be on board by now, so the clean up should be easy.
Success on this project will make getting support for the next project much easier. As Captain Picard would say, ‘make it so’.
Contact me if you would like some help…