Hi Ian @Ian Parsonage -
I totally understand the urge to see a progress bar. It feels safer and gives a sense of control when a task is large.
But here is a hard truth about Story Points: they are a measure of relative complexity and effort, not a linear unit of measurement like hours or centimeters.
When we try to capture that "2 out of 5 SP are done", we are treating points like hours. But points do not work that way. In most cases, the last 1 SP of a task contains 80 percent of the risk, the hardest bugs, and the most complex integration work. Tracking "percent complete" on a story point is often a vanity metric - it looks good on a report, but it does not actually tell you if you will hit the deadline.
If a requirement "cannot be sensibly broken down", it is usually a red flag. It means the task is likely too large for a single sprint.
However, if you are managing a large-scale project where you absolutely need to see progress on a "macro" level without guessing percentages, the professional approach is to move from Story Points to comparing Actuals vs Planned.
Instead of asking "how many points are done", you look at how many actual hours have been logged against the planned estimate. This gives you a factual, data-driven view of progress.
I work with Be on Time, an Atlassian Marketplace partner, and we built a tool called MSP Planner for Jira specifically for this. It allows you to connect actual worklogs from Jira to your planned schedule, so you can see real progress based on effort rather than subjective point-percentages.
You can find it here: https://marketplace.atlassian.com/apps/3162894022/msp-planner-for-jira
Regardless of the tool, moving away from "percent complete" and toward binary delivery or actuals-based tracking is the first step to making your planning deterministic instead of optimistic.
Hope this helps you escape the percent-complete trap!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.