Clarke asked me to explain my earlier throw-away remark that YAGNI forms part of the EXPLOIT step in moving the bottleneck away from development, so here goes… YAGNI (You Aren’t Gonna Need It) is an exhortation from the early days of XP. It has been discussed and misunderstood a great deal, so I’m not going […]
I just had a thought about the relationship between software development and the Theory of Constraints. It probably isn’t a new thought, although it seems to differ from some of the analyses I’ve seen elsewhere. Also, I probably won’t be able to express it in any coherent way; but here goes…
Everywhere I go I find managers complaining that some team or other is short of staff; and (so far) that has always turned out to be a mirage. TOC’s 5 Focusing Steps say that adding resources to the bottleneck is the last thing one should do. Before that, a much more cost-effective step is to […]
My apologies if this has been said or written a thousand times before: YAGNI is XP’s way of exploiting the constraint. Which means that XP, and hence most agile methods, are set up on the assumption that the development team is – or soon will be – the bottleneck. And having identified that bottleneck, our […]
When diagnosing a system’s throughput, its worth remembering that the constraint is as likely to be in knowledge management or communication as anywhere
In which our lack of backlog items is explored using the theory of constraints
I’ve been accepted to run a workshop at XPday Germany
