New ideas to complement the agile manifesto
The agile manifesto was awesome! It set the tone for how humans would build software in the first two decades of the 21st century. But as teams get more distributed, as collaboration tools improve and as software development gets more sophisticated, we'll need a few additional guiding principles to build software in teams. The async-first manifesto seeks to articulate such principles and values.
The async-first manifesto
We are still uncovering better ways of working in distributed, knowledge work teams, by practising agile for two decades and more. Through this work we’re coming to value:
How effectively we work over where and when we work
Intentional actions over serendipitous success
Focus and cognitive flow over always-on availability
Courage to experiment over upholding established practices
That is, while there’s value in the items on the right, we value the items on the left more.
Principles for modern, async-first work
These principles complement the 12 principles of the Agile Manifesto.
The productive output of knowledge work doesn’t increase proportionately with the number of hours worked. Effective teams measure results, not hours.
The location of work impacts people’s productivity and happiness. If you hire talented people, trust them to identify a work location from which they’ll deliver the most value.
When a team agrees on its work processes, it helps to reduce guesswork about how to solve problems.
Effective distributed teams leverage modern collaboration tools to scale communication and reduce confusion.
Documentation, in particular, written communication is the most scalable, and least intrusive way to share information in a distributed team.
Meetings are the last resort, not the first option. Implement asynchronous workflows to avoid interruptions through meetings.
On a team, anything that anyone knows, everyone else should have a way to know, with little effort. Distributed teams must invest in systems that make knowledge transparent and easy to retrieve.
Diverse teams with inclusive work practices make the most sound decisions. Location independence and asynchronous communication help improve inclusion in teams.
The more decisions a team makes, the more progress it makes. Teams should endeavour to make smaller, more frequent decisions, so that every decision feels manageable.
Effective teams benefit from autonomy to make decisions. To encourage a bias for action, teams must push decisions to the lowest level possible.
Effective leaders on distributed teams leave nothing to chance. They learn from experience and design systems iteratively, for the outcomes they must achieve.
Trust and cohesion on teams are hard to build through purely asynchronous means. Teams must plan an appropriate level of in-person and synchronous interaction to build interpersonal relationships.
Contributors to the manifesto
Pilar Orti, Lisette Sutherland, Niels Anhalt, Cliff Berg, Satish Kumar Viswanathan, April Johnson, Laïla von Alvensleben, Judy Rees, Nagarjun Kandukuru, Petula Guimaraes, Alex Garner, Luis Mizutani, Mehmet Yitmen, Elena Yatzeck, PhD, Quico Reed, Fredy PASCAL, Max Ludwig.
The discussion must continue
The manifesto you see above, isn’t perfect and it’ll stay a work-in-progress. We have a stable version on this page, but please continue to debate the values and principles in this document. That document will also help you see the versions we released, before we got to the version 1.0 text.