Processes are needed for sanity, and not much else. Don’t be the baker who’s really firm on a choice of a 9x13 pan and the entire set of ingredients for a cake

Processes are needed for sanity, and not much else. Don’t be the baker who’s really firm on a choice of a 9x13 pan and the entire set of ingredients for a cake, only to find out that people want cookies. To move quickly, you really need just two things: a way to make sure things don’t change unexpectedly, and a way to recreate anything you had before (where the 2nd is a crutch if the 1st fails). To have sanity, you need somebody setting a direction (“we’re doing this”), and somebody deciding what can wait. For software, this means things like: “for Pete’s sake, use revision control”, “track versions of dependencies”, “back things up”, “write scripts instead of step-by-step instructions”, “test somehow”, and “track problems”. There is no “daily one hour meeting” phase of software development.