[Pamar]

I am aware of Kanban’s origin and also of the checklist manifesto. My question wanted to stimulate pondering/debating about what a “methodology” is supposed to be and what, exactly, is trying to accomplish. A lot of the comments seem to say that “above average developers will always find the most productive way to self-organizing.

Letting apart the problem in always finding “above average people” - at least for now - I think that this has a fatal flaw: what happens when someone leaves and/or someone else joins the group?

I suppose that Hospitals and the Army have this happening fairly often, they must have “methodologies” catering for a wide spectrum of talents, and also accomplish satisfactorily results even when dealing with thorny, unexpected problems.

What do they use? Is this a “methodology”? (One important thing that I am not sure is adequately represented in IT methodologies is having an established vocabulary to describe situations: we have “Patterns” but these are low-level, and divorced by the actual business-specific scenario - this is just one example but I think it helps pointing out that IT methodologies are trying to standardize the wrong elements).