BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Manifesto Content on InfoQ

  • Agile at 10 – A State of Contradiction

    Mike Beedle states that agile is in a state of contradiction, the agile of 10 years ago is now passé and we run the disk of diluting the real meaning of being agile through lip service implementations without focusing on quality. He echoes the call in the 10 Year Reunion meeting for a concerted focus on quality, and asks what an Agile Manifesto 2.0 should contain.

  • The Art of Creating Whole Teams: how agile has changed the way we work with our customers

    Angela Martin earned her PhD examining how agile methods work in practice and what is different about this way of working. She shares some of the key practices which organisations can implement to increase their likelihood of successful cultural change through creating Whole Teams - truly cross functional collaborative teams working well together to deliver products which meet customer's needs

  • The Accidental Agilist: A Personal Look Back at 10 Years of the Agile Manifesto

    Johanna Rothman reflects on her journey to pragmatic agility. She discusses the way in which agile practices work together to improve project outcomes, and how this is not restricted to software development. She challenges teams to embrace the transparency that agile brings and stop talking about becoming agile and start doing it properly.

  • Reflections on the 10 Years Since the Agile Manifesto

    Mike Cohn reflects on the changes in software development over the last 10 years, as agile has gone from fringe to mainstream and his hopes that we will move from seeing agile as something different or special, to being simply the way we work. In the same way that the Magna Carta influences our lives without being in the forefront of thinking so the Agile Manifesto should fade into the background

  • Agile 10 Years On

    James Coplien looks from the hacker culture of the 1960s, through objects in the 1980s and forward to the future to put the Agile Mainfesto in context of the 20 year cycle of fashion and change. He argues against mindless adherence to a particular set of rules and tools and for carefully thought out application of good practices that support the production of good quality software products.

  • A Personal Reflection on Agile Ten Years On

    Stephen J Mellor was one of the original signatories of the Agile Manifesto. He attended the Snowbird meeting “as a spy” with but found himself agreeing with most of what was being said and became a proponent of Agile techniques and emphasizes the value of modelling in the Agile world. We rarely see the words “agile” and “model” in the same sentence, but they are not at all in conflict.

  • "Flirting" With Your Customers

    All over the world, there are classes that teach people how to flirt. A German university even requires their IT engineers take a flirting class—not to attract a partner, but to learn how to interact more effectively in the workplace. Flirting means connecting with others, and connecting is the key to good communication. That is what the first principal of the Agile Manifesto is all about.

  • Book Excerpt: Agile Software Development, 2nd ed.

    In this updated classic on Agile software development, Alistair Cockburn adds reflections from five more years of practice and research. InfoQ brings you Chapter 1, in which he compares software development with another team-cooperative game - rock climbing - and two common comparison partners, engineering and model building, in order to explore alternate ways of thinking about the work we do.

  • Do Agile Practices Make it an Agile Project?

    Use of Agile methodologies is growing, but this comes with its own challenges: including the possibility of dilution as teams copy practices rather than growing them, implementing them without understanding. Perhaps it's time to talk about how failure to teach the basics puts much at risk: the integrity and engagement of team members, and the trust of their customers.

BT