Overview[1]#

Agile refers to a set of values and Principals 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!

Agile’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 Agile.

Any project that follows the Agile Manifesto & Agile Principles can rightly be considered to be Agile. That said, there are definitely preferred practices that are common for Agile 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 and Testing in Production)
• PDCA

Agile teams work differently from Command-and-Control Management bureaucracies. They are largely self-governing:

• Senior leaders 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:

• API Economy
• Agile Principles
• Agile Task
• Backlog
• Business value
• Cloud Native
• Continuous Development
• Daily Stand-up
• Definition of Done
• Delivery Team
• Deming
• DevOps
• Emergent Design
• Epic
• Extreme Programming
• Increment
• Kanban
• Last Responsible Moment
• Lean
• Lean Product Development
• Non-functional requirement
• PDCA
• Preparation, Enforcement, and Comparison of Internationalized Strings
• Red Green Refactor
• Release
• Release Management
• Release Planning
• Requirement
• Responsive Organizations
• Sprint
• Story Point
• Velocity
• Web Blog_blogentry_160718_1

---

• [#1] - Agile Vs. Lean: Yeah Yeah, What’s the Difference? - based on information obtained 2016-09-03-