Agile is NOT Dead!

...though it's spirit just might be.  IMHO.  

So many folks think that Agile is a license to freelance and/or freewheel.  Many companies look at it as a way to get more sausage out of the grinder, faster. Couple these two schools of thought together, and you have- well, what we have today.  A mess.

The former school of "freelance and freewheel" results in a lack of structure, directionality.  I don't ever recall in any of my readings or successful experiences in agility, Scrum, the Agile Manifesto, etc- saying anything about 'doing what feels good', 'do it in spite of modern convention', or 'do it because of modern convention'.  In contrast, the later school of "more and faster" lacks the focus on craftsmanship and quality.  On that note, here is a quick refresher on the principles of the agile manifesto and what I believe are the areas that capture the spirit and intent of Agility.

Flexible Structure:
-Welcome changing requirements, even late in development.  Agile processes harness change for the customer's competitive advantage.
-Build projects around motivated individuals.  Give them the environment and support they need, and trust them to get the job done.
-Agile processes promote sustainable development.  The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Directionality/Collaboration:
-Business people and developers must work together daily throughout the project.
-The most efficient and effective method of conveying information to and within a development team is face to face communication.
-At regular intervals, the team reflects on how to become more effective, and then tunes and adjusts its behavior accordingly. 

Craftsmanship:
-Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
-Continuous attention to technical excellence and good design enhances agility.
-The best architectures, requirements, and designs come from self-organizing teams.

Quality
-Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
-Working software is the primary measure of progress.
-Simplicity -- The art of maximizing the amount of work not done -- is essential.

I find great value in reading the principles of the agile manifesto with fresh eyes on a yearly or better basis.  It's a great ice-breaker/activity for your teams too; as well as the obvious benefit of some re-grounding.