Behavior-Driven Development, or BDD, is an excellent development strategy that can help bridge the traditional gap between requirements and implementation. This talk will go discuss the basic principles of Behavior Driven Development, and look at how it builds on and differs from “traditional” Test-Driven Development. This session will demo two BDD tools: JDave, an open source framework that incorporates BDD concepts into JUnit, and easyb, a DSL-based behavior driven development framework for Java that uses Groovy to let you pretty much write tests that document themselves.

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.

Spending more time maintaining your tests than your code? Started to write tests only to be discouraged by the complexity involved? Imagine if you could implement robust automated testing on even your most complex projects by simply writing one extra line of code… Now you can! Regardless of which testing framework you use, Approval Tests allow you to painlessly capture tested output in a visible, verifiable, and automated way. Particularly useful in the context of writing tests for legacy code, GUIs, databases and web pages, this open source solution is as pretty as a picture!

The “pomodoro technique” is a simple tracking and feedback process where the unit of work is the “pomodoro”, a time slot of 25 mins. In this tutorial I’ll give you advanced practical advices on how to implement the daily pomodoro practice, common pitfalls, tools you may find useful and how to read and use pomodoro metrics and answer questions like: what did I do the last week, on which tasks I spent most of the time, how frequent is the context switching. Hopefully after this talk you’ll be able to go back to your team and give pomodoros a try with all the practical information needed.

All projects benefit from high quality code but achieving the full benefits of agile approaches demands higher-than-usual software quality. A Continuous Integration build provides an ideal platform for applying automated tools to issues of code quality.

This tutorial looks at automated code quality tools that can be used to enforce or monitor code quality in Java and Ruby, and how they can be used to check quality manifested by:

• style enforcement
• lines per method
• methods per class
• code duplication
• npath and cyclomatic complexity
• test coverage

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.

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.