This post originated from an RSS feed registered with Java Buzz
by News Manager.
Original Post: Agile Backlash, Iteration pipelining, Time sensitivity
Feed Title: testdriven.com
Feed URL: http://feeds.feedburner.com/testdrivennewslinks?news=10&links=10
Feed Description: Your test-driven development community
Jonathan Kohl posts on The Agile Backlash: "Now that the Agile movement is making it into the mainstream, and gaining popularity, it is facing a backlash. Aside from the mainstream pro-Agile trend we hear so much about, I see three reactive trends: rejection by non-practitioners, a mandated reversal in corporate methodology focus, and an adaptive reaction that builds on good software development ideas and practices."
Matt Albrecht posts on Unit-testing sensitive code: "One big headache in unit tests involves time-sensitive code. By their very nature, these tests become machine dependent and thus brittle. I'm going to spend a few blog entries reviewing some types of code and possible solutions to testing them. In this entry, I'll go over a particularly interesting one I came across in the CruiseControl code."
Azad Bolour has made good posts on process, including this one on Iteration Pipelining: "The practice of pipelining functional design and development is not uncommon in [Iterative and Incremental Development] projects. But there is concern that pipelining can lead to disruptive cross-iteration interruptions. For example, while the functional designers are busy designing the functions of the next iteration, the developers need bandwidth from them for the clarification of the functions of this iteration. In our experience, interruptions in this direction, while frequent, were welcomed."
Previous Topic
