!!! Overview[1]
[{$pagename}] refers to a set of values and [Principals|Agile Principles] put forth in the [Agile Manifesto]. 


The [Agile Manifesto] was a reaction against heavyweight methodologies that were popular, yet crippling software projects from actually doing what they needed to do – create software that helped the [customer]! 

[{$pagename}]’s values ([Agile Manifesto]) & [Agile Principles] work because of the science behind [Lean Product Development] and so you'll see a lot of similar themes repeated in [{$pagename}].

Any project that follows the [Agile Manifesto] & [Agile Principles] can rightly be considered to be [{$pagename}]. That said, there are definitely preferred practices that are common for [{$pagename}] [Delivery Teams] to follow in order to achieve agility. Most commonly:
* [Scrum]
* [Kanban]
* Extreme Programming (XP) for Technical Practices (with new practices becoming popular, largely from Lean Startup – such as [Continuous Deployment|Continuous Delivery] and Testing in Production)
* [PDCA]


[{$pagename}] teams work differently from [Command-and-Control Management] bureaucracies. They are largely self-governing: 
* Senior [leaders|Leadership] tell team members where to innovate but not how. 
* And the teams work closely with [customers], both external and internal.

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Agile Vs. Lean: Yeah Yeah, What’s the Difference?|http://hackerchick.com/agile-vs-lean-yeah-yeah-whats-the-difference/|target='_blank'] - based on information obtained 2016-09-03-