Can anyone share some guidance on appropriate contingency % for large ERP implementations?

Process Management
1.3k viewscircle icon2 Comments
Sort by:
Director of IT in IT Servicesa year ago

Personally, I'd recommend aiming for a contingency of at least 10-20% for large ERP implementations. This buffer helps cover unexpected challenges and ensures smoother project delivery.

1 Reply
no titlea year ago

I think 20% unless your organization is very process driven and have clear requirements.  Often there are overruns in these kinds of projects as people find out "Really it can do that?? Ok we want it..." Or worse, complementary features of the product and optimal process are overlooked as "they never did it that way before" . <br><br>Large ERP implementations are expected to be transformational.  Expect process changes.  

Content you might like

Which tool do you use for task automation at your work? Comment if you use other tool.

Zpaier14%

Make (Formerly Integeromat)31%

IFTTT17%

Other tool19%

I like to learn task automation14%

No task automation3%

View Results

How do you manage your enterprise content efficiently, and how is your organization (specific to content)?

Which tech conference do you intend to attend in person next year or have already participated in this year, and what motivated your choice?

Read More Comments

What's the most important friction in deploying Robotic Process Automation (RPA) in your company?

Cost of RPA products25%

Lack of developers who can code RPA applications43%

Amount of customization needed to automate business processes27%

Lack of RPA code maintenance resources4%

View Results

Digital transformation isn’t just about new tools, it’s about changing how teams work. Key lessons I’ve observed: 1. Start with process bottlenecks, not technology 2. Empower cross-functional teams 3. Measure outcomes, not outputs   What has been the most surprising lesson your teams have learned during a transformation?

Read More Comments