This snapshot, taken on
, shows web content acquired for preservation by The National Archives. External links, forms and search may not work in archived websites and contact details are likely to be out of date.
The UK Government Web Archive does not use cookies but some may be left in your browser from archived websites.
Essential maintenance work is being carried out on the UK Government Web Archive. This should not affect access, but in the event that it does, we will resolve it as soon as possible. We apologise for any inconvenience this might cause.
Please email if you require any assistance.
Picture courtesy of the Olympic Delivery Authority.


Controlled Start-Up

Before starting, it is vital to gain the commitment of the business to the proposed project. The outputs must be clearly defined and agreed, along with the measures (critical success factors) against which the outputs will be judged. It is also vital to ensure there are adequate numbers of staff with the required skill set and experience for the task.

Identify the dependencies with other projects

You are on step 10 of 15 steps.

Click for slide: Obtain commitment from the business Click for slide: Define the outcome Click for slide: Define critical success factors Click for slide: Adopt processes for project management Click for slide: Check staff skills and experience Click for slide: Determine governance arrangements Click for slide: Define the project scope Click for slide: Determine the project approach Click for slide: Plan for management of risk Click for slide: Identify the dependencies with other projects Click for slide: Determine whether procurement is required Click for slide: Define the project organisation Click for slide: Produce a project plan Click for slide: Revisit scope Click for slide: Define reporting arrangements
Previous step Next step

What you need to do

Does the project rely on other projects?

Do other projects have to be delivered first?

What would be the impact on this project if related projects failed?

Points to consider

A dependency map is a useful way of drawing together known dependencies, combined with a risk register setting out the risks associated with key dependencies.

See also: Achieving Excellence Guide No. 4: Risk and value management