Milestone Trend Analysis (MTA) records the forecast date of selected milestones at successive reporting dates. Plotting those forecasts as a time series shows whether each commitment is holding, moving later, or moving earlier. It is a visual history of forecast changes—not a standalone diagnosis of delay, cause, or final-project outcome.
What Milestone Trend Analysis shows
MTA preserves each reporting-period estimate instead of showing only the latest schedule. HWR Berlin describes it as a way to visualize milestone history, progress and prognosis; SAP project-progress documentation describes comparing milestone dates at multiple points in time. The method is also used in deadline controlling, as summarized by Projekt Management Austria.
Choose milestones that represent meaningful outcomes or decision points, then record their current forecast dates whenever the project issues an agreed update. Each new point remains on the chart, so successive revisions become visible.
How an MTA chart is laid out
| Chart element | What it represents |
|---|---|
| Horizontal axis | The reporting date—the date on which the forecast was recorded. |
| Vertical axis | The forecast or planned calendar date for the milestone. |
| Line for each milestone | The sequence of forecast dates recorded at successive reporting dates. |
Always read the labels and scale before interpreting direction. A chart with an inverted date scale can make a later date appear visually lower rather than higher.
#1 Best Overall
How to read movement in the lines
| Pattern (with a conventional chronological vertical scale) | Meaning | What to investigate |
|---|---|---|
| Horizontal | The forecast date has remained stable across the recorded updates. | Whether the underlying schedule, status data and update discipline are credible. |
| Rising | The forecast has moved later. | What changed, whether float or dependencies absorb the movement, and what response is feasible. |
| Falling | The forecast has moved earlier. | Whether scope, logic, resources or assumptions changed and whether the earlier date is achievable. |
| Sharp step or reversal | A substantial revision occurred between two reporting dates. | The decision, event or assumption that produced the revision; the chart shows the change but not its cause. |
A persistent upward trend warrants attention because the forecast has repeatedly moved later. It does not prove that the overall project finish will move by the same amount: the effect depends on dependencies, available float, critical-path position, scope and the credibility of each estimate.
Creating an MTA chart: a practical workflow
- Start with a realistic schedule. Confirm that dates, logic, calendars and progress rules are maintained well enough to support a forecast.
- Select representative milestones. Include contractual, customer, governance, release or other decision milestones that matter to project outcomes. Do not turn every activity into an MTA milestone.
- Set the reporting convention. Define what counts as the reporting date, what date is being forecast (for example, finish or approval), who owns the update and how exceptions are documented. The sources support regular updates but do not establish one universal interval.
- Capture each forecast without overwriting history. At every agreed update, save the current forecast date for every selected milestone alongside the reporting date.
- Plot the two dates. Put reporting dates on the horizontal axis and forecast milestone dates on the vertical axis. Use an unambiguous date scale and a separate, clearly labelled line for each milestone.
- Review changes with the project team. Examine direction, slope, reversals and convergence of lines, then trace the change through schedule logic, risks, scope, resources and decisions.
- Agree an action and an owner. MTA provides evidence that a forecast changed; corrective action requires the team’s broader schedule and delivery analysis.
Prerequisites for a useful analysis
- A schedule whose logic and dates are realistic enough to forecast from.
- Milestones that represent material outcomes rather than every minor task.
- A consistent definition of each milestone and its forecast date.
- Regular, disciplined status updates with prior forecasts retained.
- Clear ownership for explaining material movements and deciding responses.
HWR Berlin identifies a realistic schedule, meaningful milestones and regular feedback as prerequisites. A flat line is therefore evidence of a stable recorded forecast, not proof that the work is healthy or that the date will be met.
What MTA can—and cannot—tell you
It can show forecast stability and drift
The chart makes revision history visible: which milestones repeatedly move, when movement began and whether several commitments are changing together.
It cannot establish a cause
A later forecast might follow a design change, a supplier issue, a resource constraint, a logic correction or a more credible estimate. The line alone cannot distinguish these explanations.
Rank #3
- book
- A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition and The Standard for Project Management (ENGLISH)
It does not automatically predict the project finish
MTA has no universal formula that converts a milestone trend into a final-date prediction. Assess dependencies, float, critical-path location, scope and estimate quality in the live schedule before communicating an outcome.
It does not prove trouble from one movement
One revision can be a deliberate, well-controlled change. Repeated movement, clusters of slipping milestones or unexplained reversals are stronger prompts for investigation than any single point.
Rank #4
- Harvard Business Review Project Management Handbook: How to Launch, Lead, and Sponsor Successful Projects
- Harvard Business Review Press
- BLANK BOOK
MTA compared with a current schedule or Gantt view
| Question | MTA | Current schedule or Gantt view |
|---|---|---|
| What date history is visible? | Successive forecast dates are preserved. | Usually emphasizes the current plan unless baselines or snapshots are separately maintained. |
| What is easiest to see? | Direction and magnitude of milestone-date movement over reporting periods. | Task durations, relationships, calendars and the current plan. |
| Does it explain causes? | No; it flags changes for investigation. | It exposes logic and constraints that can help explain them, but still requires analysis. |
| What input does it need? | Consistent milestone forecasts and reporting dates. | Detailed, maintained activity status and schedule logic. |
Use the views together: MTA communicates how commitments have changed, while the current schedule supplies the dependency and critical-path context needed to decide what to do.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Building an MTA chart in Microsoft Project
Microsoft Project does not have one universal MTA workflow across editions and configurations. A practical implementation uses a maintained Project schedule plus a history table or chart that stores each update’s reporting date and milestone forecast. The Project Group has described creating MTA charts and offering an add-in, but current compatibility and availability should be confirmed with the vendor before deployment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Create or open the project schedule and identify the milestone tasks to monitor.
- At each status date, update the milestone’s forecast finish using the project’s normal scheduling and progress rules.
- Export or copy the selected milestone name, the reporting/status date and its forecast finish into a history sheet; append a new row or column rather than replacing the prior observation.
- Use Excel or another charting tool to plot reporting date on the horizontal axis and forecast finish date on the vertical axis, with one series per milestone.
- Label the date scales, preserve the data snapshot and document the status-date convention so later readers can reproduce the trend.
- Review the chart beside Project’s relationships, total float and critical-path information before assigning a cause or corrective action.
SAP-specific historical guidance
SAP’s project-progress manual from April 2001 describes relevant-milestone and project-version settings and states that, when a project runs according to plan, the curve remains horizontal. Those instructions are historical and specific to SAP’s implementation at that time; do not assume that menu names or behavior match a current SAP product. Consult the documentation for the exact SAP edition and release in use.
Communicating an MTA finding
A precise status statement names the milestone, the reporting period and the forecast movement, then separates observation from explanation. For example: “The design-freeze milestone moved 12 calendar days later between the 1 June and 15 June updates. Schedule review is under way to determine whether the change affects the critical path.” This wording reports what MTA establishes without claiming a cause or a guaranteed project-level consequence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
