The latest of the agile manifestos, in a long line of manifestos, has been launched today, called the H-A Manifesto. Read on to find out if you can apply it in your organisation.
In February it will be 10 years since a group of self-styled “anarchists” got together in Snowbird, Utah to discuss and debate their ideas on better ways to build software and founded the Agile Alliance. To commemorate a decade of agility, InfoQ is running a series of articles; we have invited all of the original signatories to contribute along with others in the Agile community. Updated 3/16.
The Agile 2011 conference organizers have announced that 16 of the 17 original authors of the Agile Manifesto will be reunited at the conference in August to answer questions and share their insights. Signatories will take the stage at a special event on the Monday evening and be available in the Open Jam area over the five days of the conference.
Ten years ago a group of software professionals gathered in Snowbird, Utah. Seventeen people created and signed what we now know as the Agile Manifesto. Alistair Cockburn is organising a reunion to celebrate the event on 12 Feb 2011. Alistair gave InfoQ a short interview to tell us what is happening.
Alistair Cockburn is a signatory of the Agile Manifesto, a book author, a keynote speaker at numerous Agile conferences, and most recently, the spokesperson for ICAgile.org, a credentialing body offering several levels of Agile certification. This is a multi-part interview that covers a wide range of current topics in the Agile space.
The Agile Manifesto was written almost ten years ago in February of 2001. Since then the environment has continued to change and thousands of people across the world have tried to apply the twelve agile principles to their daily work life. Laurie Williams has been conducting research to understand how well the Agile Principles have stood the test of time and use? She discusses some early results.
SEMAT was founded in November 2009 with the bold claim that the software industry has too many fads and immature practices. The signatories promised to refound software engineering and bring it into the modern age.
Software development is known to be a creative process. The failure of traditional methods, where the dynamic environment of software development was ignored, made Agile methods fairly popular. There has been a growing adoption of Agile methodologies, particularly Scrum. However, is everything all right with Agile? Kai Gilb does not think so. He suggested that there are serious flaws with Agile.
Jean Tabaka, Liz Keogh and Eric Willeke got together to contribute something to the "Lean Software and Systems Consortium". Instead they realized the Software Development Community (Lean, Agile, Kanban and well beyond) needed a help remembering the importance and value of true community.
In a casual interview, InfoQ got to talk with James Shore about some of the topics he's been most vocal about lately, including his Art Of Agile book, recent waves of watered-down agile, and how Kanban might be less than the whole picture.
While Scott Ambler, Ross Pettit and others continue to pursue the creation of a maturity model for agile, David Starr has looked at how and why an organization might want to measure things like: agility, craftsmanship, and organizational success. He found craftsmanship relatively easy to measure, while agility was the most difficult to measure in a useful way.
Many people have noted that the presence of trust in your agile team is a fundamental component in successfully implementing the Agile Manifesto value of "Individuals & Interactions". Esther Derby offers five concrete suggestions to help build this trust.
A movement to promote Software Craftsmanship has been brewing for a few years. Since Agile 2008 last year they found a focal point with Uncle Bob Martin's claim that the Agile Manifesto needed amending with a new value: "Software Craftsmanship over Crap". Recently a group has created the Software Craftmanship Manifesto.
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.
In his keynote at the Agile Development Practices conference, Brian Marick described values missing from the Agile Manifesto. His view is that the Manifesto was essentially a marketing document, aimed at getting business to give agile a chance. Now that this goal has largely been achieved, an extended set of guiding values are needed to help teams deliver on the promises of the manifesto.