A Preview of Mingle 2.0
On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0.
On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0.
InfoQ got together with Zach Nies, Product Development Manager for Rally software for a product walk through of Rally's latest offering of their Agile Lifecycle Management product, and to talk about where Rally's product in this space is going in the future.
A new site Agile Commons has recently been born, as a result of collaborative work between Rally employees and their customers. It has been launched as an ideas exchange platform funded by Rally & Hivemind, with the aim of becoming the leading resource for Agile minded people, by inviting different types of organisations, Linked In groups to discuss and exchange agile ideas in a single place.
Jennitta Andrea & Ward Cunningham recently hosted a WebCast on 'Envisioning the Next Generation of Functional Test Tools'. Also, towards the end of last year Thoughtworks' announced its intention to release a next generation functional testing tool. InfoQ investigates the growing momentum for change in the area of functional testing and how the thought leaders in this area see it developing.
The idea of continuous production has been around for some time, with Cal Henderson revealing in 2005 that Flickr releases code to production about every 30 minutes. InfoQ investigates continuous production and explores the effects it has on the product lifecycle, and in turn the host organisation.
Analysis of a recent study by the National Research Council of Canada's Institute of Technology into Test Driven Development turned up some interesting observations regarding the value that this approach adds, including whether, in fact, it adds any more value to the quality process than testing after development.
Going agile seems a pretty trivial task. We pair up, write unit tests, integrate regularly and support our teams with an easy to manage framework such as Scrum. In reality, however, this is not the case. All too often the benefits are not achieved and team does not function as expected. Ross Petit's recent article sheds some light on why things go wrong when the rubber hits the road.
Evan Robinson recently posted an article on why the practice of 'crunch time' doesn't work. Despite a century of studies showing that long-term output is maximized near a five-day, 40-hour work week, projects still hit the crunch usually to the detriment of the team. InfoQ looks at why crunch time is still so prevalent in the software industry and, if we know it's bad, why do we still do it?.