A working-backward plan starts with the desired customer outcome or product, then identifies what must happen to reach it. It is a planning mindset: define success first, then turn the route to success into tasks, milestones, and timelines. section 10.1.3
To put the approach to work:
- Break the goal into manageable tasks and milestones, and map their timing and dependencies. section 10.1.3
- Work with a product manager where one is available, and communicate the plan so the team understands its shared responsibility. section 10.1.3
Table 10.1 A sample template for a working-backward plan
|
Timeline
|
Tasks and description
|
Owners
|
Status
|
|---|---|---|---|
|
T-3 months
|
Perform technical spikes.
Create a technical-design document.
Signoff by senior engineer/architect.
|
Engineering team
|
|
|
T-2 months
|
Coding is implemented.
QA testing is initiated.
|
Engineering team
QA
|
|
|
T-1 month
|
When implementation finishes, end-to-end testing is performed.
Security testing is performed.
User acceptance testing (UAT) is complete.
Bug fixes are done.
Code freeze occurs.
Launch readiness is achieved.
|
Engineering team
Security engineer
|
|
|
T
|
Launch
Postlaunch production support
|
.
|
|
|
T+1 month
|
Project retrospective
Measurement against success metrics
|
.
|
The sample template works backward from launch, assigning owners and status to preparation, testing, readiness, and postlaunch review. section 10.1.3
