It sounds as though Fox is making a procedural argument against post-and-forfeit. But what about the validity of the arrest ab initio? Judicial economy is a poor argument for speedy processing of a bogus arrest. (Or put another way, nothing's more economical than leaving the guy alone.) I'm suspicious of anything that justifies many arrests but few prosecutions. Don't you think DC police (and others) are abusing the charge of disorderly conduct? Do the officers actually not understand the elements or do they not care because there is no realistic penalty for overstepping? In that vein, why are there not more complaints of false arrest?

Very interesting perspective. It sounds a little bit like biodiversity; you're better off having a variety of solutions, even at the cost of sometimes not applying the very best one. Because the diversity itself is part of the solution too.

If by "here" you mean this team with this mission, it's certainly possible for a given software method to not work "here." E.g., the method is RUP but I have three very sharp C++ developers. Overkill. E.g., the method is TDD but the environment simply doesn't support testing hooks. E.g., the method is any kind of Agile but the management is not willing to yield any degree of control. The contrary assertion to "this method won't work here" must be "this method will work here," and your claim is global. I don't think you can support "this method will work everywhere" though.

I'm just saying I wish I happened upon this about three months ago. A huge advantage of smaller user stories is that they move through the Kanban (or other workflow) so much more quickly. That avoids deadlocking and keeps team members usefully busy more of the time. It's that "seamless flow of small, valuable changes" Matthias talks about. It really is better.