Short answer: A progress tracker makes software progress visible. Not through dashboards or Gantt charts, but through cycle time per story, velocity on accepted work only, and a forecast that updates every iteration. Most tools sold as progress trackers are to-do apps with reporting bolted on, so teams end up logging activity without ever surfacing throughput. The useful ones enforce the opposite: fewer fields, one owner per card, no started-but-not-accepted work in velocity. Under three engineers shipping daily, a spreadsheet with a cycle-time column is a progress tracker. At ten engineers across two squads, you need software that enforces the discipline.
The Purpose of a Progress Tracker for Software Projects A progress tracker is a tool that makes software progress visible. That's the full story. Since they define activity on a card as progress, they would measure whether people were typing rather than whether anything was shipping. So most of them fail for this reason.
If you have been assigned a progress tracker and you wish to not to go ahead with it, this post is for you. We will look at what a progress tracker is actually supposed to do, which three features earn their keep, which features are theatre, how progress trackers and to-do apps and Gantt tools differ from one another, and when you should skip the category entirely and use a shared spreadsheet. Every strong opinion in this entire piece ultimately boils down to the assessment that a progress tracker is only as good as the discipline it enforces, and most enforce none.
Progress tracker, plainly explained
A progress tracker is a system (software, spreadsheet, sticky-notes on a wall, etc.) that answers three questions about a piece of software.
- What's done? — accepted, in users' hands, no caveats.
- What's in flight, and how long has each piece been in flight? — cycle time per card.
- At the current throughput, when does the rest of the backlog finish? — a forecast with a rolling velocity underneath it.
A progress tracker is a tool that can help you answer those three questions in 30 seconds or less. It is a search bar for my filing cabinet.
UX Glossary defines progress tracker as a component like a stepper on a sign-up flow. It is a different thing. Similar terminology, alternate issue. This post focuses on the category related to projects or teams rather than the user interface (UI) element.
The three features that earn their keep
Most progress trackers come with 40 features. Three of the walls carry a load. The remaining thirty-seven either pose no harm or cause harm.
**1. The cycle time per card measures the time taken for each story that was shipped. Having a 7-day median and a 7-day P95 is a very different issue than having a 2-day median and a 14-day P95. Your user experience will depend on how the distributions look. If your tracker displays an average without the distribution, you’re flying with one eye closed. “The Kanban Guides treats cycle time as the central metric for a reason.”
**2. Count only the work that was accepted and not what has been committed to. Not initiated Should have been linked with references as per evidence. Approved When the number ignores unshipped work, it becomes a useful forecasting tool. By keeping track of start-but-not-accepted stories, teams are blind to problems until the release date itself. The result is a velocity chart that looks ship shape right up until the deadline.
**3. A forecast curve that refreshes with each iteration, illustrating a development strategy. When velocity stays within the range of 3 iterations, this backlog will finish in 4 to 7 iterations. Any tool that gives a single date is lying with precision. A tool fails to provide a forecast if it does not update the range after each iteration.
LiteTracker has been designed specifically to support this three-feature set the queue only moves a story to throughput on acceptance and forecast cone updates every iteration from rolling-3 average. 该工具故意设计得非常狭小。 The remaining 80% are what causes enterprise trackers to appear slow.
The theatre features — skip them
Useful features that are actually not. If your tracker is prominently showing these, then the vendor is selling screenshots, not throughput.
- Gantt charts for software teams. A Gantt chart assumes a stable plan. Software plans don't stay stable past the second iteration. The chart is almost always wrong, and the time spent updating it is time not spent writing stories. Gantt is for construction and for marketing campaigns with fixed launch dates, not for a team that iterates. (Martin Fowler's writing on XP and the Agile Manifesto both pre-date most Gantt plug-ins by a decade.)
- Elaborate status workflows. New / Analysis / Approved / Started / Blocked / In Code Review / In QA / In UAT / Ready for Release / Released / Accepted / Closed. Twelve statuses is eleven more than most teams need. The cognitive overhead of knowing which column a card belongs in exceeds the information gained by the distinction. Three statuses — unstarted, started, accepted — are enough for 90% of teams.
- Custom field proliferation. Every stakeholder gets to add a field. Business value score, strategic alignment, OKR tag, risk level, dependency chain, compliance owner. Each one adds entry friction and reduces the chance anybody fills in the ones that actually matter.
- Dashboards that measure typing. Comments per day. Cards edited per week. Average response time to a mention. These measure how hard a tracker is to use, not how much a team ships.
- Dependency maps that nobody updates. Dependency tracking looks like a feature until you watch a team drift away from maintaining it in month two. If the information isn't kept current, the map is more dangerous than no map — it creates confidence that doesn't match reality.
All of these features have one thing in common: they all allow someone to produce a report. Reports do not equal progress. If you want to understand issue tracking systems in general, we wrote one on that too
Progress tracker vs to-do app vs Gantt tool
Many tools pitch themselves as all three, making the category murky. They are not.
| Tool type | What it answers | Best for | Fails at |
|---|---|---|---|
| To-do app (Todoist, Things, Apple Reminders) | What should I do next? | Individuals, errands, personal projects | Team throughput, cycle time, forecast |
| Progress tracker (LiteTracker, Shortcut, Linear's basics) | What has the team actually shipped, and when does the rest finish? | Software teams running iterations | Fixed-date launches, non-iterative work |
| Gantt tool (Microsoft Project, Smartsheet, GanttPRO) | What are the dependencies and the critical path on a fixed plan? | Construction, hardware, marketing launches | Teams whose plan changes mid-iteration |
| Hybrid tracker (Jira, monday.com, ClickUp) | All of the above, configurably | Multi-team enterprise with headcount to maintain the config | Small teams; opinion-free config means every team runs it differently |
A progress tracker focuses on shipped software and the prediction of the remaining work. If you require critical-path analysis across a stable 12-month plan, then you need a Gantt tool. Not a progress tracker. A progress tracker is not what you need to ensure you buy milk, a to-do app is. Unique questions give rise to different categories.
A common way teams choke: getting a hybrid tracker and configuring it as a progress tracker. This means switching off twelve features and training all team members to ignore a further ten. It works until someone joins the company and configures things differently. It creates a tracker that is differently interpreted by every two people.
The tool landscape — the honest version
A handful of tools come with opinions. We are the makers of LiteTracker and so this is biased.
| Tool | Does the three load-bearing things? | Note |
|---|---|---|
| LiteTracker | Yes — enforces accepted-only velocity, cycle time, forecast cone | Opinionated. Won't bend to non-iterative workflows. Free tier, unlimited users |
| Shortcut (ex-Clubhouse) | Mostly — clean story model, serviceable forecasting | Smaller ecosystem; good for software teams who dislike Jira |
| Linear | Partially — fast UI, cycle time included, less mature on velocity forecasting | Great for teams that already run on throughput; weaker for cross-team coordination |
| Jira | Only if configured | Can be made to work; most teams configure it until nobody recognises it |
| Asana | No, really — generic project management | Fine for cross-functional work. Not built for software iteration |
| Monday.com, ClickUp | No, configurably | Hybrid trackers. Fine for ops, over-featured for software progress |
| Spreadsheet | Yes, if you keep the columns disciplined | For teams of 2–3, this is the right answer |
More and more SaaS software seems to be converging on some pricing level, possibly about $8–$15 per seat per month these days, most come with a free tier, or some variant, for small teams. If a vendor is quoting $25+ per seat, without an annual commitment, the vendor is priced for enterprise procurement, not a 6 person team.
How to roll one out without the theatre
The majority of time is spent rolling out a new progress tracker.
- Pick the tool on Monday. Spend an hour, not a quarter. Methodology is the real choice; tool is the second choice. If you're already running iterations with accepted-only velocity, almost any tracker that respects that will work.
- Import the current backlog as-is. Don't rewrite stories. Don't re-estimate. Just move them. The tool is a container; the content is the current state.
- Agree three statuses. Unstarted, started, accepted. If a card needs a fourth status to describe its state, split the card instead.
- Pick one metric to watch for the first month. Cycle time distribution. Not velocity, not throughput, not WIP — one metric. The team learns the tool by watching one thing move, not by looking at every dashboard.
- Run two iterations before changing anything. Every tool feels wrong in the first week. If the team is still unhappy after iteration two, change settings. Not before.
Teams that do this, ship faster. The tracker is an implementation technique for Structured sprint management helps teams ship up to 70% more value by their eighth sprint. However, it is not about the software per se; rather, it concerns the ceremony tax paying for itself. The tracker is the surface where that discipline becomes visible. This will be A metric we see across XP-flavoured teams’ iterations, not a vendor’s brag, is .. so 297 (new SD) is their alertness (a good proxy for system quality). The device (not by HCI or Interaction design standards) is to give teams “fewer features to ignore and one metric to watch”.
When progress trackers fail — three signs
Generally, rollout of most progress-trackers do not fracture. They lessen. Signs that the discipline is losing grip.
The tracker and standup are saying different things Standup says login story nearly done Tracker says login story has been in-progress for 11 days Someone is not updating tracker, or standup is lying. When the tracker ceases to be the source of truth, it is rendered useless as no one uses it anymore. Solution: During the standup, raise the tracker. The card is touched or the status is incorrect.
Cycle time is slowly drifting upwards without anyone noticing. The median is increasing, the P95 is increasing, and the team is still barely getting ships out. When the signal is given by the tracker, the team members ignore it. Every iteration, put cycle time on the retro agenda, not as a scorecard, but as a starter. Lead time and cycle time details up what to look for.
Growth in Velocity numbers along with flat shipped features. Velocity should always measure the count of accepted stories. When velocity is increasing, but releases are not, something is being counted that shouldn't be - usually bugs, chores or started work that is not accepted. Monitor the processes involved. If a bug has any points then remove those points. The point of the number is to predict the next iteration, not to grade the team — see velocity is not the goal for the longer argument.
The underlying cause for every instance is the same: the tracker is manipulated when the team gets rewarded for the number and not the shipping. The tracker was successful. The motivation did.
When NOT to use a progress tracker
The brand message of LiteTracker: Notify people when the thing we sell is not required. Here are the scenarios where a progress tracker does more harm than good.
- Fewer than three engineers. A spreadsheet with three columns and a cycle-time column is enough. A dedicated progress tracker on a three-person team is a tool nobody asked for.
- Short, fixed-scope projects. Six weeks to a known-shape deliverable, no iteration planned, no post-launch work. A Google Doc with a checklist outperforms a tracker here. Trackers are for continuous work, not for one-shot projects.
- Non-software work with fixed launch dates. Hardware ship dates, marketing campaigns tied to a conference, compliance work with a regulator deadline — those want a Gantt tool, not a progress tracker. The questions are different.
- The team already has one that works. If an incumbent tracker is doing the job, switching costs usually exceed the gain. We built an import tool specifically for teams migrating from other trackers — the import is a one-minute upload, not a quarter-long project — but even so, don't migrate for sport. Migrate when the current tool is actively costing the team more than it saves.
To get true value from a progress tracker, a continuous flow of work must be happening with an iterative team. This happens when the question of “when is the rest of this backlog done?” actually matters. If any of those components is absent, something simpler will be better.
Frequently asked
What is a progress tracker?
A tool that makes software progress visible by showing what’s accepted, what’s in flight and for how long and when the rest of the backlog will finish at current throughput. Software, spreadsheet or sticky note wall are all useful.
How is a progress tracker different from a to-do app?
An individual uses a to-do app at the personal level that essentially asks what do i do next. A progress tracker at the product level answers questions like "what has the team shipped and when will the rest finish?". Different question, different tool. Most to-do apps get a feature for team use and get sold off as progress trackers but they usually don’t surface cycle time or forecasting which is the whole point.
What features actually matter in a progress tracker?
Three metrics include cycle time per card with distribution, rolling velocity on accepted work only, and a forecast curve that updates every iteration. All other features are considered nice-to-have, most of the forty features in a normal tracker are theatre.
Should a progress tracker have Gantt charts?
No, it is not useful for software teams. A Gantt chart assumes a stable plan, whereas software plans do not stay stable after iteration two. The rationale behind the existence of Gantt tools, is construction, hardware, marketing campaign with a fixed launch date. Software iteration is distinct and it’s better suited to a forecast cone than a critical path.
How often should the team update a progress tracker?
The team interacts with a story daily. If updates are batched into a weekly sync, the tracker will become an archive rather than a live source of truth. The test is whether the standup can be run from the tracker. If yes, the bill has already been paid. No, it is not.
What's the best progress tracker for software teams?
A tool that enforces only accepted velocity, shows cycle time distribution, and forecasts in a cone, not a date. LiteTracker is built around exactly this (bias), Shortcut and Linear do most of it, and an unloaded spreadsheet will beat a mis-configured Jira. Choice of a tool is the second most important after methodology.
Progress tracker vs project tracker — what's the difference?
Preferably promotion. Usually, a project tracker implies a larger scope i.e. multiple teams, cross functions, non-software etc. A progress tracker has a narrowly defined scope andappears software focused. It doesn’t matter much what the name is on the pricing page; what matters is whether the tool answers the three questions above.
Do small teams need a progress tracker?
No, if the team already has three or fewer people shipping on a daily basis. One way to measure progress is to have a shared spreadsheet with cycle-time columns and an “accepted today” running list.Accepted list is often a marker of progress. It is something we can agree on. It does not cost anything. Continuous coding needs clear visibility. SaaS progress trackers do good work on more than five engineers, when standup cannot hold state in head.
Still stuck
If you've discovered cycle time, accepted-only velocity, forecast cone in what you're already using, the tool is doing its job. Retain it.
LiteTracker is your go-to option if you’re looking to pick an option that ‘only’ lets you work that way. All memberships offer unlimited users without limits, no demo call, and no per-user trick when the team grows. The registration will take one click.
Use a spreadsheet if you have three engineers and no fires. You shouldn’t pay us for any friction that doesn’t exist.