First eWorkshop on Agile Methods
April 8, 2002
Pre-meeting feedback

Click here for the Summary.

Click here for 2nd eWorkshop on Agile Methods

Read the summaries of responses received for:

• Statement 1 : "Agile development works better for smaller teams and is more difficult for larger teams, e.g. refactoring can be done only for small systems and great developers"
• Statement 2 : "Agile’s emphasis is on designing for current needs, not for future ones. Therefore agile methods work best when the future is unknown, and are less than optimal for projects in which future requirements are known."
• Statement 3 : "Agile methods fit applications that can be built quickly and don't require extensive quality assurance. Agile methods work less well for critical, reliable, and safe systems."

These statements are excerpted from an article published by Barry Boehm in IEEE Computer, " Get Ready for Agile Methods, with Care ."

The summaries include responses from:

• Scott Ambler, Ronin International, Inc. and Thought Leader of the Agile Modeling methodology
  • Position statement
• Ken Auer, RoleModel Software, Inc
  • Position statement
  • Responses to the discussion items
• Kent Beck, founder and director of the Three Rivers Institute
  • Position statement
• Hakan Erdogmus & Joel Martin, National Research Council of Canada
• Peter Hantos, Xerox
  • Position statement
• Tim Mackinnon, Connextra Ltd.
  • Position statement
• Frank Maurer, University of Calgary
  • Position statement
• Randy Miller, TogetherSoft
  • Position statement
• Gary Pollice, Rational Software
• Ken Schwaber, Advanced Development Methods, Inc. and one of the developers of Scrum
  • Position statement
• Don Wells, ExtremeProgramming.org and co-chair of XP/Agile Universe conference
  • Position statement
• William A. Wood & Bil Kleb, NASA Langley Research Center
  • Position statement