How to Get Your Best Ideas to Market Faster
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. — Agile Principle #12
This is the final Agile principle and, on the surface, it wraps up the principles in a nice package — closing with encouragement for teams to make their own decisions about how to work more effectively.
This seems both simple and obvious yet it’s one of the most challenging tools in the Agile toolbox.
The best architectures, requirements, and designs emerge from self-organizing teams. — Agile Principle #11
Of the 12 Principles behind the Agile Manifesto, this is the one with the smallest levels of adoption even among Agile Software Development teams, and the least well-understood. Most Agile experts and organizational development writers equate self-organization with autonomy — the ability of a team to make its own plans and decide for itself how to best accomplish its goals — and acknowledge that this is challenging to implement inside most corporate structures.
We had such a great response to the Spot Check case study from David Stokes that we’ve embarked on a campaign to identify more members of our community willing to contribute one. These stories help those considering Rapid Learning Cycles to envision what it might look like in their own organizations. We know that if […]
Simplicity–the art of maximizing the amount of work not done–is essential. — Agile Principle #10
A simple development process is a lean, efficient process with no unnecessary work.
This principle is the most direct connection between the Agile Manifesto and lean thinking, which calls for the elimination of all “unnecessary waste” from processes, and the minimization of “necessary waste” that a process needs to run, but that does not directly add value. In software development, value is in the form of working software, and everything else is waste.
A Simple Process Has Less Waste
To accelerate innovation, we have to push decisions later.
This is the most challenging idea within the Rapid Learning Cycles framework — the one that generates the most raised eyebrows — and the most essential concept to embrace if you want to accelerate innovation.
It seems to go against everything we think we know about how to get things done fast…
