IT Project/Program Management
Sample Project Plans
Sample IT project and ERP program plan structures: phases, gates, workstreams, dependencies, resourcing, and cutover planning.
Overview
A plan structure should make the work easier to govern, not harder to read. These reference structures show how we organise common enterprise programmes into phases, gates, and workstreams.
They are starting points, not prescriptions. Each structure should be adapted to scope, risk, and the organisation’s delivery model.
Practice 01
Anatomy of a workable plan
We organise plans around outcomes and phase gates: what must be true before the programme moves on, who confirms it, and what evidence is required.
Workstreams are defined so that ownership is unambiguous, while cross-stream dependencies appear on the integrated plan rather than in separate documents.
- Phases with entry and exit criteria
- Outcome-based milestones, not only task dates
- Dependencies with named owners on both sides
- Resource assumptions and decision lead times
Practice 02
Assessment plan structure
A typical ERP assessment runs in four phases: mobilise and scope, current-state discovery, fit and gap analysis, and recommendation and roadmap.
The plan protects time for stakeholder validation. Findings that have not been tested with process owners are not yet findings.
Practice 03
Implementation and rollout plan structure
Implementation plans combine design, build, test, deploy, and stabilise phases with business readiness workstreams running in parallel.
Rollout waves are planned as separate deployment units, each with its own readiness gate, cutover runbook, and hypercare exit.
Practice 04
What to adapt first
Start with decision lead times and approval cycles. They are frequently underestimated and often sit outside the programme’s control.
Then test the plan against resource availability, not just role names. A plan that assumes the same three people in every phase is usually a plan with a hidden constraint.
From the field
Illustrative structure
An ERP assessment plan is organised into mobilise and scope, current-state discovery, fit and gap analysis, and recommendation and roadmap. Each phase closes with named stakeholders confirming the evidence — so the final recommendation is built on validated findings rather than a late review of a draft report.
Reference material
Documents and templates
Final documents will be published here when approved. Each placeholder describes the intended content so programme leaders can judge whether it will be useful.
Sample ERP Assessment Plan
A reference plan structure with phases, gates, and workstreams. Workbook to be supplied.
Document to be supplied
Sample Implementation & Rollout Plan
An adaptable implementation plan outline including wave and cutover placeholders. Workbook to be supplied.
Document to be supplied
Downloadable files are being prepared for release. No links are published until final documents have been reviewed and approved.
Continue exploring
Related capabilities
02 Best Practices
A practical set of delivery habits for governance, planning, risk, stakeholder alignment, and stabilisation.
Explore service
04 IT Project Manager Toolkit
The working documents we reach for most often: charters, RAID logs, status formats, decision records, and readiness checklists.
Explore service
01 Lessons Learned from Various Local & Global Rollouts
Patterns that repeat across local and global rollouts — and the early decisions that change the outcome.
Explore service