Building your project plan

Open the project plan template and sequence eighteen modules' worth of work against this brief. Identify the hard dependencies — geographies before entities, entities before legislative data groups, structures before people, security before user testing, workers before hierarchy — then identify what runs in parallel. Mark the decision points needing client input; in the capstone those become documented assumptions. Estimate effort per workstream. And mark the three permanent decisions as gates: nothing downstream of them starts until they are signed. Plan before configuring. An hour here saves three later. Where the brief is ambiguous, document an assumption and proceed. Do not stall. That is what consultants do — and it is what the assumptions log is for. And the professional move: a plan that treats the permanent decisions as gates is the difference between a consultant and somebody who configures.

In this module: Module 18 · Global Implementation Capstone

1. 1How the capstone works
2. 2The client brief
3. 3Building your project plan
4. 4Submission and grading
5. 5Solution walkthrough
6. 6Common submission mistakes