Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
JProbe Freeware,
an Eclipse plug-in,
diagnoses
memory issues
quickly & easily.
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Agile adoption often proves challenging. Participants at a recent OpenSpace event focused on the dynamics of adoption rather than the structure that results from adoption. The resulting patterns are part of an effort to compile Agile adoption patterns answering: "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?"
What is the role of testers on an Agile team? What is their day to day experience like? What lessons have they learned
In which David Longstreet claims Agile Software Development is a Fairy Tale that just tries to legitimise Cowboy development, and Geoff Slinker invites him to write a Serious Article based on Logical Arguments and Citing Sources.
Agile literature is sprinkled with experiments on the effectiveness of one or more practices. Not all experiments come to the same conclusion. Some experiments come to conclusions that may not coincide with your team’s experience. To understand experimental results, and the level of confidence that you should have in their outcomes, an understanding of a few simple evaluation criteria is helpful.
Carrying on from last year's survey, Scott Ambler published the 2007 Agile Adoption survey this month. InfoQ provides some analysis of his findings and asks readers how they would approach getting a single view of Agile trends from across the community.
Mike Arace writes about his negative early impressions of pair programming. Are the benefits of pair programming worth the costs?
Organizations adopting Agile naturally ask these questions; "Where do I start?", "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?" In this article, Amr Elssamadisy gives a glimpse into an ongoing effort to document Agile practice adoption patterns: Participants at XPday Montreal took a stab at "Simple Design" and "Pair Programming."
Paired programming is an agile practice that is the source of much debate. Martin Fowler has posted an article on common misconceptions with paired programming, suggesting that pair programming is not a requirement of XP, it does not halve productivity, and others.
