[lgunsch]

The answer is in the article itself. It gives you real historical data so you can predict how long the project will take with evidence, rather than just a feeling, hope, or guess.

> Velocity is an aggregate measure of tasks completed by a team over time, usually taking into account developers’ own estimates of the relative complexity of each task. It answers questions like, “how much work can this team do in the next two weeks?” The baseline answer is “about as much as they did in the last two weeks,”

If there's one thing the last 50 years of software development has conclusively proven, is that estimating the number of man months (hours) a project will take doesn't work.

[awinter-py]

hmm fair, I skimmed and should have read more carefully

still: (1) sounds like complexity predicts weeks? so they are estimating hours. And (2) I think if jira clones were really a tool for estimation, they'd have uncertainty scores and some kind of prediction market built in

[politelemon]

A clear solution for this exists: we should double the number of people who are estimating how long a project will take.

[waynesonfire]

counting hours doesn't work so lets count unicorns? Want some of my koolaid? You seem to be out.