Case 08: a plan of 9 work packages and 15 activities, 7.2 weeks against a
10-week window, with the customer's carrier circuit on the critical path. The
stated topology was built this time. The owner keeps the estimates as they
are: one experienced engineer, no contingency.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new Deliverable in the packaging Phase, produced by a delivery planner
after validation.
- The planner writes the plan as data: work packages that name the Elements
they deliver, and activities with days, what each follows, and whether the
team or the customer owns it.
- Code checks the plan against the design: every Element belongs to a work
package, and the activities can be scheduled.
- Code computes the schedule, with no more of the team's activities at once
than the team has people, and the critical path.
- Code writes the WBS dictionary (a work package is done when the Checks on
its Elements pass), the activity sequence and a timeline on a relative axis
from Day 0.
- The plan is checked against the delivery window from the agreed scope; over
it, the Deliverable says by how much and names the critical path.
- With a start date it also gives calendar dates and a Mermaid Gantt chart.
- The timeline is added to the solution guide, and the plan's length is in
execution.json and the packaging Approval.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>