Intent

Provide the participants with a hands-on-experience of real world refactoring by taking an open source project and refactoring it.

Summary

Refactoring is a very well established practice not just in the Agile Community, but outside as well.

This session is an attempt to help the development community understand refactoring a little better. It will provide a hands-on opportunity for developers to explore these concepts in action. This session will try to amplify the participant’s learning process by pairing them with other practitioners and peers.

It’s easy to speak of test-driven development as if it were a single method, but there are several ways to approach it. In our experience, different approaches lead to quite different solutions.

In this workshop, we’re not trying to decide which approach is best. Rather, we’ll use concrete examples to explore

• What goes into the moment of decision when a test is written?
• How do you think about the problem you’re trying to solve?
• What strategies or techniques help you write the first few tests?

This workshop is targeted at TDD/BDD Practitioners.

Agile software development means collaboration, and increasingly this collaboration will cross boundaries of organizational and national culture. The session introduces models of culture and explores the impact of cultural differences on software development processes and methods, especially those involving the practices common in agile development. The session will be organized around two collaborative games that illustrate how cultural differences interact in the software development workplace. Our aim is better understanding of the issues and how to manage them.

How do you become agile with all the constraints surrounding you and your team? This tutorial introduces a new way to approach agile adoption efforts. We will go through important and key concepts related to agile adoption such as adopting values not practices, the difference between education and training, readiness assessments, and the process of organizational change. One of the tangible outcomes from this tutorial is a roadmap to agility that consists of five different levels, or steps, along with the different practices that can help an organization achieve each level of

Bad build practices take a hidden toll on teams. It is not uncommon for a new developer to take days or even weeks to establish a functioning workspace. Good build engineers can make all the difference. By treating the build framework with the same respect as other source code they can help prevent these problems. In this clinic we will show how to refactor your build approach to end up with sustainable practices that get new people up and running quickly and set the stage for long term productivity. While the workshops are in Ant, the concepts are portable.

This tutorial is a detailed look at several Agile practices and the HOWTO of Adopting each practice successfully. We will cover the business value delivered and the context where they are most effective. For each practice you will learn what steps can be done to effectively get from “I want to do this practice” to “I’m doing it and getting obvious value” and, just as importantly, what happen when things go wrong and how you can diagnose these difficulties.

A variety of practices will be covered including: Stand Up Meetings, Iterations, Demos, Automate Developer Tests, and Refactoring.

How’s your Behaviour Driven Development? Healthy, sick or new-born? Drop in to the clinic at any point during the session and find out. Bring your code, tests, examples and scenarios in to the experts for a thorough check-up, diagnosis and prescription. We can give your code base a full going-over, from business value through unit tests, mocking, and code. Got problems? Not sure who to talk to? Just making sure everything’s all right? Let us help!

We are able to work with Java, C# and Ruby, and will consider other species if you can describe them to us.

Field-tests about how personal responsibility works in the mind (i.e., how we avoid it and how we take it) now make it possible for coaches to understand and teach the mental processes, language, and keys to personal responsibility. Cool huh?

Doing so inspires your charges to demonstrate far greater ownership behavior as individuals, teams, and even as entire enterprises. You add more value as your charges take ownership and learn, correct, and improve more easily, directly, and quickly.

Come acquire the basic tools and practices for coaching success with personal responsibility.

Coaching helps communities produce real value and grow sustainable agility. Successful coaches know the importance and value of treating each community as unique, helping the individuals and the larger community find a “groove” (style) that truly helps them deliver. If you are coaching or getting ready to coach, and you want to learn a pile of pragmatic coaching tools, based on years of coaching agile projects, this session will pass your tests.

Cucumber is a new acceptance testing (AT) tool that works with RSpec. Already popular in the Ruby community, this tutorial shows you how to use Cucumber to test drive Java applications, when you combine Cucumber and RSpec with JRuby.

We’ll also discuss Cucumber vs. FitNesse and using RSpec vs. JUnit. You’ll learn tips for writing good acceptance tests. Half of the time will be devoted to a hands-on exercises, where you will test drive a simple Java application using Cucumber.

Bring your laptop (or a pair partner with one), with the latest Cucumber, RSpec, and JRuby installed.