7 points nifragos 3 days ago 3 comments
pythonic_hell 2 days ago | parent
wasabinator 2 days ago | parent
Then there is task sizing "oh it's not a time estimate" they say, then they schedule n points per two weeks, with the work sized in "not a time estimate" points now literally converted into a time estimate on the team's behalf. In addition, it then gets phrased as a "commitment" by the team of what will be delivered.
Kanban is really the only honest form of agile, with no wasted upfront planning commitment. Take top card, move it to completion, repeat. Prioritisation moves the card order and it doesn't have to be the devs job, more a product person can decide that.
gregw2 2 days ago | parent
The author doesn't discuss kanban which is less overhead, but then makes collaboration acrossultiple scrum teams a bit trickier actually.