Waterfall Project

The basic thinking around a Waterfall project is to have a checklist of things needed to be handled before each gate (step in the process).

The steering committee controles that the checklist is performed and approves deviations to the checklist if needed.

Development is performed simultaneously to all functions and parts of the project.

The activities in the checklist can be very detailed meaning that this way of steering is quite detailed

A project is a temporary effort undertaken to create a unique product, service or result

A lot of changes are performed in projects

You assign cross-functional project groups to steer and perform the project

To have a common picture of the progress of a project is essential in a company and there are a couple of advantages that I mention

Everyone in the company should know how far the project has progressed (What checkpoint is passed and when the next one will be passed)

Updates from previous projects can be used in all new projects

In the document the following areas are covered:
- Project the Dyne way (I am using the Set-based pinciples described among
The Building Blocks)
- Project the design process way
- To consider when using set-based engineering
- Checkpoints
- Steering group/Sponsor support

Agree and decide on chosen model

Make it detailed enough, make it easy to follow

Everything is fulfilled up to the checkpoint – if not fulfilled there needs to be a timeplan on how the Project can catch up (does the project need extra resources or help in any other way from the steering group?
What needs to be fullfilled up to the next checkpoint? (based on the process description and the delayed activities from this checkpoint).