Project tracking is the process of monitoring a project’s progress against its original plan. In Software Project Management (SPM), it ensures that the development team stays on schedule, within budget, and maintains the required quality standards.
Effective tracking acts as an early-warning system, allowing managers to identify risks and adjust resources before a delay becomes unmanageable.
1. Core Tracking Activities
To track a project effectively, several key areas must be monitored simultaneously:
- Schedule Tracking: Comparing actual start and completion dates of tasks against the project schedule.
- Effort and Cost Tracking: Monitoring the actual man-hours and financial resources consumed compared to the original estimates.
- Milestone Analysis: Verifying that major “checkpoints” or deliverables have been met.
- Defect Tracking: Monitoring the number of bugs found, their severity, and the speed at which they are resolved.
2. Common Tracking Techniques
Earned Value Analysis (EVA)
EVA is a quantitative technique that combines schedule, cost, and scope to measure project performance. It helps answer: “Is the project ahead of or behind schedule?” and “Is it over or under budget?”
- Planned Value (PV): The estimated value of the work planned to be done by a specific date.
- Actual Cost (AC): The actual cost incurred for the work performed.
- Earned Value (EV): The value of the work actually completed.
Earned Value Indicators
- Schedule Variance (SV): $SV = EV – PV$ (Positive means ahead of schedule).
- Cost Variance (CV): $CV = EV – AC$ (Positive means under budget).
3. Visual Tracking Tools
Gantt Charts
The most common tool for Waterfall-style projects. It provides a horizontal bar chart showing the timeline of every task and the dependencies between them.
Kanban Boards
Popular in Agile environments, Kanban boards track the “flow” of work. Columns typically include To Do, In Progress, Review, and Done. This makes bottlenecks (where too many tasks are stuck in one column) immediately visible.
Burn-down and Burn-up Charts
- Burn-down: Shows how much work remains versus time. If the line stays above the ideal path, the team is behind.
- Burn-up: Shows the total work completed against the total scope. This is useful for tracking progress when the project scope (total requirements) is changing.
4. Formal Progress Reviews
Beyond automated tools, tracking requires human intervention:
- Daily Stand-ups: Short, 15-minute meetings to discuss what was done yesterday, what will be done today, and any “blockers.”
- Status Meetings: Weekly or bi-weekly meetings with stakeholders to review high-level KPIs and risks.
- Milestone Reviews: Formal sign-offs at the end of a phase (e.g., after the Design phase is finished) to ensure the project is ready for the next step.
5. Metrics for Tracking Quality
Tracking isn’t just about speed; it’s about stability. Managers track:
- Velocity: The average amount of work a team finishes in a sprint.
- Cumulative Flow: A diagram showing the status of work items over time to identify process inefficiencies.
- Defect Leakage: The percentage of bugs that “leak” from one phase (like coding) into the next (like testing).