Delivery Planning
Delivery Planning is a collection of ongoing activities in which the delivery team produces and maintains a comprehensive plan for delivery. This will include both how the design and implementation is expected to
The objective of Delivery Planning is to ensure efficient coordination and execution of tasks to achieve timely and successful delivery of a solution.
Delivery Plans¶
Delivery Plans are a set of artefacts produced and maintained by the delivery team and should be clear, visible and easily accessible. Delivery Plans include a design plan and implementation plan. Delivery Plans should be continually reviewed and updated throughout the entire problem solving lifecycle.
Design Plans¶
Note
Design Plans typically include: detailed technical requirements, functional requirements, experiential requirements, test planning requirements, estimates and a DOT (direction of travel).
Implementation Plans¶
Note
Implementation Plans typically include: status reporting artefacts, a prioritised backlog, a timeline and delivery schedule, detailed resourcing plan and a RACI (responsible, accountable, consulted, informed).
Responsibilities¶
| Owner | Responsibility |
|---|---|
| Delivery Owner | The Delivery Owner is accountable for ensuring that delivery planning occurs at appropriate times and delivery plans are produced and effectively communicated with colleagues and stakeholders |
| Delivery Team | The whole Delivery team is collectively responsible for conducting delivery planning sessions, producing delivery plans and ensuring these plans are well maintained, accessible and effectively communicated with colleagues and stakeholders |
| Product Lead | Responsible for participating in any delivery planning events, producing delivery planning artefacts by sharing relevant product insights and providing relevant estimations |
| Engineering Owner | Responsible for participating in any delivery planning events, producing delivery planning artefacts by sharing relevant technology insights and providing relevant estimations |
| Design Owner | Responsible for participating in any delivery planning events, producing delivery planning artefacts by sharing relevant user/design insights, and providing relevant estimations |
Triggers¶
Delivery Plans need to remain current and as change is so frequent in software development environments, these plans typically become outdated quickly. The team responsible for delivering a solution will need to determine and document when Delivery Plans including Design Plans and Implementation Plans should be produced, reviewed and updated, and therefore when any planning events should occur. This will typically be as soon as enough is known to produce a delivery plan, and after any change that impacts the validity of the plan.
Note
All Problem Owners, Delivery Owners, Delivery Teams, Product Leads, Engineering Owners and Design Owners are collectively responsible for flagging when delivery plans are stale, as and when they discover relevant information.
Communication Plan¶
The team responsible for a problem will need to determine and document how and when delivery plans will be communicated with colleagues and stakeholders, ensuring expectations are clear and guidance available to support effective stakeholder engagement.
Note
Be mindful of your audience when defining an approach to communicating delivery plans with your stakeholders and/or colleagues. You may need to tailor your approach for each level of stakeholder to ensure you enable the engagement required from that particular audience.
Considerations & Toolkit¶
The Delivery Planning event typically occurs at the beginning of the AMPFlow design zone and the process is repeated as and when necessary throughout the full problem solving lifecycle.
Teams can use any approach they wish to perform delivery planning events and produce delivery plans
- Review the tooling section of the Knowledgebase for current default document templates.