UPI Study › Courses › Project Management › Free lessons › Lesson 8.4 Free with a free account
Defining and Tracking Milestones in Active Projects
Project Management · Chapter 8: Driving Project ExecutionSection 8.4 · lesson 47 of 7312 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Handling Incomplete Tasks: Consequences and Recovery →← Managing Team Roles and Work DistributionNext lesson: Handling Incomplete Tasks: Consequences and Recovery →
In this lesson
Writing testable milestones and tracking their slip with honest forecasts.
- Distinguish milestones from activities and deliverables
- Write evidence-based milestones with a verifiable event, one owner and stated proof
- Calculate milestone slip from baseline and forecast dates
- Interpret milestone trend charts and report moved milestones honestly
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,726 words). Read along, or search it.
Opening Question
Can a Milestone Be Forty Percent Done
Can a milestone be forty percent done? A made-up cabinet workshop is building a display counter. Sanding and finishing it takes three days, so that work can be forty percent done. It's an activity. The finished counter is a thing you can pick up and hand over. It's a deliverable. Counter finished and accepted by the shop owner happens at one instant, when the acceptance takes place. It has either occurred, or it hasn't. That's a milestone. Confusing these three is the root of many reporting errors. This lesson shows how to write milestones that can't be fudged, and how to track them honestly.
Definition
A Zero-Duration Point in the Schedule
A milestone is a zero-duration point in the schedule that marks an event, or a result achieved. Zero duration means it uses no working time. It's a moment, not a stretch of effort. A milestone is also not the same as its date. The date is a property the schedule attaches to it. The milestone is the event the date refers to. Once a project moves from planning into execution, milestones become the checkpoints that real progress is compared against, and the points sponsors and customers ask about first.
Milestone Types
Deliverable, Approval, Phase and External
Milestones come in four types, because the type decides who must act, and what counts as proof. Here are examples from a made-up furniture maker. A deliverable milestone marks a defined product completed and handed over: a prototype drawer unit delivered. Its proof is a signed delivery record. An approval milestone marks a decision by a named person or body: packaging artwork approved by the brand director. Proof is a signed approval, naming the approver, date and item. A phase milestone marks the end of one stage and the start of the next: design closed, build opened. Proof is the recorded closing decision. A gate is one kind of phase milestone. An external milestone is controlled by someone outside the team, like a supplier, a regulator, or a customer: import clearance received for the hinges. Proof is a notice from that outside party. The other three are usually internal. External ones are the easiest to leave off the schedule, since nobody on the team does the work, and they're often the biggest surprises.
Common Faults
Untestable, Activity-Worded and Ownerless
A milestone has one job: to show clearly whether the project has reached a defined point. Three faults stop it. First, dated but not testable. Design mostly done, end of March: mostly has no edge, so on April first one person calls it met and another calls it missed. Second, activity wording. Testing the prototype names work going on, which can last for weeks, so it can never be declared finished at a point. Third, the ownerless milestone. When everyone is vaguely responsible, nobody notices the date approaching, and nobody is asked why it moved. The three often travel together, and they share an effect: a milestone that can't be tested can't be reported as missed, until long after the damage is done.
The Repair
Event, Owner and Evidence
The repair is an evidence-based milestone, written with three parts. A verifiable event, worded as a result and its state, like drawings issued, or inspection passed. One named owner, answerable for making it happen and reporting it. And the specific evidence that proves it occurred, stated in advance, something that can be filed and shown to a third party. The test: could someone who wasn't involved decide, from the evidence alone, that the event happened? So: final drawings issued by March thirty-first, with the drawing register signed by the design lead. Prototype load test passed, shown by a signed test report. And finish sample approved: the retailer's buyer signs the approval form, and the account manager owns chasing it. A milestone is also all or nothing. If four of five drawings are issued, it hasn't occurred. Say which part remains. Never call it eighty percent met.
Quick Check
Choosing a Supplier Sample Milestone
Quick check. A bakery needs a milestone for its supplier's samples. Three drafts are on the table. Samples mostly in by May fifth, with a signed note. Receiving the samples, with a signed note. Or samples received, with a signed note. Which one works? Pause, and decide. The third. It names a result, and a note an outsider can check. Mostly in has no edge, and receiving describes work going on, not a moment. To finish the repair, name one owner, like the buyer who tracks the supplier.
Milestone Schedule
Baseline, Forecast and Actual Dates
A milestone schedule lists a project's milestones in date order, holding three dates for each. The baseline date is the one committed when the plan was approved. It's kept fixed, so there's always something to compare against. The forecast date is the owner's current best estimate, based on evidence, revised at each report. The actual date is when the evidence shows the event occurred. It's entered once, and from then on the forecast equals it. Moving a forecast is routine. Moving a baseline changes the commitment itself, so it goes through change control.
Measuring Slip
Forecast Minus Baseline in Calendar Days
At each report, the manager compares forecast with baseline for every milestone. Slip is the forecast date minus the baseline date, in calendar days. Positive means later than planned, zero means on time, and negative means early. Count how many moved, and note how far each moved. Three milestones that moved by one day tell a different story from one that moved six weeks. And milestones are linked. When an early one slips, later ones often slip too, so a high count may be one cause showing up several times.
Worked Example
Slip Across Five Kitchen Milestones
Here's a made-up kitchen opening, reported on April first. Floor plan approved: baseline March fourth, actual March fourth. Slip zero. Ovens delivered: April eighth to April fifteenth, seven days. Electrical inspection passed: April twenty-second to May sixth. That's eight days to the end of April, plus six: fourteen. Recipe handbook issued: May thirteenth, now May tenth: minus three, three days early. Build phase closed: June third to June twenty-fourth: twenty-one. The total is thirty-nine days, and the simple average over five milestones is seven point eight. The three late ones average fourteen. So quote the count that moved, and the largest single slip, twenty-one days, beside any average. And notice: the inspection moved fourteen days, but the phase that depends on it moved twenty-one. Seven days are unexplained, a question for the working schedule.
Trend Charts
Holding, Drifting or Recovering Forecasts
One report shows where a milestone stands, not which way it's heading. A milestone trend chart plots each milestone's forecast at every report. Reporting date runs along the bottom, forecast date up the side, and a diagonal marks where the forecast equals the report date. A line that meets the diagonal has occurred. A flat line means the forecast is holding, but it reassures only if the forecasts rest on evidence. Flat, then a jump just before the diagonal, is a problem found at the deadline. A rising line means the forecast keeps moving later. Milestone B climbs a week at every report, parallel to the diagonal. At week five it's forecast for week twelve. At week ten, it's forecast for week seventeen. Its gap never shrinks. A milestone that stays the same distance away is a milestone that never arrives. A falling line moves earlier. That's good news with a stated reason, like a delivery arriving early. If the only reason is optimism, scrutinize it like a rising one. The chart shows the pattern, not the cause, and it's only as honest as the forecasts feeding it.
Case Example
A Forecast Rising a Week Every Week
Here's how that plays out. Imani manages a made-up furniture product launch. Her tooling milestone has a baseline of week eight. At the week five report it's forecast for week nine. Week six says ten, week seven eleven, week eight twelve. Each move came with a reason that sounded fair. She plots the four forecasts and sees a line rising a week per week. A showroom event, set by an outside organizer, can't move. Each estimate had quietly assumed the obstacle would clear next week. After four repeats, the estimate isn't information anymore. The slip is already four weeks: twenty-eight days. So she shows the baseline, all four forecasts, the slip, and the effect on the showroom date. She marks the milestone no reliable date, instead of a fifth one-week guess. She commits to a firm forecast within three working days, once the tooling supplier gives a dated test schedule. Her report looks worse that week, and her sponsor conversation is harder. In exchange, a run of small surprises doesn't end in one large one.
Executive Reporting
An Honest Entry for a Moved Milestone
Executives read milestones first. A milestone needs no technical translation, it matches a commitment they've made to someone else, and there are few enough to scan in a minute. An honest entry for a moved milestone gives the baseline and the current forecast, the slip in days, and the cause in one sentence, saying only what's known. It names the owner and the action, the effect on later milestones and any fixed outside date, and what evidence will confirm the new forecast, and when. And it shows the earlier forecasts, so the reader sees the trend.
Warning Signs
Accurate Figures That Still Mislead
Some presentations mislead even when every figure is accurate: reporting only the milestones that were met, quoting an average slip alone, or counting approval requested as the approval. So does quietly replacing the baseline with the new forecast, a green status beside a forecast that moved later, or dropping a hard milestone and adding easy ones. A reader can ask four questions of any entry: what was the baseline, what's the forecast, what evidence supports it, and how has it changed over the last few reports?
Quick Check
Slip From June 24 to July 8
Quick check. A permit milestone has a baseline of June twenty-fourth. Today's forecast is July eighth. June has thirty days. How many days of slip is that? Pause, and decide. Fourteen days later. June twenty-fourth to the thirtieth is six days, and eight more reaches July eighth: six plus eight. Eight counts only the July days. Sixteen adds two days too many. And because it's an external milestone, someone named should be tracking the permit office.
Key Takeaways
Testable Events and Honest Tracking
To recap: a milestone is a zero-duration event, separate from the activity before it and the deliverable it records. Write each one with a verifiable event, one owner, and stated evidence. It's all or nothing. Track baseline, forecast and actual dates. Slip is forecast minus baseline, and both count and distance matter. And a trend chart shows whether a forecast is holding, drifting, or recovering.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Defining and Tracking Milestones in Active Projects
What is a milestone in project management?
How do you calculate milestone slip?
What is a milestone trend chart?
What makes a milestone poorly written?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →