Why we stopped breaking down stories into tasks An Article by Adam Silver adamsilver.io 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. Why We Don't Do Daily Stand-Ups at Supercede agile
We'll slap a little color on this piece of junk "The one thing Apple's providing now is leadership in colors," Gates said as he pointed to a Windows-based PC that he jokingly had painted red. "It won't take long for us to catch up with that, I don't think." Jobs was furious, and he told a reporter that Gates, the man he had publicly decried for being completely devoid of taste, was clueless about what made the iMac so much more appealing than other computers. "The thing that our competitors are missing is they think it's about fashion, and they think it's about surface appearance," he said. "They said, We'll slap a little color on this piece of junk computer, and we'll have one, too." Walter Isaacson, Steve Jobs On Taste