Fictional case study · Document 11 · Week 2 baseline
Project Schedule
The team maps the initial twelve-week milestones and their dependencies.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Original schedule
| Weeks | Milestone |
|---|---|
| 1–2 | Charter, design, WBS, ownership and backlog |
| 3–4 | Environment, backups and runtime work |
| 5–7 | Connector, database migration rehearsal and monitoring |
| 8–9 | Integration, security and recovery tests |
| 10 | BookEasy pilot |
| 11–12 | Release, stabilization and handover |
Dependencies and baseline control
Connector and database changes must be ready before end-to-end tests. A restore rehearsal and QA/Security evidence are required before the pilot. Sponsor release approval follows pilot acceptance. The CTO / sponsor approves the schedule baseline at the end of week 2; version 1.0 becomes the reference for tracking and changes. The part-time team availability was reviewed with functional leads when building this estimate. The PM records competing work that could affect the schedule.
Schedule tracking view
Planned work is tracked separately from milestones: planning and design (weeks 1-2), environment and runtime (weeks 3-4), connector, migration rehearsal and monitoring (weeks 5-7), testing (weeks 8-10), BookEasy pilot (week 11), production authorization and deployment (week 12), stabilization and operations handover (weeks 12-13), and project closure (week 13). Key terms: schedule baseline is the approved time plan; milestone is a significant completed result; dependency is work required before another activity; stabilization is the post-deployment monitoring and handover period.
Capacity, critical path and advance conditions
Planning capacity assumptions are: PM 50%, Engineering 50%, Database 25%, DevOps/SRE 25%, Security 15%, QA 50%, Product 10%, Customer Success 20%, and Support 10%. These are planning assumptions, not billing claims; the PM records competing work. The likely critical path is compatibility, test environment, migration and recovery rehearsal, integration and security testing, BookEasy pilot, sponsor authorization, deployment, stabilization, handover and closure. Functional tests must pass before the pilot, BookEasy must accept the pilot before production authorization, stabilization must pass before handover, and handover must be accepted before closure. Calendar duration is the time an item occupies the schedule; effort is the person-time required, so a two-week testing window may use four QA days.
Gantt and resource histogram
The Gantt is the primary schedule view for activities, dependencies and milestones across the 12-week plan plus the one-week recovery impact. A resource histogram compares weekly planning hours with each part-time role's availability; it is used to identify conflicts and competing work. A burndown is not included because this project is not organized into sprints.