m o t i o n l e s s
m o t i o n l se s
m o t i o n sle s
m o t i osn l e s
m o t i so n l e s
m o t si o n l e s
m ost i o n l e s
m so t i o n l e s sm o t i o n l e s s om t i o n l e s s o m t i no l e s s o m t ni o l e s s o m nt i o l e s s o m n t oi l e s s o m n oti l e s s o m n o t lie s s o m n o lt i e s s o m n o l it e s
I've been tracking my listening habits with last.fm since I was in high school. As I'm about to turn 30, it's nice to be able to look back on almost my entire adult life – to see how I've changed and how my tastes have changed with me.
The Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint.
But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this:
Breaking down stories into tasks is time consuming
The tasks we came up with invariably would change as we worked on the stories
Tasks are repetitive
Tasks were often carried out in parallel
Our estimates didn't improve
It decluttered our task board
It encouraged collaboration throughout the sprint
While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace.