Talk to a real, live person

Complete the simple form to the right, and one of our professional consultants will be in touch. You’ll get free consultation with no obligation to purchase anything.

Or, call us toll-free

If forms aren’t your thing, just give us a call at
888-920-2784.

Contact us for a FREE Evaluation

Sending  

Contact request successful. Thank you.

We will contact you within 2 business days.

 

Blog

Your source for insightful information that's relevant to you and your business community.

Jun
4
2010

3 Keys for ERP Project Success

With the right approach, your plan can translate the business case, operational requirements and project objectives into a successful ERP project. The plan then identifies the potential ROI, business requirements, project scope, effort and solution recommendations.

But a recent study by the Gartner group found that almost 65% of all IT projects failed to meet the goals of the sponsoring organization. These failures included project cost overruns, missed deadlines and a failure to achieve the ROI as planned.

How do you produce project success?

A successful ERP project is one where the business goals are achieved, the project costs are within budget and the “go live” dates are met. It is created with a “top down” approach for the business issues and augmented with a thorough “bottoms up” operational review that involves the process owners within the organization. The result is a blueprint for both the ERP implementation and project success.

The Three Key Steps in Successful ERP Planning:

  • Start with an Executive Visioning Session to define the business case, ROI and project goals
  • Perform an Operational Review with process owners to detail operational and business requirements
  • Conclude with an executive and project team review of the detailed findings

With well over 1,000 implementations to date, BroadPoint has developed and refined a methodology for ensuring that our clients are among the 35% that achieve project success.  So what’s our definition of project success? A successful ERP project is one where the business goals are achieved, the project costs are within budget and the “go live” dates are met; and finally, where we have delighted the client with our service.

The Executive Visioning Session

Successful ERP project planning starts with an executive visioning session. This is a “top down” driven process involving both the senior executive stakeholders within an organization and the ERP project team. Typically this would include the CEO, CFO, CIO and appropriate IT or operational staff that will be involved in the project. The goals are simple--to identify the business case and objectives for the ERP project. The planning is typically done in a morning session and is led by a facilitator. 

The session focus is on the following critical factors:

  • Project goal alignment within the various stakeholders
  • Identification of the business case and drivers for the ERP project
  • ROI Golden Triad (Return on Investment) review
  • Increased staff productivity
  • Better decision making
  • Increased revenue or improved gross margins

A key tactic for a successful Executive Visioning session is to put technology last. A skilled facilitator has both deep business experience and technical knowledge of the software. By focusing on teasing out the business issues and not the technology, we can develop the broad business case for the project.

The Operational Review and Business Analysis

The next step after an Executive Visioning Session is to perform a detailed Operational Review and Business Analysis. In this step, all of the major operational requirements are discovered using a “bottom’s up” approach. BroadPoint’s process for this critical step is to facilitate a series of joint sessions with the appropriate operational staff or process owners and the organizations ERP project manager. It is critical in these sessions to first understand the business requirements and process for a given operational function. Later we’ll perform a gap analysis to compare the project requirements against the out of the box functionality of the considered software solution.

This expertise is used to guide the discussions with the process owners so that key requirements are discovered. The operational review can include:

  • Discovery sessions around strategic operational areas
  • Detailed “day in the life” review with key process owners to identify hidden requirements
  • Confirmation and alignment of the business drivers identified in the Executive Visioning Session with operational realities
  • Comparison and gap analysis of business requirements vs. the considered technology’s out of the box capabilities

The goal of this step is to identify all of the critical business requirements and to do so efficiently. This step may be anywhere from a day to a week depending on the complexity of the solution being considered and the maturity of the business processes being analyzed.

ERP Project Findings and Review

Once the Operational Review is completed, a Project Findings document is prepared.  We’ve found that the results of the Executive Visioning Session create a strong foundation for the Operational Reviews. These in turn result in a Project Findings document that creates a blueprint for project success by aligning the ERP project recommendations with the business case, ROI project goals created in the Executive Visioning Session. 

Once the ERP Project Findings document is completed, typically within ten days, it is presented and reviewed with the team that participated in the Executive Visioning Session. The discussion and Findings document include:

  • Business case and drivers
  • Discovered business requirements
  • Software gap analysis and recommendations
  • ROI confirmation
  • Solution recommendation
  • Project scope, time frame and effort estimate

A Proven Approach to Implementing a New ERP System

Hundreds of organizations have successfully navigated the implementation of a new ERP system using this approach. Effective planning plays a key role in ensuring a successful deployment of any new technology solution. By bringing together the business case, operational requirements and project objectives, an organization creates the foundation for an ERP project plan. Finally, by using a “top down” approach for the business issues and a “bottom’s up” review for the operational requirements, the result is a blueprint for both the ERP implementation and project success.

Sending  

Thank you.

eNewsletter sign-up successful.

Sign-up another person.

Done.

Posted by Lee Raesly on Fri - Jun 04, 2010 at 10:26 am EDT

Total of 0 comments.

Commenting is not available in this channel entry.