The Requirements section is devoted to building what\'s called a Requirements Document. The Requirements Document contains all stakeholder requirements - in this case for the future - as collected from stakeholders including government and business leaders, and you - the citizens. Also included in this document is a inventory or what exists today - so that a sizing (GAP) analysis can better estimate the work required during design and build.

Implementation contains a number of standard parts including: acquisition of required materials, training, how-to documentation to train with and a Operations Book that explains how to get things started again when they stop.

Commonly a Pilot is run before affecting change on a much larger community of affected participants. On completion of the Pilot, a designated UAT (User Acceptance Test) Team scores and accepts responsibility for the full-scale implementation

Now comes the effort of training and transitioning the 90%.

Phase 2, 3, and so on - Per our Road Map. Often a change might require too long an interval to complete and best-practise suggests that we should break up the end deliverable into Phases for delivery. This keeps project timelines down to very reasonable durations from which progress can be easily measured.