Agile Manifesto. Can You Define Agility? Most years, just after the first of January, I fly to Hawaii and while escaping the New England winter is a bonus, my real reason is to attend the Hawaii International Conference on Systems Sciences (HICSS.)
The conference is pretty broad, but one of the tracks focuses on research into Agile practices. Most years I present a paper, this year I shared some of the latest research I’ve been doing on how teams that finish early accelerate faster. Conference attendees voted it the best paper in the Agile track and nominated it for best paper overall. A paper that grabbed my attention with its title alone is: State-of-the-Art: A Systematic Literature Review on Agile Information Systems Development. What is Agility? There is no Agility for Dummies.
Agility isn’t a silver bullet. You don’t achieve it in five easy steps. What Agile Is — And What It Isn’t. This article was originally featured at ProjectsAtWork and is reprinted here with permission.
What is Agile? Agile is a philosophy of product development that uses organizational models based on people, collaboration, and shared values. The phrase “Agile” was coined in February 2001 at a summit held in Snowbird, Utah. Attending were people who had been practicing ways of developing software that took advantage of the collaborative and creative energies of teams and the quality that comes from building learning in as one progresses. During the summit these folks defined their commonalities and created an Agile Manifesto, which details their philosophy of product development and the principles that drive Agile teams.