Amr Elssamadisy ponders over pipelined Continuous Integration: "One of the well-known practices of Agile development is Continuous Integration, which entails team members integrating their code regularly into the baseline and running all unit and system tests. In most teams a CI server is used to do this quickly and automatically when code is checked into the baseline. This usually works well in the beginning of a project, but sometimes, when the team and/or code-base get large, the CI server starts to slow down. The cycle between builds grows and the feedback degrades — a build may take an hour or more to respond with a pass/fail, and by that time several people may have checked in their code into an already broken build." (Is Pipelined Continous Integration a Good Idea?)
Nikita Ivanov also wonders about the Dark side of diligent unit testing.Peter Maas blogs on how to do TDD with Grails.
Scott announced that Version 4.1 of TypeMock.NET is now available. (Announcement)
Did you know soapUI has plugins?
Matthew Bass wishes flexmock and unit_record would play nice.
Ben Fulton posts some notes from a "really good session by Gerard Meszaros" on Test Patterns at SD Best Practices 2007 (xUnit Test Patterns and Smells)
Mark Levison knows that working at a Distance is hard, and lists the tools he uses to shorten distances in outsourced Agile teams.
Patterns of Agile Practice Adoption is available as a free download from InfoQ (after registration).
Stelligent will be celebrating Testoween on tuesday, October 30th, from 5:50PM to 7PM in Reston, Virginia. "I often run into teams who attempted to jump skull first into TDD and eventually threw their bones up in frustration when either schedules became scary or they ran into scenarios too frightening to test. Are there areas where test-driven development gives you the spooks? We’re terribly excited to announce that on Tuesday, October 30th, we will be hosting a roundtable discussion on TDD at our lair in Reston, Virginia. Get into the spirit of Halloween by treating us with your horror stories on the trickiest problems when implementing TDD. We’ll be talking about what spells work and what spirits don’t, while mingling over a cauldron of fine wine (courtesy of Savoy-Lee), cheese, and other potions. We’ll also be raffling off a screamingly appropriate iPod shuffle. Registration required, seats limited." (Share your TDD horror stories)
What is Agile Development? An Interview with Venkat Subramaniam.
"An interesting part of the discussion in the After Agile, What Next? session involved the question of omitting certain agile practices when they are impractical or unsupported in a given organization or under a given set of circumstances. The consensus was that people who fully understand how and why agile practices add value and how they interoperate to bolster each other’s strengths and cancel out each other’s weaknesses, and who have actually worked on projects that were ‘fully agile,’ are equipped to find alternatives to compensate for the removal of one or more particular agile practices. Unfortunately, many people who have never fully applied agile practices mistakenly believe they understand how to pick and choose individual practices without losing any of the effectiveness of the agile approach. This sort of thing is often behind the comments we sometimes hear about agile experiments that ‘failed.’" (Dave Nicolette on Agile software development)
Tad Anderson voices his concerns about the Agile buzzword: "You either know how to do the tasks in the process right, or you don’t. Just doing them is not good enough. So this agile attitude of ‘Since process activities don’t work, let’s get rid of them’ does not do anything for the team that didn’t know how to accomplish the tasks right in the first place. It just displaces their lack of skills to different task. I have seen tons overly bloated software out of agile teams because most teams use agile as an excuse to go right to code." (Agile Development != Low Ceremony && The Movement Needs to Die)
And there’s always more on Religion driven industry…
Luc Legardeur and Xebia propose a tentative model for Agile Maturity, based on Governance, Technical excellence, Specifications, Simplicity, Collaboration and Leanness (Simple Agility Maturity model, in French).
In August, VersionOne published their second annual survey of Agile Development: "VersionOne, in association with the Agile Project Leadership Network, are pleased to present the results from the second annual "State of Agile Development" survey. The survey has become one of the largest in the Agile Development market; receiving almost seventeen hundred (1,700) responses with a truly global reach of respondents from seventy-one (71) countries." (2nd Annual State of Agile Development Survey)