Home / DMAIC / Define

Define · Tool guide 10 of 20

Time Plan

A time plan places project activities and milestones on a working calendar. It combines task durations, logical dependencies, resource availability and review decisions. A milestone marks an event or accepted outcome; it has no duration of its own.

Expected output: An agreed calendar schedule with activity owners, milestones, assumptions and a review routine.

01 · Purpose

Why and when to use it

Why?

It helps the team coordinate work and recognise when delays threaten an agreed review or delivery date.

When?

Create an initial plan in Define, then update estimates as measurement and cause investigation reduce uncertainty.

Who takes part? The leader maintains the plan with activity owners; the sponsor agrees important milestones and changes to commitments.

02 · Application

How to apply it

Start with: Work packages, network logic, effort estimates, calendars, resource commitments and review requirements.

  1. Convert work packages into activities with named owners.
  2. Estimate effort and duration separately.
  3. Apply predecessor relationships and realistic working calendars.
  4. Place review milestones where decisions are needed.
  5. Check resource conflicts and agree an achievable baseline schedule.
  6. Update actual progress, forecast completion and escalate significant slippage.

03 · Example

A warehouse dispatch project

Original illustrative example. All quantities, targets, roles and timings below are fictional teaching assumptions, not findings from a real project.

WeekPlanned workReview or condition
1Confirm charter, scope and measure definitionsDefine review: mandate and measurement approach agreed.
2–3Validate data and establish baselineMeasure review: baseline sufficiently reliable.
4–5Investigate and test cause explanationsAnalyze review: causes supported by evidence.
6–9Select and test changesPilot review: benefits and guardrails evaluated.
10–12Implement, monitor and transfer ownershipControl review: sustained performance and handover evidence.

04 · Interpretation

What the result tells you

The dates are an initial planning scenario, not a reason to declare a phase complete without evidence. If cause verification needs more work, revise the forecast and discuss the effect on the goal.

Completion check: An agreed calendar schedule with activity owners, milestones, assumptions and a review routine.

05 · Judgement

Mistakes and limitations

Common mistakes

  • Confusing eight hours of effort with one elapsed day when staff are only partly available.
  • Omitting approval and waiting time.
  • Changing dates silently rather than recording a revised forecast.

Limits of the tool

A calendar plan is sensitive to uncertainty, availability and competing operational work. Detailed plans for later phases should remain provisional until the required evidence is available.

07 · Reading

Sources and further reading

Toolset backbone: Six Sigma+Lean Toolset: Mindset for Successful Implementation of Improvement Projects, second edition, edited by Stephan Lunau, with Renata Meran, Alexander John, Olin Roenpage and Christian Staudter (Springer, 2013). This reference identifies the toolset; the book text was not available for a chapter-level comparison in this development pass. The explanations, application sequence and fictional examples here are original LeanTrainingLab teaching material. Linked readings provide background; they do not prescribe every example or target.