Prescribe a productivity model that is not just Velocity or Story Point based but focused on timely delivery of tasks *within* the Sprint.
That is, give priirity to delivering tasks as per estimate over tasks delivered per Sprint as measure of high productivity.
1 commentComments are closed
Joseph 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.