ERP implementations are massive undertakings with notoriously high failure rates. As a project manager, how do you set you and your team up for a successful ERP implementation?  

Based on our experience, we’ve put together a list of technical ERP project management tips. These tips are a good jumping off point for project managers to then add their own style based on the ERP system being implemented and the dynamics of the ERP project team.

8 ERP Project Management Tips

1. Squash Scope Creep Early

You might be thinking to yourself that this tip is project management 101. True, but have you ever experienced how quickly it can rear its head in a software implementation?

​Here’s a simple example of how something deemed out-of-scope can suddenly find its way into your ERP project plan: The statement of work (SOW) outlines that all accounts payable business processes are in scope for the project. A list of business processes is included in the SOW, and “settle vendor invoices” is a process that makes the cut. In the SOW, it is also noted that automated workflows are out of scope. Now imagine the team conducts an ERP requirements gathering workshop and notices that several of the requirements are related to workflow. These requirements are valid as they are required to complete their business process. The business analysts or ERP consultants on your team may go ahead and configure these requirements if the ERP software can handle the requirements.

What’s the issue here? While it is admirable of the team to configure the ERP system to meet the business requirements, what is not immediately apparent is the impact this has on the project timeline. Introducing workflow to the project scope now has added hours for testing and regression testing (see tip #4). This is why quelling scope creep early on is so important and can save you from being weeks behind on your project plan.

2. Be Realistic About the Timeline

The classic project management constraint triangle of scope, time and cost is infamous for a reason. One cannot increase or decrease a factor without proportionately doing the same for the others.

Unfortunately, since time is based on predictions of the future, it is usually the factor that is frequently underestimated. That said, when creating your project timeline, it’s important to be realistic about the schedule. If your project sponsors are adamant on having all requirements gathered in two months, but you have 12 weeks of workshops to get through, it’s time to have a reality check with your leadership to either increase the timeline or reduce the scope.

For many implementation projects, the need for more resources is common. However, adding more resources does not always solve timeline issues. In many scenarios, there are a handful of project resources (i.e., subject matter experts) that are required to attend all critical meetings. Just because there are four ERP consultants for a workstream, doesn’t mean that four workshops can be conducted simultaneously.

3. Build in Time for Regression Testing

Creating a timeline for software requirements gathering, design and development is fairly straightforward: You can estimate the complexity of a feature in terms of design and development, and based on this complexity, you can determine approximately how many hours or days of testing is required once the feature is delivered.

However, one element almost always forgotten when building the project timeline is regression testing. Regression testing is retesting all test scripts previously passed to ensure any new development has not impacted the results. Regression testing for ERP requirements can sometimes take even longer than testing the new feature itself.

Lately, there has been a trend of automating regression testing using predefined test scripts. While this automation may save you time in executing the regression testing, it’s still important include time in the project plan to build the test scripts to program the tool.

ERP Selection Guide

This ERP Selection Guide will help you select technology that will support your organization for at least the next ten years.

4. Use Templates for Design and Integration Documents

There’s a good chance that multiple team members will be writing design and integration documents, but only a few will review and approve them.

To bring some consistency to the reviewers and approvers, we recommend sticking to a standardized template for design and integration documents. This will allow reviewers to quickly review large documents and help them zero in on complicated sections needing extensive review. This also saves time for the authors of the documents, as they will be reminded of what elements to include, such as performance considerations, security requirements and test scripts.

5. Leverage DevOps Tools to Track the Status of Deliverables

A weekly, or sometimes even daily, requirement for ERP project managers is to report out the project status. Since project managers cannot possibly attend all workshops and meetings, the data for these reports are provided by other project team members.

Asking for daily or weekly updates from each member of your team is time consuming for all parties involved – the business analysts and ERP consultants have to set aside time each day to write up a report, and then you as the project manager have to combine all these individual reports.

However, if your project is leveraging a DevOps tool, you can simply extract the needed data on demand to put in a report. This eliminates the need for your project team to do double work since they will already be completing and updating their tasks in DevOps.

DevOps tools have become increasingly advanced when it comes to reporting. With some tools, you may not even need to extract the data as the internal reporting capabilities may suffice.

6. Build a Solid Cutover Plan

One deliverable often overlooked or rushed through during an ERP project is a cutover plan. A cutover plan is a list of activities required to prepare the production environment for end-user use. Examples of cutover tasks include loading user IDs into the system, kicking off batch jobs, connecting hardware components to the ERP solution and starting any integration services.

Cutover plans are extremely important as there are many tasks required to get an ERP system production ready, and many are dependent on one another. As an example, consider the task of starting integration services. Most ERP systems require a user ID to identify any records created or updated via an integration. However, if the user IDs haven’t been loaded yet, this task can’t be completed. Part of creating a cutover plan is to sequence all tasks in order of dependency.

Another key success factor in building a cutover plan is building it while the system is designed. During a six-month (or longer) ERP project, you risk forgetting activities if you wait until the month before go-live to create your cutover plan. It’s best to seek input from all team members throughout the project.

7. Set Expectations for Team Availability

Setting expectations up front with the entire team that there will be some weeks where the team works remotely prevents disagreements in the future. Ask your ERP consultant to provide a calendar of when they will be on or offsite so that critical meetings and activities can be planned accordingly.

It’s also important to establish a holiday schedule across all teams. Between your internal group, your ERP consulting partner and your ERP vendor, you may all have different holiday policies. This may seem like a trivial thing, but when it comes to supporting a live ERP system, knowing your resourcing capacity is crucial.

8. Schedule in Some Fun

Employee burnout is real. All work and no fun can really bring the morale of the team down, along with the health and motivation of individual team members. It might sound counterproductive to take time away from work to get out of the office and have some fun, but there is extensive research that happier employees produce better results.

In fact, team bonding activities can help break down barriers that exist in the workplace. Team members that wouldn’t normally interact can get to know each other and what their responsibilities are on the project.

What About Organizational Change Management

Many ERP project managers wouldn’t notice that organizational change management was left off our list, so if you did, you likely are way ahead of your competitors. Now that you understand the technical components of project management, you may be interested in one of our blogs about change management, such as How to Coach Managers to be Change Leaders.

Panorama’s ERP consultants can help your company manage the people, process and technology aspects or your ERP project. Request a free consultation below to discuss different project management strategies with our ERP experts.

Posts You May Like:

HRIS vs HCM vs HRMS: What’s the Difference?

HRIS vs HCM vs HRMS: What’s the Difference?

With the rapid pace of digital change in the HR sector, companies must thoroughly understand the variety of HR solutions available to them. Three options that many organizations consider include HRIS, HCM, and HRMS. Today, we’re breaking down the meaning behind these...

AI in the Pharmaceutical Industry: A Prescription for Change

AI in the Pharmaceutical Industry: A Prescription for Change

Artificial intelligence (AI) is reshaping the operational and scientific landscape of the pharmaceutical industry. As AI technology transforms drug discovery, development, and delivery, it’s also enabling operational efficiencies. Today, we’re sharing insights into...