Gilb’s 10 Agile Principles
Jump to navigation Jump to search
- Control projects by quantified critical-few, results. 1 Page total!
- Make sure those results are business results, not technical.
- Give developers freedom, to find out how to deliver those results.
- Estimate the impacts of your designs, on your quantified goals.
- Select designs with the best value impacts for their costs, do them first.
- Decompose the workflow, into weekly (or 2% of budget) time boxes.
- Change designs, based on quanti- fied value and cost experience of implementation.
- Change the requirements, based on quantified value, cost experience, and new inputs.
- Involve the stakeholders, every week, in setting quantified value goals.
- Involve the stakeholders, every week, in actually using value increments.
Where do these come from?
- Critical Stakeholders determine the values.
- Values can and must be quantified.
- Values are supported by Value Architecture.
- Value levels are determined by timing, architecture effect, and resources.
- Value levels can differ for different scopes (where, who).
- Value can be delivered early.
- Value can be locked in incrementally.
- New Values can be discovered (external news, experience).
- Values can be evaluated as a function of architecture.