Flocci Projects

Home › Agile answers › Which agile metrics actually matter for a small team?

Which agile metrics actually matter for a small team?

For a small team, four metrics are enough: velocity for forecasting, lead time for customer experience, work-in-progress for focus, and completed-versus-committed for planning honesty. Everything else — story points per developer, lines of code, individual burndown — measures activity and quietly rewards the wrong behaviour.

The four that earn their keep

Velocity tells you how much to commit. Lead time tells you what the requester experiences. WIP tells you whether the team is finishing or starting. Completed-versus-committed tells you whether your planning is calibrated. Each maps to a decision you actually make every sprint.

The ones that damage teams

Any per-person productivity metric turns estimation into negotiation and collaboration into a cost. Points per developer punishes the engineer who spends a day unblocking two colleagues. Cross-team velocity comparison measures estimation scales, not output. Both are common and both are corrosive.

Reading them together

One metric alone always misleads. Velocity plus WIP catches the team inflating throughput by starting more. Lead time plus velocity distinguishes an execution problem from a queue problem. Completed-versus-committed plus workload distribution usually explains a velocity drop faster than a retrospective discussion does.

What Flocci Projects gives you

Average velocity and a per-sprint velocity trend, sprint progress against total, status distribution across the five columns, and open workload by assignee — all derived from the board, all on the free plan. Lead and cycle time are not built-in reports today, though the activity history records the timestamps they would be computed from.

Try it on a free Flocci Projects board

Related questions

Should we track individual velocity?

No. Velocity is a team measure by design; splitting it per person rewards visible individual output over collaboration and immediately corrupts estimation, because points become a performance currency.

What is a healthy completed-versus-committed ratio?

Consistently around eighty to ninety percent. A team hitting a hundred percent every sprint is almost certainly under-committing, and one hitting sixty percent is over-committing and losing morale to it.

How often should we look at metrics?

Once per sprint, in the retrospective, together. Metrics checked daily become a scoreboard people play to, which is the fastest way to make them stop describing reality.

More agile answers