Schedule Strategy
What schedule strategy actually decides
Schedule strategy is the set of decisions made before a schedule model is built. It selects the scheduling method (critical path method, critical chain, rolling-wave, agile or hybrid, or a simple milestone-driven bar chart for small work), the scheduling tool and its degree of standardization across the enterprise, the schedule levels produced (for example an L1 executive summary, L2/L3 control schedule, L4/L5 execution detail), the coding and WBS structures, calendar and resource conventions, and the governance rules: who may status, revise, baseline, and archive the model.
Concepts a candidate must know
Enterprise environmental factors and organizational process assets shape the choice; so do contract type, project size and complexity, risk exposure, organizational scheduling maturity, and schedule data confidentiality and security. Tailoring is a first-class concept: a strategy that is right for a multi-year capital program is wrong for a two-week internal deliverable. Also understand that the schedule model (the underlying data set) is distinct from the schedule (the output presented to stakeholders).
Traps
- Treating a Gantt chart as a scheduling method; it is a presentation view, not a method.
- Assuming CPM is mandatory on every project rather than tailored.
- Producing one level of detail for every audience, so executives get 4,000 activities.
- Ignoring organizational process assets and reusing an unsuitable legacy template.
- Selecting a tool before defining reporting and control needs.
Rule of thumb
Adopt the simplest method that satisfies the control need. When scope is well defined, risk is low, and one accountable owner exists, a milestone chart with a critical-path check is sufficient; add resource loading, multiple calendars, earned schedule, and formal update cycles only when complexity, contract terms, or risk justify the added overhead.