The other way to build a massive tech company - doing it slowly A Podcast by Howie Liu www.secretleaders.com I like to think about the early years of [Airtable] as not only a great time for us to be patient and to get a lot of details right in the product. I think some of those details had to be done in a slow, deliberate way with a small team. You can't necessarily parallelize the design and development of a really detail-oriented product. detailsproductsslowness
the speed of God An Article by Alan Jacobs blog.ayjay.org [Andy Crouch] quotes the Japanese theologian Kosuke Koyama saying that “the speed of God” is three miles an hour because that was the speed at which Jesus moved through his world. So maybe, and I think this is one of the chief burdens of Andy’s book, what makes the most sense for us is to try whenever possible to move at the speed of God – and in that way refuse the offer of superpowers. Of course, this dovetails with a lot of things people have been writing lately about slowness, but what I like about Andy’s book is that it specifies why we can find ourselves responding so warmly to the possibility of slowness. What happens when we seek superpowers, and especially super-speed, is the sacrifice of what I want to call our proper powers – the powers through the exercise of which we (heart-soul-mind-strength) flourish in love. The brain is wider than the sky religionloveeuphonyslowness
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