Establish the scope
List the work included in the planning discussion and identify the tasks that must precede others. Confirm effort estimates with the people closest to the implementation.
Planning Agent
A plan that starts with the constraints.
Build a proposed schedule around dependencies, available capacity and the work still ahead.
ACDFMC+1
Illustrative workspace · interactive demonstration
Sequence dependencies
Keep blocked work behind the tasks it depends on.
ENG-284Linked context
Check available capacity
Review planned effort against the team’s available hours.
Review the range
Compare alternatives
Discuss what changes when a deadline or scope moves.
Ready for reviewHuman approval
A practical workflow
Build the schedule around the work that must happen.
A useful proposal respects prerequisites, recorded effort and the people available to deliver it.
Review the available week
Use the week selector in the demonstration to inspect a proposed schedule. Compare the sequencing with known availability, support responsibilities and other commitments.
Choose a reviewed alternative
Discuss what changes if a task moves, a dependency slips or scope grows. Keep the tradeoff attached to the plan so a later review can understand the original decision.
A connected working example
The sequence is only half the plan.
The Atlas example links migration implementation with validation and a cutover checklist. A schedule needs that ordering, but it also needs space for the people assigned to the tasks.
Review the capacity view alongside the proposal. An overloaded week suggests a planning discussion about sequencing or scope; it does not prove that moving a task will make the team faster.
ACDFMC+1
Illustrative workspace · interactive demonstration
Inside the approach
How the model works.
Planning uses explicit dependencies and capacity constraints to create a proposal. Effort estimates and availability can be wrong. A person reviews tradeoffs and approves the working plan.
Methodology and evaluation01Scope & capacity
02Dependency ordering
03Proposed schedule
Before you move forward
Confirm the constraints before accepting the schedule.
| Review | What to look for |
|---|---|
| Dependencies | Check that blocking work precedes dependent tasks and that external prerequisites are represented. |
| Effort | Review estimates and unknowns. Missing effort is not zero effort. |
| Availability | Include known leave, operational work and competing projects in the capacity discussion. |
| Tradeoffs | Record the scope or timing decision with the affected owner and the person responsible for the commitment. |
Questions & answers
A few useful answers.
Is the proposed plan automatically accepted?
A proposal needs review. The public demonstration shows a fictional schedule and does not change a real team’s calendar or task assignments.
Can I inspect another week?
Use the week selector in the planning example to compare the visible schedule. The records are seeded demonstration data.
What if an estimate is uncertain?
Keep the uncertainty visible, discuss the task with its owner and consider how a range of effort could affect the schedule and forecast.
Ship what you promised.
Bring the plan, the work and the next decision together.