Currently, the iPhone is the hottest platform for mobile development, with everyone wanting to develop on it. Test Driven Development is a proven technique for developing high-quality software, but isn’t encouraged by the iPhone development platform. Open Source developers have stepped in, creating Unit Test Libraries for the iPhone. We’ll show you how to get started, run your first tests, put tests in your build, and touch on advanced techniques like mock objects and dependency injection. Perfect for the Agile Developer looking to get started on iPhone.

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.

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.

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.

Project Managers comprise the single largest category of agile practitioners that are actively engaged in the industry (18%). However, there is no clear consensus on the role of project manager within the Agile community. Viewpoints range from: • The PM is complete waste. • The PM is a necessary part-time helper. • The PM is a crucial communicator and facilitator.

So who’s right? This interactive session will seek to address these questions about who is good, who is bad, why they are, and who says so.

This hands-on advanced workshop teaches incremental Test-Driven Development, showing how to grow code one feature at a time. It will show: how to use tests at multiple levels to focus on requirements, how to use unit tests to drive the discovery of roles and responsibilities in your design; and how to write resilient tests that express your intent and don’t break for irrelevant changes.

The workshop is for programmers who want to improve their TDD practice. It has been presented at several conferences, one review from XpDay London was “Incredibly useful; the best technical I’ve heard”.

You’ve started your new project and “surprise” (not really) you’re dealing with legacy code. This unique workshop will focus on a few specific techniques that help make up the majority of what to do in improving legacy code design. Our forefathers gave us “Extract Method” and “Rename”. Cleaning up code is fun and challenging at times!

The instructors wish, when they were first learning test-driving, refactoring, and OO, that they had had a side-by-side comparison between code Heaven and code Hell. Such an object lesson would have made the value and benefits of agile programming practices so much more plain, so much sooner. Alas for us, but hurray for you! In this workshop you will be able to compare and work with two very different implementations of the same problem domain: one of them fabulously ugly, and the other of them — well — a lot better. This is a close-repeat of a successful session we gave at Agile 08.

Continuous Integration is a key practice in the agile toolkit. The practice is pretty simple - when checkins occur, some process is run against the codebase. This usually includes compilation and unit tests, but could include all sorts of things.

The panel of CI experts host discussion of the audience’s problems, questions, concerns and ideas about how to make best use of CI.

We aim to draw together the experience of the panel with the enthusiasm and fresh eyes of the participants to share our collective CI knowledge with those having issues with their CI implementations.