8 ms·
It kind of is. Well, the public dinging probably isn't. But at a few companies I've seen, teams are tracked on how many tickets span multiple sprints. If it exc
by hiyer 3y ago
It kind of is. Well, the public dinging probably isn't. But at a few companies I've seen, teams are tracked on how many tickets span multiple sprints. If it exceeds some threshold, then theoretically it means that either:
1. The team is not breaking down tasks granularly enough, or
2. They're not estimating tasks correctly
Practically, it means nothing of course.
- foogazi 3y agoIn Scrum: - the product owner sets the backlog priority - team estimates - team commits to what it can deliver from the backlog - any misses are analyzed for scope mistakes Rinse/repeat There’s no shaming part Edit: format
- seadan83 3y agoThe scrum guide [1] says team gives a forecast and not a commitment. I have yet to know any other scrum practitioners aware of that update. Unless a person has no shame, failing a commitment I certainly believe is intrinsically shameful. Some cultures would commit seppuku if you don't deliver on a commitment. The words, "you failed on your commitments" seems very much like shaming. Thus the move to "forecast" over "commitment" [1] https://www.scrum.org/resources/commitment-vs-forecast https://www.scrum.org/resources/commitment-vs-forecast *edit (addendum): Invoking 'seppuku' might be a bit sensationalist, my apologies. The southerner in me is coming out - saying someone does not live up to their word is a very big deal.