Probably you already hear Agile process at least one time in your software development life. Yes, this word becomes very popular nowadays. Google 'Agile' return many search results, you can see many successful case studies of Agile also the failures too. Many blames to Agile such as 'no documentation at all', 'suitable for small projects only', 'Agile is worth for process consultant not for enterprise' etc. Actually, Agile process is not suitable for all teams, it is different with older process (that the old manager already have experience) that it focuses on people, their skills and work attitude not project artifacts (use-cases, design document, process checklists, various project reports). The different focused items could cause guy, who is familiar with traditional process model, confused. If you want to applying Agile process to your real project (or the pilot one), your team must meet some pre-conditions to meet Agile, if not your project probably be failed

Picking the Right Project Team by Kent McDonald. While at the Agile 2007 Conference a couple of weeks ago, a project manager from a small development shop ...

VersionOne is the leading project planning and management tool designed ... Agile Development Poster: Accelerate your team's success with Agile core values. ...

The word 'agile' has become popular in software development and project management circles, as the agile method produces quality product speedily in a very flexible and organic way. Agility, however, describes much more than a method for software development and speaks right to the core of project team formation and development. The individuals, project team, and team building process itself all need to be agile in today's demanding environment.

Ian Clatworthy escribe sobre una metodología de desarrollo de software que combina Agile con los procesos comunitarios del software libre, para guiar el sistema durante su evolución.