On Teamwork What I’ve always felt that a team of people doing something they really believe in is like, is like when I was a young kid, there was a widowed man that lived up the street. He was in his 80’s, and a little scary looking, and I got to know him a little bit — I think he paid me to cut his lawn or something — and one day he told me, “come into my garage, I want to show you something.” And he pulled out this dusty old rock tumbler. It was a motor and a coffee can and a band between them. And he said “come out here with me,” so we went out to the back and we got some rocks, just some regular old ugly rocks and we put them in the can with a little bit of liquid and a little bit of grit powder, and he turned the motor on and said “come back tomorrow,” as the tumbler was turning and making a racket. So I came back the next day and what we took out were these amazingly beautiful and polished rocks. The same common stones that had gone in — through rubbing against each other, creating a little bit of friction, creating a little bit of noise — had come out as these beautiful polished rocks. And that’s always been my metaphor for a team working really hard on something they’re passionate about. It’s that through the team, through that group of incredibly talented people bumping up against each other, having arguments, having fights sometimes, making some noise, and working together, they polish each other, and they polish their ideas. And what comes out are these really beautiful stones. Steve Jobs, Steve Jobs: The Lost Interview teamworkpassionargument
To prove it in purity The series of photos of the 1959 model ends or stops with the photograph in which Kiesler triumphantly shows us the shell of his house like the remains of a creature taken from the seabed, a kind of Moby Dick harpooned and finally captured after the obsessive pursuit of a project that has taken up ten years of the life of the architect. "I think that everybody has only one basic creative idea and no matter how he is driven off, you will find that he always comes back to it until he has a chance to prove it in purity, or die with the idea unrealized." — Frederick Kiesler Smiljan Radić, Some Remains of My Heroes Found Scattered Across a Vacant Lot creativitylifeobsessionpassion
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