Home › Solutions › Velocity Tracking & Sprint Reporting

Velocity tracking that starts the sprint after your first sprint

Flocci Projects computes sprint reporting from your completed sprints automatically: average velocity in story points, a velocity trend bar chart with one bar per completed sprint, current sprint progress (done points against total, with days remaining), a status-distribution breakdown, and open workload by assignee. All of it is on the free personal board.

Who this page is for: Tech leads and engineering managers who need forecasting, not vanity dashboards.

Velocity is only useful when it is free of ceremony. Ours is derived, not entered: complete a sprint and the points from its Done issues become that sprint's bar on the trend chart, while the average across all completed sprints becomes the number you plan against. Nobody maintains a spreadsheet, and nobody can quietly inflate the figure by editing a cell, because the only way to raise it is to finish work.

Read the four views together and they answer different questions. Average velocity answers 'how much can we commit'. The trend answers 'are we stable' — and stability matters more than magnitude, since a team that ships twenty points every sprint forecasts better than one oscillating between ten and thirty-five. Status distribution answers 'where is the work piling up'. Workload by assignee answers 'who is carrying too much', which is usually the cause of the other three.

One thing we do not have, stated plainly: there is no in-sprint burndown chart. You get sprint progress — done points versus total, and days remaining — which answers the same on-track question at lower resolution, but if a day-by-day burndown line is a requirement for you, Jira and Zoho Sprints both provide it and Zoho provides it free. What we give instead is a cross-sprint view that is free, automatic and hard to game.

What you get

Average velocity across all completed sprints, computed from Done points
Velocity trend bar chart — one bar per completed sprint, chronological
Sprint progress: done points versus total, plus days remaining
Status distribution across Backlog, Todo, In Progress, Review and Done
Open workload by assignee (top six) — over-allocation visible before it bites

Start free with Google sign-in

Frequently asked questions

How does Flocci Projects calculate velocity?

It sums the story points of issues in the Done status within each completed sprint. Unfinished work contributes nothing — velocity measures delivery, not effort — and the headline number is the average across every completed sprint in the project.

How many sprints before velocity is trustworthy?

Three completed sprints give a usable average and five give a reliable one. Until then, plan conservatively and let the number emerge rather than setting a target, because a target turns points into a currency people inflate.

Is there a burndown chart?

No. Flocci Projects shows sprint progress (done points against total with days remaining) and the cross-sprint velocity trend, but there is no day-by-day burndown line. Jira, Zoho Sprints, Shortcut Business and Plane Business all offer burndown if that is a hard requirement.

Can I compare velocity between two teams?

You can look, but you should not conclude anything. Story points are relative to each team's own estimation scale, so cross-team comparison measures estimation habits rather than output. Velocity's only legitimate use is forecasting the team that produced it.