Skip to main content
Version: 2.0

Progress Tracking

For over two decades leading engineering teams, I’ve seen countless approaches to “progress tracking.” From elaborate spreadsheets to trendy Agile boards, the goal is always the same: understand if we’re on track to deliver. But too often, these systems become about tracking, not about understanding. They generate data, but little insight. We end up with a false sense of security, or worse, panic attacks triggered by a red burndown line.

Let’s move beyond just showing progress and focus on understanding it. This isn't about ditching your tools; it's about shifting your mindset and applying a few key principles.

The Illusion of Velocity​

Many teams fixate on “velocity” – the amount of work completed in a sprint. While it can be a data point, treating it as the definitive measure of progress is dangerous. Here's why:

  • Story Point Inflation: Teams inevitably get better at estimating. What was a "5" last month becomes a "3" this month. Velocity increases, but actual output might not.
  • Hidden Work: Technical debt repayment, refactoring, and documentation often fall through the cracks in sprint planning. This crucial work isn't reflected in velocity, masking the true cost of delivery.
  • Context Switching: Interruptions, meetings, and urgent bug fixes derail focus, slowing down progress. Velocity doesn't account for this lost time.

Actionable Insight: Don't treat velocity as a KPI. Instead, use it as a trend indicator. Is it generally stable? Increasing? Decreasing? Investigate why before drawing conclusions. Velocity can be a useful tool for team self-organization and identifying patterns in workload, but it should not be the primary measure of progress.

Beyond Tasks: Focusing on Outcomes​

We often measure progress by the number of tasks completed. But completion doesn’t equal value. A perfectly coded feature that nobody uses is, well, a waste of time.

Instead, shift your focus to outcomes. What demonstrable benefit will this work deliver to the user or the business?

  • Define Clear Objectives: Every piece of work should tie back to a specific, measurable objective. "Implement user authentication" is a task. "Increase user registration conversion rate by 10%" is an objective.
  • Track Key Metrics: Identify the metrics that indicate whether you’re achieving your objectives. This could be daily active users, error rates, or revenue.
  • Celebrate Impact, Not Just Output: Recognize and reward the team for delivering tangible results, not just for completing tasks.

The Power of Incremental Advances (and Detecting Stalls)​

As the input mentions, making "incremental advances" is vital. Big bang releases are risky and delay feedback. (As highlighted in Lean principles) Break down large features into smaller, deliverable increments. This allows you to:

  • Get Early Feedback: Validate assumptions and course-correct before investing significant time and resources.
  • Reduce Risk: Smaller changes are easier to test and deploy.
  • Maintain Momentum: Frequent releases keep the team motivated and engaged.

However, incremental progress can also stall. And that's where a more nuanced tracking approach is vital. Simple task trackers like Linear are great for seeing what is blocked, but won't tell you why.

Here’s how to detect stalls:

  • Daily Stand-Ups: Go Beyond "What did you do?" Ask "What’s preventing you from making progress?" and "What support do you need?". Focus on impediments, not just activity.
  • Weekly Reviews: Look for Patterns: Are the same issues consistently blocking progress? Is a particular team member consistently overloaded?
  • Lead Time & Cycle Time (Leverage Tools like Uptrace): These metrics, tracked with tools like Uptrace, can highlight bottlenecks in your development process. They’re key indicators of flow efficiency in a DevOps pipeline, and a sudden increase in lead time is a warning sign.

Actionable Insight: Use a simple "Progress/Impediment" board alongside your task tracker. Visually highlight roadblocks and actively work to remove them.

Tools as Enablers, Not Drivers​

We're bombarded with project management tools – Clockify for time tracking, Repohistory for GitHub insights, even tools for tracking analytics issues like Trackingplan. These tools can be valuable, but they shouldn’t define your progress tracking strategy. Beware of "tooling overwhelm"—adopting too many tools without a clear strategy can be counterproductive.

  • Choose Tools That Fit Your Needs: Don’t adopt a tool just because it's popular. Consider your team's size, complexity, and workflow.
  • Don’t Over-Automate: Manual tracking can sometimes provide more valuable insights than automated reports. (Especially when it comes to identifying qualitative issues.)
  • Focus on Communication: The most important tool is still a conversation. Regularly check in with your team, ask questions, and actively listen to their concerns.

In conclusion: True progress tracking isn't about creating elaborate dashboards or obsessing over velocity. It's about understanding why things are moving (or not moving), identifying and removing impediments, and focusing on delivering value to the user. By shifting your mindset and embracing a more nuanced approach, you can build a more effective, engaged, and high-performing engineering team.

What's one small change you can make this week to shift your focus from tracking to understanding?