Project management · York University

Reusable-Container Implementation Pilot

A technical project-management case covering work breakdown, sequencing, critical paths and schedule sensitivity for a 26-week implementation pilot.

Project contextGraduate team project · My contribution: work breakdown, schedule development, critical-path and network-sensitivity analysis.

Decision summary

Problem

Make a 12-week pilot schedulable and finishable inside a 26-week project.

Evidence

The network showed two parallel critical paths and 37 of 50 activities with zero float.

Decision

Treat schedule sensitivity as a management priority rather than a reporting exercise.

My role

Built the WBS, baseline schedule, Gantt, network and critical-path analysis for my workstream.

The question

How do you make a 12-week sustainability pilot schedulable, testable and finishable inside a 26-week project?

Schedule logic

Two preparation paths converge before the same launch sequence.

ABDEFGH

ACDEFGH

Parallel critical paths identified in the final network analysis.

26 weekstotal project duration

12 weekspilot operations

37 / 50activities with zero float

74%critical-activity ratio

01 · Project objective

A pilot still needs a full project architecture.

The team proposed a 12-week reusable takeout-container pilot at York University. The full project covered preparation, launch readiness, pilot operations, evaluation and closeout over 26 weeks, within a C$85,000 maximum budget.

02 · My responsibility

My workstream focused on schedule logic.

My contribution covered the 3-level WBS, task list, duration estimates, baseline schedule, Gantt chart, network diagram, critical path, network-sensitivity analysis and project completion date.

03 · Critical-path logic

Two preparation streams converge before launch.

The final network had two parallel critical paths: A → B → D → E → F → G → H and A → C → D → E → F → G → H. Both preparation streams must finish before launch-readiness testing can begin.

04 · Schedule sensitivity

The schedule had very little room to absorb delay.

Thirty-seven of 50 activities had zero float, a 74% critical-activity ratio. That made supplier delivery, approvals, installation, testing and the pilot itself especially important to monitor because a small delay could move the December 17, 2027 completion date.

Selected work product

Selected project evidence.

26-week baseline schedule from the reusable-container pilot — Project schedule developed as part of my assigned project-management workstream.

Critical-path and schedule-sensitivity analysis from the reusable-container pilot — Selected team deliverable; my assigned workstream covered the critical-path and schedule-sensitivity analysis.

What I took from it

A schedule becomes useful when it shows where the project cannot absorb delay. The critical path was not an academic add-on; it changed what deserved management attention.

← All selected work Contact