In this session, we invite CI tool vendors to give a short demonstration of the best features of their tool. Each vendor will be given 10min to show off the best features of their software, with a further 5min of questions.

This will allow CI users to quickly get a good grasp on the plethora of CI tools on the market, to help them find out about useful features of various tools that may help their CI implementation, and to learn about the practices that each tool encourages.

It also helps CI tool vendors gauge the market, and improve the standards and features of all CI products.

There are plenty of good tools out there - the trick is to get them all to play together well. In this session, we will go through the full process of setting up an automated software development infrastructure, from code changes and version control right through to automated deployment to staging and production. We will go through the key steps involved in automating a typical Java project using Maven, Hudson and a large cast of other supporting tools. We will see not only how to automate the build itself, but also how to improve code quality, manage releases, and improve team communication.

Automating your build process with Continuous Integration is certainly a great idea, but why stop there? Why not go the whole nine yards and automate the deployment process as well? Staging and production deployments are typically more complicated and more involved than a simple development deployment, but doing them by hand can be time-consuming, tricky and error-prone. Indeed, turning your staging and production deployments into a one-click affair has a lot going for it.

Continuous Integration means different things to different people. This workshop will demonstrate a set of best practices that allow a software delivery team to derive the most value out of their software development dollars, by adhering to the Agile Manifesto principle that states “Working software is the primary measure of progress.” That is, we will see how software can be delivered that allows rapid change, monitors that the changes do not adversely affect quality, and delivers potentially shippable code from easy to implement open source tools available to the community at large.

In this session, you will learn one thing: how to enable emergent design in a database. The reality is that database development is different from application code development. They are similar, but databases bring about some forces that we haven’t given much thought.

This session challenges traditional, foundational database development techniques and proposes a new framework into which Agile processes, as well as techniques such as TDD or refactoring, can better fit.

In today’s Agile development environment, UI testing is still very much done the old way. We still see long scripts that are easily broken and impossible to maintain. By applying modern software development techniques like test first development, refactoring, and pair programming we can seek to make better tests that are less fragile and more likely to discover defects in code. In this session we will demonstrate the techniques listed above and discuss how they can be applied to UI testing. The demonstration will use a combination of fitnesse and SWAT (an open source web UI testing tool).

This demonstration will show how the Scrum process and many XP/Agile practices can be implemented using Visual Studio Team System, Team Foundation Server, and the Conchango Scrum Process Template in a .NET development environment. The demonstration will follow a User Story from being added to the Product Backlog, through development during a Sprint, to deployment to production, and back again via a reported defect; covering the entire lifecycle cradle to grave.