Fictional case study · Document 10 · Week 2 baseline
Technical Backlog
The work packages become prioritized tasks with owners, dependencies and acceptance evidence.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Prioritized work
| ID / WBS | Task / owner | Dependency | Acceptance evidence |
|---|---|---|---|
| B01 / 2.1 | Update runtime and review dependencies / Engineering | Approved technical approach | Login, API and regression tests pass on selected versions (REQ-01) |
| B02 / 2.2 | Implement stable IDs, retries and deduplication / Backend | Agreed BookEasy event scenarios | The same test event is processed once after a simulated timeout (REQ-03) |
| B03 / 3.1 | Rehearse migration and restore / Database | Prepared test environment and representative data | Records reconcile and restore succeeds (REQ-02, REQ-06) |
| B04 / 2.2 | Configure ingestion monitoring / DevOps | Connector test environment | A simulated failure generates an actionable alert (REQ-05) |
| B05 / 4.1 | Run integration and security checks / QA | B01–B04 ready for testing | Agreed tests pass with no release-blocking defects (REQ-01–06) |
| B06 / 4.2 | Coordinate BookEasy pilot / Customer Success | B05 and customer test scenarios | BookEasy accepts documented pilot results (REQ-04) |
Release and handover work
| ID / WBS | Task / owner | Dependency | Acceptance evidence |
|---|---|---|---|
| B07 / 3.2, 4.2 | Execute approved migration and release / Database and DevOps | Successful pilot, restore rehearsal and sponsor go/no-go | Production checks and agreed reconciliation completed; rollback available |
| B08 / 1.2, 4.3 | Transfer support procedures and close project / PM and DevOps | Release and stabilization | Operations accepts runbook; sponsor accepts closure |
How estimates are used
Effort estimates are initial team estimates for planning, based on dependencies and assumed capacity. Functional leads confirm or change them during planning. The PM records estimate changes and their schedule impact.
Backlog controls and key terms
The backlog uses priority and status to distinguish pending, in-progress, blocked and done work. Monitoring is WBS 2.3. Security and data protection is a separate task under WBS 4.1. Release execution, operations handover and project closure are separate tasks. Backlog: ordered project work. Dependency: work required before another task. Acceptance evidence: proof of completion. Retry: another delivery attempt after temporary failure. Deduplication: preventing the same event from being processed twice. Regression testing: checking existing behavior after a change. Runbook: operating and recovery instructions.