How to manage ERP project

Enterprise resource planning incorporates all aspects of a business into a single software package. Changing ERP software will impact all phases of a business, so managing the project successfully is a key goal. Other goals include ensuring that the business can adapt to the change and ensuring that the new software doesn’t impede productivity. Managing an ERP project requires detailed planning and research. You will need to analyze all aspects of the company’s operations to see how the software change will affect the way they conduct business.

Difficulty:

Challenging

Instructions

Things You'll Need

• ERP project plan

1. • 1
     Enter milestones into the ERP project plan so that you can view the software transition in its entirety. Add specific time frames and task owners for each milestone.
   • 2
     Define measurable metrics for hardware and software and include them in your project plan. Determine the project's technical requirements and add tasks to the plan to ensure that the requirements are met, tested and online prior to the ERP software going live.
   • 3
     Define and map the static and dynamic files that will be converted during the ERP implementation. Static files include products, customers, price matrices and vendors. Dynamic files include accounts receivables, accounts payable, inventory costs, product costs, open sales orders, open purchase orders, purchase history and sale history.
   • 4
     Define user accounts and permissions for your project. The user setup should include testing and training on the new software, as well as live accounts and permissions.
   • 5
     Document the standard operating procedures for this project. End users will refer to this documentation during and after the ERP deployment. Modify the procedures as adjustments are made during the ERP implementation.
   • 6
     Schedule training for your end users. This training should include how the project will impact the user’s daily responsibilities. If possible, include comparison training so that users can see their responsibilities on their previous system and how they will appear in the new ERP system.
   • 7
     Conduct exercises that let the end users use the new system before it goes live. This gives them experience with the new ERP system and the opportunity to ask questions they may not have thought of during training.
   • 8
     Complete the ERP project by deploying the new software with real-time data and shutting down the previous system. During the initial phases of the transition, additional support staff can assist end users as they get used to this change in their work environment.

Read more: How to Manage an ERP Project | eHow.com http://www.ehow.com/how_6716050_manage-erp-project.html#ixzz1NGyXfn4l

Dependency determination

In the project management world, dependencies determine the order in which various activities should be completed. These dependencies usually documented as an activity attribute and help in sequencing the activities on the project schedule network diagram. As you prepare for your PMP exam, it is important to know the difference between discretionary dependencies and mandatory dependencies.

A mandatory dependency is one that “must be” carried out at a particular time. It is usually requirement of some kind based on contracts, laws, company procedures, physical limitations, etc. When the sequence of events is developed for various aspects of the process, mandatory dependencies are placed where they must happen.

A discretionary dependency is one that isn't based on a "have to", but on a "should". These decisions are usually based upon best practices, business knowledge, etc. They are placed on the project diagram where the team members would like them to occur.

Since discretionary dependencies are more arbitrary, they should be fully documented so the reasons for their placement can be maintained and available during future revisions. As a project progresses and adjustments are needed, discretionary dependencies are often reviewed for possible alterations.