Over the weekend I posted another 1800 words of QCon notes, including an extended description of what was for me the most important session of the conference, Modifiabilty, or, Is there Design in Agility?, which was Martin Fowler and some senior colleagues talking about important guildelines for projects (for instance, always knowing and being able to articulate the model). We’ve all been on projects that skipped or broke some of these rules, but I can’t think of a single case where that turned out to be the right decision. Well worth a read.
Picking up on BC’s “we should be leaders not followers” remark, if we were building our own list of practices-not-to-be-broken, what else would we include? Would we leave any of these out?