An automation project is not just installing software. It changes how people work, where data comes from and who is responsible for what. That is why it needs the same discipline as any other business change.
Why project management matters in automation
Companies rarely automate because an ERP looks impressive. The reason is usually a concrete problem: spreadsheets no longer work, stock levels do not match, purchasing is done by hand, or data is copied between systems. When the problem is clear, the goal of the project can be written down. When the goal is missing, the project drags on and its result stays unclear.
Common reasons automation projects fail or slip:
- the scope is not written down, and each stakeholder means something different by it;
- change requests are agreed verbally, and cost and schedule drift without anyone noticing;
- data migration from the old system is left to the end, even though it often takes the most time;
- users are not involved, so the new system does not fit daily work;
- handover is not agreed, so nobody owns the system after go-live.
PMBOK in brief
PMBOK (Project Management Body of Knowledge) is a framework of project management practice published by the Project Management Institute (PMI). The current edition, PMBOK 7, is built on 12 principles and eight performance domains: stakeholders, team, development approach and life cycle, planning, project work, delivery, measurement and uncertainty. It is not a single way to run a project. It is a set of principles applied to the situation at hand.
How the principles appear in an automation project
Scope. The scope of an automation project is written down before work starts: which processes move, which systems are connected and what is left out. A scope that is not written down is the most common cause of schedule and cost overruns.
Change control. Every change is recorded, assessed and approved before it is made. This includes small things such as a new report or an added field. The effect on schedule and cost stays visible throughout.
Risks. Risks in automation projects are usually about information: the quality of old data, missing interfaces, access rights and user adoption. Each risk is entered in a risk register with a named owner and an action.
Stakeholders. The buyer, users, finance and the system vendor need different things. A stakeholder plan states who decides what and how information flows. Without it, decisions are slow.
Data migration and integrations. Migration is a separate work package. It includes cleaning, conversion and checking. Integrations, such as banking, an online shop or e-invoicing, are tested with real data before go-live.
Go-live and handover. A project is not finished when the system is running. It is finished when users can do their work, the data reconciles, the administrator knows what the system contains, and ongoing support is agreed.
What we do in practice
In our projects these principles look like this:
- We start with one process that can be measured, and extend only after acceptance.
- Each project has a named owner and a written scope.
- Changes are recorded and approved before they are made.
- Data migration is planned and tested as its own step.
- The ERP data and access rights stay with the customer. The customer receives a list of components and handover instructions.
Limits
PMBOK does not guarantee that a project succeeds. It gives structure, but decisions, the team and the quality of the data decide the outcome. We do not claim certification on the basis of PMBOK. We describe the results of each customer project separately, once they have been agreed and measured.