Why We Don't Do Daily Stand-Ups at Supercede An Article by Jezen Thomas jezenthomas.com Yesterday I worked on the widget. Today I will work on the widget. I have no blockers. Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery. What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down. Why we stopped breaking down stories into tasks agile
The most rewarding iterations Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications. Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk. Niklaus Wirth, A Plea for Lean Software So that you can get feedback on it and make it betterTo anticipate all the uses and abuses agileiteration