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
Whomst styles? An Article by Robin Sloan www.robinsloan.com This is a “whostyle”: an attempt to carry the ~timbre~ of an author’s voice, in the form of their design sensibility, through into a quotation. It’s the author who defines their whostyle; the quoting site just honors it, a frame around their words. I think the whostyle makes a few arguments. Among them: Text is more than a string of character codes. Its design matters, typography and layout alike; these things support (or subvert!) its affect, argument, and more. The web should be more colorful and chaotic, along nearly every dimension. The past five years have brought a flood of new capabilities, hugely expressive — let’s use them! Quoting is touchy, and anything you can do to cushion it with respect and hospitality is a plus. Whostyles hypermediatypographystyleblogging