BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Introducing Agile Content on InfoQ

  • No Easy Road to Agile Cultural Change

    A number of commentators have written about the challenges involved in migrating an organisation to an Agile culture. Ken Schwaber has estimated that 75% of Scrum implementations will fail to deliver the anticipated benefits. This article looks at some of the reasons why and what can be done to improve success rates.

  • High-performance Teams – Avoiding Teamicide

    High-performance teams constitute a mere 2% of the workforce, but Agile processes appear to stimulate the formation of these types of teams. This article discusses Steve Denning's perspective on how such teams can be nurtured in the workplace; it also looks at a recent talk by Ominlab Media's Stefan Gillard on how to select and employ for the formation of high-performance teams.

  • An Agile Team's Weekly Schedule

    It's 9:35 AM; do you know where your agile team is? If they are using William Pietri's example schedule, they are in the middle of their stand-up meeting, unless it's Monday, in which case they are doing iteration planning & kickoff. William's sample schedule is understandable and practical, and sparked discussion that explored subtitles in scheduling for agile teams.

  • Cost Justifying an Agile Migration

    Show me the money - cost justification of Agile migration is a thorny issue. Agile approaches are more successful, deliver value sooner and produce better quality products, but how do we prove it? This article discusses measurements and presents results that help to justify adopting Agile methods.

  • 3 Pillars Of Executive Support For Agile Adoption

    An executives job is not over once they've justified agile to their teams and paid for training. To make a transition successful, its required this executive provide sustained support. Esther Derby takes a moment to describe what she believes to be the 3 most important aspects of this ongoing support.

  • Interview: Linda Rising on "Fearless Change" Patterns

    In this interview by Floyd Marinescu, co-founder of InfoQ, Linda Rising talks about the book "Fearless Change: Patterns for Introducing New Ideas" and offers examples of how the patterns presented in the book can ease Agile adoption.

  • InfoQ Book Review: Agile Adoption Patterns

    Ryan Cooper picked up Agile Adoption Patterns: A Roadmap to Organizational Success by InfoQ's own Amr Elssamadisy and gives this book a positive: This book belongs on the bookshelf on anyone who is interested in helping a traditional software organization make an effective transition to a more agile way of working.

  • CM Crossroads on SCM for Small Teams

    Agile brings to organizations, among other things, small teams coupled with constant change. Navigating this effectively requires understanding what this means to Software Configuration Management practices. The July edition of CM Journal's "cm//crossroads" is dedicated to helping people meet this challenge successfully.

  • Results of Agile Adoption Survey 2008

    In February 2008, Dr. Dobb's conducted a survey on Agile adoption and the success rate of Agile software development. The survey revealed some interesting results on various parameters, including: adoption, scalability, iteration length, and team location.

  • Interview: James Shore on “The Art of Agile Development”

    In this interview taken by InfoQ's Deborah Hartmann during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book "The Art of Agile Development".

  • Don't Worry About Scaling Scrum

    Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.

  • Stories of Scrum Adoption in China

    This recent inquiry, by InfoQ China editor Jacky Li, looked at five very different cases of Scrum adoption in China, which got different results. He asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.

  • 50 Developers Answer: What Do You Want Your CIO to Know About Agile?

    Trying to explain the benefits of Agile Software Development to your CIO? Does your boss want some outside validation? Esther Schindler asked more than 50 developers and Agile practitioners one question: "If you could get the boss to understand one thing, just one thing, related to agile development...what would it be? Why that?".

  • Mythical Agile Shortcuts

    Going agile seems a pretty trivial task. We pair up, write unit tests, integrate regularly and support our teams with an easy to manage framework such as Scrum. In reality, however, this is not the case. All too often the benefits are not achieved and team does not function as expected. Ross Petit's recent article sheds some light on why things go wrong when the rubber hits the road.

  • Charming the Army: the Power of Delivery

    Here is a story about Agile's use in a governmental organisation: at the 2006 APLN Leadership Summit Mark Salamango and John Cunningham looked at the problems and opportunities of introducing Agile in Army environments. True Agile practices cannot be 'commanded' or 'directed’ but frequent delivery offers Agile leaders a "soft" kind of power that is, in fact, very effective.

BT