4 ms·
So basically you say "two days", while knowing that won't be two days - it's "virtual day". At this point how is it different from story point? :-) It's weird
by dzikimarian 4y ago
So basically you say "two days", while knowing that won't be two days - it's "virtual day". At this point how is it different from story point? :-)
It's weird how people whose half of work is coming up with clever abstractions, have so much problem with that one.
- woopwoop24 4y agobecause everyone could have a different opinion on what it actually means instead of just a simple time based measurement. The whole thing is just absolute bonkers
- dzikimarian 4y agoWell for a day I've already meet: ideal man/day, average man/day of the team, man/day of the guy doing estimate. Maybe estimation is complex thing and therefore team needs to align opinions before doing it?
- adammarples 4y agoWe never do that though, we have to estimate our own tickets. So we're always estimating time for ourselves, we just can't say it's time though. Drives me mad but scrum masters these days have fully drunk the kool aid, it's fixed adherence to meaningless fibonacci story points or you're not doing it right.
- TulliusCicero 4y agoYou don't know that it won't be two days. It's an estimate, it's possible that a junior will go quick or senior will go slow. That's why points aren't really necessary. Using days is still an estimate. That said, I don't really object to points, I object to the idea that they don't represent time, when they obviously do.
- dzikimarian 4y agoThey do. It's just your subjective time not objective that entire team needs to agree on. Which - more we discuss seems more and more impossible because it's more or less random how long it will take specific person.