BT

InfoQ Homepage Agile Manifesto Content on InfoQ

  • Ron Jeffries Says Developers Should Abandon "Agile"

    Ron Jeffries, author, speaker, one of the creators of Extreme Programming (XP) and a signatory of the Agile Manifesto back in 2001, shared a post on his blog in which he advocates that developers should abandon “Agile”, meaning they should stay away from the “Faux Agile” or “Dark Agile” forms and get closer to the values and principles of the Manifesto.

  • Co-Author of Agile Manifesto and Creator of Enterprise Scrum Mike Beedle Passed Away

    Mike Beedle, co-author of the Manifesto for Agile Software Development and the creator of Enterprise Scrum, has passed away at the age of 55. He leaves his wife and six children behind.

  • Oath for Programmers

    Our society demands a commitment to professional behavior; we need an oath for programmers as lives and fortunes depend upon the proper construction and execution of software, argues Robert Martin. According to him, this will have to be enforced by membership in an professional association.

  • Hiscox CTO Emphasises DevOps Is about Survival

    Hiscox's CTO talks about cloud strategy, DevOps and getting ops on board these changes.

  • Learning to Become Agile

    The agile paradigm adapts processes to human nature, in contrast to the classical management approach which obliges team members to adjust to a particular development process. Bateson's learning model can help us to go from doing agile - following an agile method - to being agile - having your own agile identity and vision.

  • Courage to Become Agile

    Being brave is about doing what is necessary, even when you are afraid. The single most important thing in agile is to inspect and dare to change things which aren't working. You can start with small experiments to find solutions, and if it turns they do not work, then you can stop them.

  • Refuting the Idea of Rewriting the Agile Manifesto

    Alistair Cockburn recently posted his viewpoint on the history of the Agile Manifesto, from the perspective of one of the original authors and signatories. He encourages readers to understand the perspective taken at the time by the authors, and also to explore the ongoing work of many of the original signatories. The original authors explicitly refuted the idea of rewriting the manifesto.

  • How Agile and Architecture Parted and Finally Became Friends

    People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.

  • Survey on the Need for an Agile Manifesto 2.0

    The survey on Agile Manifesto 2.0 investigates whether the Manifesto for Agile Software Development is still relevant and effective in today's environment. Kamlesh Ravlani, an Agile / Lean Coach and Scrum Trainer, created this survey to gain insight into the need for change in the Agile Manifesto. The survey is open to anyone who has experience with and an opinion about the Agile Manifesto.

  • Agile 2016 Keynote: Modern Agile

    At the recent Agile 2016 conference in Atlanta, Joshua Kerievsky, CEO of Industrial Logic and author of "Refactoring to Patterns" gave a thought-provoking keynote around the idea of Modern Agile.

  • Overcoming Paradigms to Become Truly Agile

    Truly agile is what you are, and to become agile you need to overcome paradigms, argues Arie van Bennekum, co-author of the agile manifesto. It takes "being agile" and not "doing agile" to achieve success. Agile is an interaction concept based on the values and principles of the agile manifesto. Technology facilitates agile working, but tools don’t make you agile.

  • The Importance of Technical Practices in Agile

    Sometimes organizations that are adopting agile complain that they didn't get the benefits that they expected to get out of it. One of the possible reasons could be that insufficient attention has been given to performing the technical practices that support the agile values and principles.

  • Q&A with Pragmatic Dave: Agility over Agile

    Dave Thomas and Martin Fowler participated in a panel for the GOTO Conference series, focused on ‘A retake on the Agile Manifesto’, inspired from Dave’s blog, ‘Agile Is Dead (Long Live Agility)’. In this Q&A, Dave (also known as Pragmatic Dave) explains his thoughts around the panel, his blog and why he believes it’s time to focus less on agile and more on the practical application of agility.

  • Having Actions Done from Retrospectives

    Agile retrospectives help teams to find and do actions to improve continuously. There are different ways to do follow up on the actions and to evaluate if actions are leading to better team performance and more value delivered to customers.

  • Documentation in Agile: How Much and When to Write It?

    The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.