shortlived
Joined 16 years ago
Karma
1,273
Submissions
422
Member since
Sep 19
[email protected]
View on Hacker NewsJoined 16 years ago
I’m with a provider now who is phasing them out.
We do T-shirt sizes mapped to numbers, because recording effort in numbers lets you get an avg etc...
- plan in 2 week chunks
- estimate in points (relative size to something you've already done), emphasis on consistent estimates for each dev.
- make sure you define what 'done' means, and make sure it relates to what exactly you are trying to measure (Eg just coding effort, work till feature can ship?, etc). This is probably the most tricky bit.
- capture total velocity every 2 weeks and eventually use the avg for future planning
- review the entire process and modify things that take a lot of time for devs.