ERP Business Blueprinting: How to Resolve Schedule Overrun
Since the 1990s, several ERP implementations have been completed across industries. However, organizations still run into many challenges. One of the key success factors is to ensure a project is completed on time and thus avoid schedule overrun. In this article, I’ll introduce an approach for handling issues related to project timeline and then illustrate a concrete case on utilizing this approach in the business blueprinting phase.
“Delivering a project isn’t difficult. What’s difficult is delivering a project without first taking the time to plan properly.”
-- James Leal
The proposed two-step simple approach is:
- Identify prospective issues that can impact the project timeline.
- Perform advanced detailed planning so that the expected issues are addressed.
The next few paragraphs will provide a concrete case of how this approach can be used in one of the key project activities--business blueprinting, where probability of occurrence issues impacting schedule is very high.
Any ERP implementation project has five main phases--planning, business blueprinting, solution build, testing and training--followed by go-live activities. Successful conclusion of business blueprinting activities is quintessential for building the precise solution for business users. The business blueprinting phase can be categorized into four
Please log in or sign up below to read the rest of the article.
|
"A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty." - Winston Churchill |




