Tracking change and innovation in the enterprise software development community
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Rule your SOA
with CentraSite
standards-based
registry/repository
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Continuous Integration, a basic XP practice, has now become an accepted development best practice. InfoQ presents Chapter 6: Continuous Testing, with advice and examples for writing good tests to ensure system quality, from the book "Continuous Integration: Improving Software Quality and Reducing Risk," which aims help teams make CI a transparent "non-event".
Many agree that the minimum set of Agile practices includes disciplined version control. In particular, when several development teams work in the same codebase, to ensure there's a clean, releasable version at the end of every iteration, they need a plan. Henrik Kniberg's proven scheme is a useful guide for teams. This detailed paper includes the entire method and even a cheatsheet.
After asserting that one must, as a rule, always version their database work, Scott Allen detailed an approach to making the best of versioning databases. Allen presented a comprehensive, practical approach to creating a baseline, using change scripts to manage schematic revisions, controlling programmatic database objects, and handling branching and merging.
There has been a lot of discussion on various agile forums and blogs about the difference between 'Done' and 'Shippable'. It might sound like both mean the same, however discussions on the lists and various blogs suggest that these are still widely misunderstood, mis-used terms. Here's a roundup of recommendations about how to handle "Done."
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.
At Qcon London, Kevin Jones spoke from his experiences about Building Better Apps using MSF for Agile with Visual Studio Team System (VSTS). Using examples from Agile teams, he walked through the layers and components of Microsoft's tools, emphasising their flexibility. For Agile teams considering / already committed to Microsoft, this video provides an experienced viewpoint & may be worth a look.
A recent article published in IBM developerWorks talks about automating Continuous Integration and Code Inspection tasks in a build process using open source tools. It explains how to install and configure Hudson server with Subversion, Ant, and software inspection tools like FindBugs and PMD to create a build process with continuous feedback on test results and defects.
Mingle R1.1 is out, just 3 months after after the first release, packed with new functionality driven by user feedback from the launch and beta period. In December R1.2 will be released.
The Database Publishing Wizard is a popular add-in for Visual Studio, which supports deploying a local database to a remote host. The Visual Web Developer team announces that the wizard will be integrated in Visual Studio 2008.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
