Track Project Milestones with SMART Criteria

Provides a structured approach to milestone tracking and project management - SMART milestone definition, dependency mapping, critical path analysis, earned value tracking, and status reporting.

Use this skill when defining project milestones with clear acceptance criteria, mapping dependencies between milestones for critical path analysis, tracking progress via earned value metrics, building a weekly status report with traffic-light health indicators, or integrating milestone tracking with Agile sprints and Jira/Gantt tooling. Not a fit for day-to-day task management unrelated to milestone-level tracking, or for projects without defined delivery dates.

Core principles: SMART milestone definition (specific, measurable, achievable, relevant, time-bound - e.g. "Deploy user authentication system with 99.9% uptime by March 15" rather than "improve system"), dependency mapping of predecessor/successor relationships, risk-adjusted scheduling (25-40% buffer for high-risk technical milestones, 10-15% for routine ones), and stakeholder alignment with a clear owner and approval process per milestone.

Provides a full YAML milestone structure with ID, category, priority, owner, dates, progress percentage, acceptance criteria, predecessor/successor dependencies, deliverables with status, risks with probability/impact/mitigation, and resource allocation. Progress tracking methodologies include earned value tracking (planned value, earned value, actual cost, schedule performance index SPI = EV/PV, cost performance index CPI = EV/AC) and the Critical Path Method, with a Python function example performing a forward pass to calculate earliest start/finish times and identify critical milestones via topological sort.

Status reporting uses a traffic-light system with explicit thresholds (Green: within 5% behind schedule with no blockers, Yellow: 6-15% behind with minor blockers, Red: over 15% behind with major blockers), plus a weekly status report template covering executive summary, a milestone update table (ID, owner, status, percent complete, target date, risk level), risks/blockers, and decisions required. Agile integration guidance covers sprint-milestone alignment (each milestone spanning 1-3 sprints) and epic-to-user-story decomposition under a milestone. Tool configuration examples include a Jira custom field schema (milestone ID, category, critical path flag) and a Gantt chart JSON data structure with tasks and finish-to-start dependency links.

Best practices recommend milestone granularity of every 2-4 weeks, baseline management tracking variance from the original baseline rather than just current targets, a communication cadence of weekly updates for active milestones and immediate escalation for critical path delays, and post-milestone retrospectives to improve future estimation.

Provides configuration examples for Jira (custom milestone fields) and Gantt chart tools (task/dependency JSON structure), alongside a Python-based critical path calculation approach.

Project managers and technical leads tracking milestone-based delivery who need concrete critical path analysis, earned value metrics, and status reporting templates rather than a simple task checklist.

def calculate_critical_path(milestones):
    earliest_start = {}
    earliest_finish = {}