1 voteJoseph Little commented
One of the concepts (not sure how explicit this has been made) is NOT to worry (much) about inputs and to focus on increasing outputs.
One can argue that the only real output (in software) is a software release.
But, for sprints we have settled on the concept that the stories (done-done) are the key output.
Hence, putting too much focus on tasks (which are sometimes wrong or incorrect or incomplete or unnecessary) ... would focus on input (to getting a story done) and NOT outputs.
I do agree that most beginning teams need tasks to, among other things, learn to work more tightly together. (Which might be contrary to how the tasks are used. Haha.) Still, tasks can be used that way. Collaboration is a key principle.
5 votesJoseph Little commented
The impediment list is an action list for the SM to get right people (including himself) to get it done. As always, the usual improvement expected from each one is an increase in velocity, but it could be seen as increased happiness, higher quality, more business value, or in some other way.
The key principle is that the SM get the most important (small piece) impediment mitigated first. (Single piece continuous flow.)
It's hard to prioritize a list if you don't have a list.
5 votesJoseph Little supported this idea ·