We ensure that enough research and analysis is done so that we fully understand:

• The purpose of the project or programme. This includes the expected business benefits and the impact on the people. The people can be stakeholders, users, customers and suppliers.

• The processes impacted by the project or programme. The current-state processes need to be understood along with their future-states.

• How any technology will underpin the project or programme. This is especially important as more and more software solutions operate in the cloud.

• The risks that have been identified that may negatively impact the delivery if not managed effectively.

• Any current issues that need a resolution.

​

We setup appropriate delivery teams to structure the workload and communication streams.

​

The above information is used to build the detailed project or programme plans. These clearly show:

• The individual tasks and the person or team responsible for completion.

• When the tasks are planned to take place. These clearly show the inter-dependencies between tasks and the effect of any slippage.

• The phases, where relevant. For software implementation projects, they usually follow; design, build, training, test, and transition to production.

​

The information is published in a 'project initiation document' and project plan. This is signed off and approved by the senior stakeholders or project board.