are.na An Application by Charles Broskoski www.are.na Build ideas mindfully. Save content, create collections, and connect ideas with other people. ObsidianRoam ResearchWhat this site isOn Motivation thinkingnetworkshypermedianotetaking
On Motivation An Essay by Charles Broskoski www.are.na I’ve had this (semi-vague) idea that I want to write about what keeps us excited to work on Are.na, on the occasion of its 10th (yes 10th) birthday. While writing generally is a tricky process for me, this subject motivation is even trickier. In turning this subject around in my mind, and thinking about all the people and things that have been influential, I have some idea about what keeps us going. Nodal pointsInfinite varieties of contextsA lifelong projectGrowing in the correct way are.naThe slow blade penetrates the shield
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