3 ms·
Thanks. My teams have always estimated in hours (though at times these hours were called points) so I was a bit frightened to hear that an estimation of 13 hour
by kqr 4y ago
Thanks. My teams have always estimated in hours (though at times these hours were called points) so I was a bit frightened to hear that an estimation of 13 hours would be considered bad! I guess if 13 means 26 person-days I get why people would be nervous – even I would suggest breaking it down into smaller pieces, if possible!
- Scarblac 4y agoThe main point of points is that they are not supposed to be equivalent to x amount of time. They're supposed to represent a measure of complexity. How much time that then takes depends on who does the work, the order in which tickets are implemented, how much distraction there is, luck (do you encounter any unforeseen problems), and so on. They're then used to see how many issues will fit in a sprint, which is a measure of time. So everybody ends up treating them as representing time anyway...
- re-thc 4y agoThat’s the theory but it doesn’t help managers so they still convert it back to time somehow.
- hgsgm 4y agoScrum was never for managers. If a manager is involved in predictions, it's not scrum. Scrum is about delivering the best you can each month, with client/management setting priorities and then appreciating what they get, instead of trying to steer the car from the boot.
- re-thc 4y agoSure, I get what scrum is. "Scrum" in the real world isn't that though - at least 80% of the common case (check the other comments).