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
AI-driven "Design"? An Article by Jorge Arango jarango.com Like a programming language interpreter, GPT-3 translates the designer’s intent from a language they’re already familiar with (English) to one they need to learn (Figma’s information architecture, as manifested in its UI.) This can be easier for a new/busy designer, much like Python is easier and faster to work with than assembly language. But that’s not “designing” — at least not any more than compiling Python code is “programming.” In both cases, all the system does is translate human intent into a lower level of abstraction. Sure, the process saves time — but the key is getting the intent part right. I’ll be convinced the system is “designing” when it can produce a meaningful output to a directive like “change the product page’s layout to increase conversions.” aidesignintentabstraction