Some key points from the article:
As we said before, Agile was initially used as a business model for software development companies who found their industry becoming burdened by the same stale business interactions that public procurement is feeling. The model is based around 4 core values and 12 principles described in the Agile Manifesto, which is worth reviewing to understand the philosophy.
The 4 core values are:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
There are also 12 principles demarcated in the Agile manifesto; however, we’ve found that all 12 aren’t particularly useful for public procurement purposes, so we’ve narrowed it down to just 5. These 5 principles stand out from the rest in situations that involve securing goods and services:
- Welcome changing requirements, even in late development.
- Deliver working software (solutions) frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Simplicity—the art of maximizing the amount of work not done—is essential