This is the 6th and final blog in our series offering guidance to help you be better prepared for your ERP implementation. In this blog, we highlight the importance of avoiding scope creep.
What is scope creep?
Implementing a new ERP can be very exciting. And so, it should be. You are, after all, making changes for the better.
As your project progresses, your knowledge of the new system will grow. You will inevitably learn of features and capabilities that were not incorporated into your requirements at the start of your project.
It’s easy to let excitement get the better of you and try to move the goal posts mid project. As your knowledge grows, you may be tempted to expand project scope. Individually, the impact of each of these changes to scope may be small – an hour here, an hour there – but collectively the impact can be big. So big that it threatens the agreed budget and delivery timetable.
This is scope creep.
If it’s not in the Solution Design Document…
Early in your project, during planning and design, we will agree and document your requirements based on listening and understanding the key project drivers and desired benefits. We also map out the project and clarify the resources that will be needed to deliver successful outcomes. Everybody benefits from the clarity these documents provide. They set expectations. They clarify when budget will be needed. They help avoid nasty surprises.
There is nothing wrong with identifying new requirements. Indeed, it’s great that you can see possibilities for further development of your system. It’s just that it may be prudent to deliver those requirements in a later phase. Trust is very important. Don’t risk that trust by shifting goal posts. Review all proposed changes carefully and openly and either admit them with corresponding changes to budget and timescales or defer them into a second phase of work with its own budget, plan, and project deliverables.
Take the next step
Thank you for reading our six top tips for a successful ERP implementation. To learn more, please download a copy of our SAP Business One Implementation Guide or SunSystems Cloud Implementation Guide.
By Edward Bentley