in reply to Re^2: Beyond Agile: Subsidiarity as a Team and Software Design Principle
in thread Beyond Agile: Subsidiarity as a Team and Software Design Principle

I would agree that anarchy is no substitute for design. You can't have top-notch security without design for example.

The problem is that usually we are given a false choice of "let's do the blueprints first and fully design everything to the smallest detail and then code" and "let's just start coding." In reality the choice isn't between micromanagement and anarchy, but between segmented responsibility with coordination and either of those two. In my view, segmented responsibility is the clear winner.

  • Comment on Re^3: Beyond Agile: Subsidiarity as a Team and Software Design Principle

Replies are listed 'Best First'.
Re^4: Beyond Agile: Subsidiarity as a Team and Software Design Principle
by Your Mother (Archbishop) on Jul 21, 2015 at 15:43 UTC

    I was arguing the philosophy leading up to the statement was misguided and that a master plan (strategy) cannot be directly applied in daily work (tactics).

    Segmented responsibility, which I agree is the way things work best in the world, not just project management, looks like anarchy from 10,000 feet or on a 10 year project plan. Intelligent design, crock that it is, has been a persuasive idea for all human history because self-interested "anarchy" churns out things like spider silk, gecko toes, echolocation, and mantis shrimp eyes and claws in immeasurable amounts.

[reply]
    A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Meditations