SI Delivery
SI Delivery is a WBS template that breaks a contract delivery project into 28 tasks across 6 phases. Phases follow the contract structure from kickoff report to final acceptance, with the interim and final acceptance Milestones stated explicitly. It is the deepest template in this collection: a 4-level tree where Design splits into architecture design and feature design.
When this template fits
- You build and deliver a system under contract with a client
- The contract includes sign-off gates such as interim and final acceptance
- The project replaces an existing system, requiring As-Is analysis and data migration
- Formal reporting such as a kickoff report is expected
When another template fits
- If there is no acceptance procedure and the system is internal, In-house Development is the better fit
- If the goal is market validation for a new product, IT New-Product MVP is the better fit
Phase by phase
Initiation
Project preparation and the kickoff report. In delivery projects the kickoff report is not a formality — it is the first agreement with the client on scope and schedule.
Analysis
Current-state survey, As-Is analysis, and requirements definition, closed by a review of the analysis deliverables. The review is its own task because only client-confirmed analysis feeds design.
Design
Splits into architecture design (system, DB) and feature design (screens, interfaces). Keeping the two tracks separate lets you follow infrastructure decisions and feature decisions independently.
Development
Common modules come first, followed by core features and interface development. Including environment setup and deployment, it is the largest phase by duration.
Integration & Migration
Integration tests, performance and security tests, and data migration, closed by the interim acceptance Milestone. An acceptance Milestone has zero duration, so any slip shows up in the schedule immediately.
Go-live & Stabilization
System go-live and hypercare lead to the final acceptance Milestone. The stabilization window before final acceptance buffers defect response and operations handover under the contract.
Full template structure
| WBS Code | Task Name | Type | Duration (d) | WEIGHT (%) |
|---|---|---|---|---|
| 1 | SI Delivery | Deliverable | — | 100% |
| 1.1 | Initiation | Phase | — | 8% |
| 1.1.1 | Project initiation preparation | Work Package | 4 | 55% |
| 1.1.2 | Kickoff report | Work Package | 3 | 45% |
| 1.2 | Analysis | Phase | — | 15% |
| 1.2.1 | Current-state survey & As-Is analysis | Work Package | 6 | 40% |
| 1.2.2 | Requirements definition | Work Package | 5 | 35% |
| 1.2.3 | Analysis deliverables review | Work Package | 3 | 25% |
| 1.3 | Design | Phase | — | 20% |
| 1.3.1 | Architecture design | Phase | — | 45% |
| 1.3.1.1 | System architecture design | Work Package | 5 | 55% |
| 1.3.1.2 | DB design | Work Package | 5 | 45% |
| 1.3.2 | Functional design | Phase | — | 55% |
| 1.3.2.1 | Screen design | Work Package | 5 | 50% |
| 1.3.2.2 | Interface design | Work Package | 5 | 50% |
| 1.4 | Development | Phase | — | 30% |
| 1.4.1 | Common module development | Work Package | 10 | 20% |
| 1.4.2 | Core feature development | Work Package | 20 | 40% |
| 1.4.3 | Interface development | Work Package | 12 | 25% |
| 1.4.4 | Environment setup & deployment | Work Package | 7 | 15% |
| 1.5 | Integration & Migration | Phase | — | 18% |
| 1.5.1 | Integration testing | Work Package | 10 | 40% |
| 1.5.2 | Performance & security testing | Work Package | 7 | 30% |
| 1.5.3 | Data migration | Work Package | 7 | 30% |
| 1.5.4 | Interim acceptance completeMilestone | Milestone | 0 | 0% |
| 1.6 | Go-live & Stabilization | Phase | — | 9% |
| 1.6.1 | System go-live | Work Package | 3 | 50% |
| 1.6.2 | Hypercare & stabilization | Work Package | 10 | 50% |
| 1.6.3 | Final acceptance completeMilestone | Milestone | 0 | 0% |
Start with this template
FAQ
- Why do acceptance Milestones have zero duration?
- Because a Milestone is a point in time, not work, its duration is zero. The interim and final acceptance gates in this template are set that way. If acceptance preparation needs effort, add it as a separate Work Package.
- How does progress roll up in a multi-level tree?
- Progress entered on the lowest Work Packages rolls up through WEIGHT. A split phase like Design aggregates each branch first, then combines them into the phase's progress.
- Can I share the schedule with the client?
- A read-only share link gives the client a view without an account. You can also download the Excel file and attach it to contract documents.
- Our methodology uses different phase names.
- Rename the phases after applying. The structure and dependency links stay intact, so renaming to your in-house methodology is the fastest customization.
- Is this compatible with how we worked in MS Project?
- It uses the same standard concepts: WBS codes, dependencies (FS links), durations, and Milestones. The Excel file follows standard WBS notation, so it moves into an existing document system easily.