Manifesto for Async Software Development

I hate useless meetings as much as the next developer, but there are certain issues that can be much more efficiently resolved if you have all the parties sitting around the same table (or video conference, for remote workers). Especially if you're working on a complex product where it's not immediately obvious how something should be designed or implemented.

For the record, I'm not a fan of daily stand-up meetings. Most of the stuff I work on is complex enough that there isn't that much measurable progress to report after one day. Day to day status can be posted in an issue tracking system. My theory is that the daily meetings were designed to instill an artificial "sense of urgency" in workers.

The page addresses "necessary meetings" further down.

Anyways, for anyone trying to grok this:

Agile:

1) Individuals and interactions over processes and tools

2) Working software over comprehensive documentation

3) Customer collaboration over contract negotiation

4) Responding to change over following a plan

Async:

a) Modern tools and flexible work environments over meetings and office hours

b) Flexibility in prioritization over detailed planning

c) Comprehensive documentation over tribal knowledge

Whats changed:

(a), and (1) are at complete odds.

(b) is (4) restated

(c) is some kind of patch of (2)

(3) isn't mentioned.

Also if you're wondering about the crappy design, I'm guessing its a pisstake of the original http://agilemanifesto.org/