InfoQ Homepage Agile Manifesto Content on InfoQ
-
What does it mean to be Agile - survey results
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 - Software Engineering Method and Theory
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.
-
Uncovering Serious Flaws of Agile and Scrum
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.
-
A Community of Thinkers
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.
-
James Shore With More On Keeping It (Agile) Real
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.
-
Measuring Agility, Craftsmanship, and Success
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.
-
Five Ways To Build Team Trust
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.
-
Software Craftsmanship Manifesto: A Call to Arms
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.
-
Interview with Brian Marick at Agile 2008
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.
-
Brian Marick: What's Missing From the Agile Manifesto
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.
-
Presentation: Future Directions for Agile
In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
-
Craftsmanship - the Fifth Agile Manifesto Value?
Robert "Uncle Bob" Martin re-invigorated the discussion around "professionalism in programming" by proposing that the Agile Manifesto be updated with a fifth value, "Craftsmanship over Execution".
-
Doer vs. Talker: Working Software over Comprehensive Documentation
In Are You a Doer or a Talker? Jeff Atwood of Coding Horror echoes the agile manifesto's 'Valuing working software over comprehensive documentation.' Noting an article by John Taber, Atwood draws parallels between transportation studies and transportation construction projects.
-
Refactoring the Agile Manifesto
The Agile Manifesto is six years old. Many have become disillusioned with Agile as it has spread and (inevitably?) been diluted. Post-agilism has been discussed even before Agile has become truly mainstream. Some have suggested that we have learned much over these years and the Agile Manifesto needs to be updated.
-
Agile Tools Usefulness Debated
The Agile Journal's April issue examined how tools are being used in Agile projects. There are articles that are pro-tools, anti-tools, and a debate between Ron Jeffries and Ryan Martens.