What do we mean by consistency? I know some people are going to say: "Hey! That's Dan Flavin's act. Why in the hell is Irwin doing a Dan Flavin? Why is he suddenly so inconsistent – fluorescent one day and Cor-Ten the next?" The key to all of this is that we have to examples what we mean by consistency. And here the critical question is: "what do we use to measure consistency with?" If you measure consistency in terms of material, or gesture, then I will be found inconsistent. But, in all of the recent pieces and proposals, if you go to the actual site and look at it, you will find that the solution is absolutely consistent on the grounds within which it responds to its environment. This in turn is consistent with my development of the implications implicit in non-object art. Robert Irwin, Robert Irwin: A Conditional Art consistency
What's suitable for each unique condition What of machines and prefabrication? How do they compare? Well, the machine has its limits. We, using handcrafted methods, do things that machines cannot do. Of course, it's not fast like a machine. And in complicated areas like here, things wouldn't go the same using a machine as it would by hand. We use numerous variations of all these connecting and splicing joints. Using a machine, [the wood joints] can all be made uniform, but really, we need to consider whether that's a good thing. It's better to make each mechanism and joint by considering what's suitable for each unique condition. Akinori Abo, Kigumi House Chopped and disfigured contextmachinesconsistency
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