I like this. For me it speaks to a general Open* approach. Favoring open source, open standards, open data. Initiatives that support community engagement and diversity rather than ownership of intellectual property.

It would be interesting to think about how we want to build things (including processes like this) in a collaborative manner that sees that we are both inclusive, but also able to produce the goods and services that ultimately need to be delivered.

There is a lot of hype around agile approaches to development. Lots of good ideas, particularly when compared with a hierarchical waterfall methodology.

Having spent two decades trying to work with non-profits to build tools together that help us collectively build a better alternative to what advanced capitalism has to offer, I’m not sure that refashioning a manifesto will do much.

At the end of the day most non-profits are still after the “shiniest widget for the cheapest price”. If the organization believes agile will give that to them, great. There is risk in any process. The challenge is to get organizations to think long-term and to come to terms with technology being a critical part of any effective business.

Thanks for putting forward this critique though and gathering this history (or perhaps herstory) in one place. Nice to have these together for deeper consideration.