At RedShield, we’ve learned that to commit to a customer deployment date, we need to have our ducks in a row. It’s a lot like a formula 1 qualifying run; where the car is the project, worked on by multiple teams that need to synch together to hit a target time - to deliver the winning result.
The perfect synchronisation of an F1 team of teams - what we’re aiming for at RedShield
To get started right we have 2 quality gateways and key activities and artefacts for each to enable us to launch, summarised in the following tables:
Gateway 1 (G1) | Gateway 2 (G2) |
Quote / Agreement
|
Plan Discovery (Scoping, RASCI, Risk and Coms) Charter (Scope artefact) RFI Doc (key build information) |
Enables us to: Scope, Plan, assign resources, prepare discovery and kickoff. |
Enables us to: Commence work Understand and meet timelines & expectations |
So - expect all these best practise activities, artefacts and communications, so we can start right, be aligned and deliver to standard.
Comments