EN
Insight

Agile or plan-driven? Why ERP projects need both

Both, each where it fits. Process design, enhancements, and reports gain from short cycles, while data migration and cutover need fixed dates and abort criteria. Above both sits a governance layer in which the executive team decides at fixed points.

Martin Hörnig5 min read

In brief
  • Govern each part of the project by its nature. What only shows up in the system is built iteratively; what must work on a cutoff date follows a plan.
  • PRINCE2® provides management stages, tolerances, and the project board. SAFe® provides joint planning of several teams on a fixed cadence.
  • WSJF ranks enhancement requests by cost of delay relative to size. Legal requirements and anything critical for go-live sit outside this ranking.
  • Before the start, clarify who prioritizes, who approves data, and who decides on tolerances.

Why “agile versus waterfall” is the wrong question

The “agile versus waterfall” debate comes from software development. An ERP project is more than development. It changes processes, migrates years of data, and switches operations over on a fixed date.

These parts behave differently. Govern them all the same way, and you make either the migration unpredictable or the process design cumbersome.

How to govern each part

Project partCharacteristicGovernanceWarning sign
Process designGaps only show up in the systemCycles of workshop, system demo, and adjustmentDesign documents wait weeks for approval
Enhancements and custom softwareRequirements change during the projectBacklog, sprints, review with the businessThe specification is outdated before development starts
Reports and analyticsThe value only shows with real dataShort cycles with key usersReports go unused after go-live
Data migrationQuality comes from repetitionTest migrations (mock migrations) on a fixed cadence, reconciliation after every runEach test migration runs differently from the last
CutoverFixed date, fixed sequenceRunbook with go/no-go decision, see cutover runbookOn Sunday evening, people debate what “done” means
Contracts and contract awardThe scope of services must be specified up frontFixed framework with defined flexibility, for example a budget allowance for enhancementsEvery change becomes a change request

Data migration is a special case. It runs in cycles, but with fixed requirements. Every test migration follows the same procedure so that the results are comparable.

The framework: PRINCE2® for decisions, SAFe® for cadence

In practice, a division of labor between the methods works well. Each level answers a different question.

LevelMethodContributionWho decides
Executive managementPRINCE2®Management stages with a decision at every stage boundary, tolerances, management by exceptionProject board
Several teamsElements of SAFe®Joint planning on a fixed cadence (PI Planning), visible dependencies between teamsProject lead with the product owners
TeamScrum or KanbanShort cycles, prioritized backlog, regular demosProduct owner in the business
Migration and cutoverPlan-drivenScheduled test migrations, runbook, go/no-goProject board, on the project lead’s recommendation

The project board, called the steering committee in many companies, decides at the stage boundaries. The management stages follow the milestones of migration and cutover, and the teams deliver toward these milestones at their own cadence. Our five project phases follow the same pattern.

Tolerances also differ by part. PRINCE2® 7 defines tolerances for time, cost, scope, quality, risk, benefits, and sustainability. Agile teams get leeway on scope, while migration and cutover get a tight tolerance on the date.

Prioritizing with WSJF

When there are more enhancement requests than capacity, a transparent ranking helps. SAFe® uses Weighted Shortest Job First (WSJF) for this: the cost of delay of an item is divided by its duration. Because duration is hard to estimate, teams use relative size in practice.

Cost of delay is made up of three values, each estimated relative to the other items. They are user and business value, time criticality, and risk reduction or opportunity enablement. A modified Fibonacci sequence is common for the estimates (1, 2, 3, 5, 8, 13, 20).

Here is a worked example with assumed values from an ERP backlog. Cost of delay is shown as the sum of value, time criticality, and risk reduction or opportunity enablement.

ItemCost of delaySizeWSJF
Add supplier and planned delivery time to the MRP list8 + 5 + 3 = 1635.33
Determine the source of supply automatically via source list and purchasing info records13 + 8 + 5 = 2683.25
New layout for the delivery note3 + 2 + 1 = 623.00
Interface to an additional shipping provider8 + 13 + 8 = 29132.23

The small MRP list enhancement comes first, even though automatic source determination brings more value. It delivers value quickly and ties up little capacity. If the new interface must be live at go-live, it does not belong in this ranking at all.

This is where WSJF reaches its limit. Legal requirements and everything that go-live depends on come before any prioritization. WSJF orders the rest, and it is only as good as the joint estimate of business and IT.

Separate the roles clearly

Clarify before the start who decides what. This is how we split the roles when we hold overall project leadership:

  • The project lead owns plan, budget, and milestones. They alert the project board when a tolerance is forecast to be exceeded.
  • The product owners in the business own the content and priority of their backlog. For that, they need decision-making authority.
  • The data owners for each area own cleansing, reconciliation, and sign-off of their migration objects.
  • Under PRINCE2®, the project board represents business, user, and supplier interests. It decides at the stage boundaries and whenever a tolerance is exceeded.

Typical mistakes in hybrid projects

  • “Agile” serves as an excuse for a lack of planning in migration and cutover.
  • Sprints have no link to the management stages. Team deliveries miss the milestones.
  • Product owners lack decision-making authority, and every priority is renegotiated by the project board.
  • A fixed price applies to a scope that is meant to change iteratively.
  • The project board decides details instead of deviations from the tolerances.

How we help

We combine agile and plan-driven parts in five phases, with decisions by your executive team at fixed points. If your project lacks a project lead or needs a restart, we provide interim leadership.

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

Initial call Call