Handover
Handover is the formal moment a live product moves from its project to the Product layer. It happens at the end of stabilisation, only when the handover criteria are met and the handover pack is complete.
The handover rules
- The Receiving Product Manager is named at Define and shadows the project from Build.
- Handover criteria are written into the project charter at G1.
- No handover without a complete handover pack and a Handover Review.
- The Receiving Product Manager may accept, accept with dated conditions, or reject.
- From the day after handover, all change goes through the Product layer.
Possible outcomes
| Outcome | What happens |
|---|---|
| Accept | All criteria met. The product team owns the product from the next day. |
| Accept with conditions | Minor gaps with named owners and dates within one Pulse Cycle. The product team owns the product; the project closes the conditions. |
| Reject | A criterion that protects customers or service continuity is not met. Stabilisation continues and a new review date is set. |
The rest of this page is for subscribers
Subscribe to read the other 6 sections of this page:
- Handover criteria
- The handover pack
- Step by step
- Who does what
- In the DelPulse workspace
- If you use Jira or Azure DevOps