Values and Principles

With any Agile Transformation, there are four values and twelve principles that will govern the processes and practices. These four values and twelve principles comes from the Agile Manifesto (www.agilemanifesto.org) as stated below.


Agile Values

Birth of Agile: February 2001 @ Snowbird ski resort in the Wasatch mountains of Utah.

value Image





Common philosophies in Light weight methodologies
For more information on the Authors and their background, Please click here:


We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:


value Image


Agile Principles

    Individuals and interactions over processes and tools:

  1. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  2. The best architectures, requirements and design emerge from self organizing teams.
  3. At regular intervals, the team reflects on how to become more effective, then tunes & adjusts its behavior accordingly (Retrospect).
  4. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  5. The most efficient & effective method of conveying info to and within a development team is F2F conversation (Co-location).
  6. Working software over comprehensive documentation:

  7. Working Software is primary measure of progress.
  8. Our highest priority is to satisfy the customer through early & continuous delivery of valuable software.
  9. Deliver working Software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  10. Continuous attention to technical excellence and good design enhances agility.
  11. Simplicity - the art of maximizing the amount of work not done - is essential (Design for today).
  12. Customer collaboration over contract negotiation:

  13. Business people and developers must work together daily throughout the project.
  14. Responding to change over following a plan:

  15. Welcome change in requirements, even late in development. Agile processes harness change for the customer's competitive advantage.


* The Agile Practices we look to implement should align with the Agile Principles and Values.

A true Agile Transformation will also embrace Lean values and principles. For the Agile Axiom framework, we leverage the original House of Lean by Taiichi Ohno for Toyota Production System (TPS) to guide our lean practices.




The A2F Framework distills the TPS House of Lean to the same 7 lean principles as first cited by Mary and Tom Poppendieck for knowledge work.


Lean Software Development



7 Forms of waste in Software

# Waste Example
1 Partially done work Code waiting for QA, Specs waiting for development
2 Extra processes Unused / over documentation, unnecessary approvals, bureaucracy
3 Extra features Less / no value adding for end user, gold plating, Technology showcase
4 Task switching People assigned multiple projects
5 Waiting / Delay for reviews, approvals, clarification, guidance, dependency (internal / external), feedback, slow communication…
6 Motion Info / deliverable movement from one to another Distributed teams, hand-off
7 Defects Defective documents, requirements or software



  1. http://agilemanifesto.org/
  2. http://agilemanifesto.org/principles.html
  3. Lean Software Development: An Agile Toolkit by Mary Poppendieck and Tom Poppendieck. Addison-Wesley Professional 2003.
About Me

Sed pellentesque nibh enim, quis euismod enim lacinia nec. Phasellus quam diam, semper in erat eu. Consectetur adipiscing elit. Sed pellentesque nibh enim, quis euismod enim lacinia nec.