ERP Implementation Manifesto

 We follow these principles:

40 thoughts on “ERP Implementation Manifesto

    • Hi Wanda – please go to my blog: and look under the “Book” menu. This will provide you a link to my publisher and the ISBN #.

      Special request: If you could navigate through my blog and let me know how you like the experience then I would appreciate it. I’m always looking at making it better.

      Best Regards

  1. Hi Brett, great work. I love how you’ve adapted the principles of the agile manifesto into your own ERP implementation principles.

    I wrestle with similar challenges when implementing CRM solutions for my clients. Especially, the value of sticking to the ‘out-of-the-box’ funcitonality.

    My opinion is that customers should stick to the standard features where it makes no difference to their competitive advantage. Where they manage a paticular business process in such a way that it gives them great advantage, then they should customise the system as much as needed in this area to support their competitive process. Make the customisation investment where it will lead to the greatest returns. Don’t just try and avoid all customisation otherwise any competitor can catch up with you by spending as little as you.

  2. Thank you Neil. I’m very fortunate to be able to leverage existing work from great experts like the SCRUM/Agile community. I recently published a book where I provided guidance on where to find areas for value-add software changes (what i call enhancements) versus non-value-add software changes (what I call customizations). There are times were I need to work with customers to identify true competitive practices and respectfully challenge existing requirements (i.e. do you really need to be competitive in a revenue-supporting business process?)

  3. Hi Bret,

    thankyou for contributing and sharing your well thought article. I like th econtent and relevance.

    Good job.

    If any of your listeners sould like to see what you shared I want to share with you also.

    Thanks again. Good to hear from you..


  4. John Belden says:

    I would suggest 3 additional componets to define a viable business process: quality data to fuel, compliance assurance and capacity to support and advance. Great points in the article.

  5. This is the latest trend that is fast catching in the ERP domain. Tier 1 is basically the legacy app used at corporate level whereas tier 2 is modern ERP implemented at subsidiary level. During the early ages of ERP evolution, businesses faced heavy loses if the ERP system failed. A two-tier ERP model prevents total failure and enables businesses to adapt better. Some use cases for two-tier ERP

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s