A LEADERSHIP TEAM’S AGILE MANIFESTO
In 2001, seventeen self-described “organizational anarchists” met for three days to discuss more adaptive ways of developing software. They released what they called the Manifesto for Agile Software Development, describing the practices they had learned to value most:
- individuals and interactions over processes and tools
- working software over comprehensive documentation
- customer collaboration over contract negotiation
- responding to change over following a plan
As we serve clients transitioning to agile enterprises, we often facilitate similar discussions with their agile leadership teams, helping them to customize and commit to their own version of an agile manifesto. By the end of the discussion, ...