Working with Brian Eno on design principles for streets An Article by Dan Hill & Brian Eno medium.com Think like a gardener, not an architect: design beginnings, not endings Unfinished = fertile Artists are to cities what worms are to soil. A city’s waste should be on public display. Make places that are easy for people to change and adapt (wood and plaster, as opposed to steel and concrete.) Places which accommodate the very young and the very old are loved by everybody else too. Low rent = high life Make places for people to look at each other, to show off to each other. Shared public space is the crucible of community. A really smart city is the one that harnesses the intelligence and creativity of its inhabitants. collectionsurbanismstreetscitieswastegardens
The answer to a brief is not necessarily a building An Article by Dan Hill medium.com This brilliantly engaging book may actually be one of the first to describe and discuss what might be architecture’s true value at this pivotal point in our own history: seeing that everything is connected, and artfully hosting that complexity, before constructively plotting routes towards clarity, pinned up on broad civic, ethical foundations. So Architects after Architecture, as the title suggests, is not about buildings. Or at least not always, not directly. Buildings are simply one of the ways that this complex yet constructive sensibility might exert itself, but they are certainly not the only way, nor are they always the most potent – as muf’s Liza Fior makes clear here, when she says “the answer to a brief is not necessarily a building.” The Best Interface is No Interface architectureconnection
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