TeamBoostWORKFLOW LIBRARY

Dependency schedules / Delivery leads, planning owners and acceptance reviewers

Before / after

Add a shared-resource constraint to a schedule

Show why logically parallel tasks may still require serial execution.

The example isolates the difference between logical parallelism and actual shared-resource feasibility.

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Original worked case · Manual planning resource

Inspect the decision, not just the summary.

Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.

01 · Inspect the inputs

Every record stays visible

Inspect the invented case records
ActivityModel durationRequired resource
Artwork A3 daysSole illustrator
Artwork B4 daysSame illustrator
Assembly1 daySeparate assembler after both

Use horizontal scrolling for wide tables. These records are invented, not customer data.

02 · Follow the reasoning

How the case leads to a decision

Without contention the network-only finish would be max(3,4)+1=5. The stated exclusive resource requires 3+4+1=8 days.

The bounded result

The resource-constrained plan needs at least eight model days: seven illustrator-days in sequence, then one assembly day. Logical independence does not create a second illustrator.

Definitions and method context

Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.

GAO Schedule Assessment Guide ↗
General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule.

External references checked 6 October 2026. Demand for these topics has not been measured.

Compare the decision quality

Illustrative before / after

Synthetic planning case: Two independent artwork tasks take three and four model days. Both require the same sole illustrator full-time; final assembly takes one day after both.

Before

Network-only plan: five model days with unlimited independent artwork resources.

After

Declared sole-illustrator plan: eight model days with artwork serialized.

01

Check exclusive resource use

Owner role · Resource owner

Evidence: A and B cannot use the sole illustrator simultaneously under this model.

02

Revise the feasible sequence

Owner role · Scheduler

Evidence: The illustrator has seven nonoverlapping model days before assembly.

03

Explain the schedule change

Owner role · Project lead

Evidence: Five is labelled a network-only result; eight reflects the declared resource constraint.

Decision to make: The resource-constrained plan needs at least eight model days: seven illustrator-days in sequence, then one assembly day. Logical independence does not create a second illustrator.

Filled manual planning note

Invented planning text. Adapt it to your evidence and confirmed owners.

The resource-constrained plan needs at least eight model days: seven illustrator-days in sequence, then one assembly day. Logical independence does not create a second illustrator. Without contention the network-only finish would be max(3,4)+1=5. The stated exclusive resource requires 3+4+1=8 days. This simple exclusive-resource case is not a general resource-optimization solver. Durations and availability remain assumptions.

Put the outline to work

  1. Check exclusive resource use. Check: A and B cannot use the sole illustrator simultaneously under this model.
  2. Revise the feasible sequence. Check: The illustrator has seven nonoverlapping model days before assembly.
  3. Explain the schedule change. Check: Five is labelled a network-only result; eight reflects the declared resource constraint.

From a useful outline to team work

Explore TeamBoostAI for your team

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Questions about this workflow

Can I choose either artwork first?

Yes under these inputs; both orders finish at eight days. Other deadlines may distinguish them.

Does another team member remove the constraint?

Only if their eligibility and availability are established; do not infer substitution from headcount.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.