TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Is velocity a good metric to measure team performance?

2 pointsby duykhoa12tover 8 years ago

2 comments

_niom_over 8 years ago
Short answer is no.<p>Problem with the velocity is that we developers are really poor in estimates and the velocity is rarely accurate enough.<p>So what I would like to recommend is that you first check your definition of done and then start experimenting with velocity by following how many stories you get done per week. After 4 weeks calculate the average. Each week through out put should be fitted in 1 Standard deviation (Normal distribution). Make it a strict rule that only ready for prod is done done.<p>This contains a problem that the stories are not equal size but when we experimented with this we used shirt sizes (S, M, L) and made a rule that only S and M size stories (Small enough) where only allowed inside the sprint. Our S was max 2 days and M max 5 days. We got to a point where our through out put was 3 stories per week (Small team: 2 devs + a test expert).
realstuffover 8 years ago
No. Agile does not work. Tasks will get delayed, need reviewing, etc, etc. A task is done when it&#x27;s done. Deal with it.
评论 #13253120 未加载