BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Adopting Agile Content on InfoQ

  • What Should Your Agile Organization Value?

    Adopting agile is not easy. Many organizations often struggle trying to squeeze the practices of Scrum or XP into the way they work. Mike Cottmeyer offers a reminder to such organizations that placing too much value in the "how" of agile may be a misguided approach.

  • A Comprehensive Collection Of Agile Mailing Lists

    As a participant of the Agile community here on InfoQ, you've already shown you are interested in learning more about agile, and likely have ideas of your own that you're interested in contributing back. This is what you can experience in the various mailing lists that exist related to agile development. But what lists are available? Mark Levison helps to answer that question.

  • Automated Acceptance Tests - Theoretical or Practical

    There have been sporadic reports of successes in writing requirements as acceptance tests and automating them. This practice is only used by a small minority of the community. Are automated acceptance tests written at the beginning of each iteration just a theoretical assertion that have been proven ineffective by the lack of adoption?

  • 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.

  • Interview with Bas Vodde at Agile 2008

    Bas Vodde describes strategies for large teams with legacy software to adopt Scrum successfully. Bas discusses communication problems found in most component teams and why and how teams - especially large ones - should make the change to feature teams and how that change affects organizational structure.

  • 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.

  • 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.

  • Presentation: Beyond Agile - Cultural Patterns

    Willem van den Ende and Marc Evers introduce different cultural patterns you can find in software organizations, based on Gerald M. Weinberg's work, and tell how to recognize them, what behavior to expect, and how you can handle unexpected events and change. They show how different agile processes like Scrum, XP, and Lean fit in, while explaining some common agile failure modes.

  • Recommended Agile Books

    This post is a compilation of recommended Agile books by various Agilists. The recommendations try to cover the entire spectrum of process, people and technology related to Agile. The idea is to make the process of Agile adoption easier and fruitful.

  • 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.

  • Mike Cottmeyer's View Inside The Lean/Kanban Conference

    The first organized conference focusing on Lean & Kanban was held in Miami during the first week of May. Mike Cottmeyer was present and used his popular blog 'Leading Agile' to provide a relatively comprehensive play-by-play look into what occurred there.

  • Learning to be Agile - a snapshot of Agile training providers

    A list of some of the Agile training providers and consolidators from around the world. This article is not a comprehensive list, but a snaphot and starting point for the reader's further investigation.

  • Recommended TDD Tutorials

    Recently, Dave Nicolette consolidated a list of recommended TDD tutorials from a discussion on the Extreme Programming group. Here is a sneak peak at the consolidated list with categorization for quickly getting started with Test Driven Development.

  • A Good Velocity

    Buddha Buck recently asked the Extreme Programming list if there were a velocity range that could be considered 'good' for a team of about seven people doing two-week iterations. He felt that a velocity of eight or below indicated that the team's stories might be too big. The resulting discussion provided some answers to the question, and the questions behind the question.

  • Comparing Kanban To Scrum

    Kanban has been gaining serious interest as a valid approach to implementing agile for your development organization. As such, many people are asking the question "how does Kanban compare to Scrum?". Henrik Kniberg has taken a stab at answering this question

BT