|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 | Working Agile into a Non-Agile EnvironmentSpeaker(s): Tina Mangham
How can you be agile if nobody else at work is? This presentation is geared towards 1 man teams and is an explanation of how 1 person can introduce Agile into a non-agile environment by following some of the agile practices such as project boards, iterations, etc. It shows how some of the agile practices can be geared to 1 man teams (regardless if you are a BA, tester, Project Manager, developer).
|  Oct 9th |
|
| TDD in the RAW, building an algorithm from scratch using RubySpeaker(s): Brett Schuchert
You, me, vi and TDD. What you can expect from this session is a screen, two terminal windows, one with vi open and the other where I run the tests, and check in my work.
Starting with nothing, we'll quickly review an algorithm, develop a test approach and then work through several complete TDD cycles applying both Martin's three laws of TDD as well as code refactoring and even a touch of continuous integration.
If you are interested and cannot attend, or even if you can attend but would like to come prepared with lots of questions, the presentation will closely follow:
|  Oct 9th |
|
| Comparing TDD and BDD in Ruby using Test::Unit and RSpecSpeaker(s): Brett Schuchert
This is a three-part demonstration. In parts 1 and 2 we start with nothing and develop a solution first using TDD with Test::Unit in Ruby and then second using BDD and RSpec. In both cases, we'll use the same problem so there's a good chance you'll have a direct comparison between the two.
In part 3, armed with these two comparisons, we'll develop a list of differences in an attempt to get a better idea of just what is what.
|  Oct 9th |
|
 | Manager's Introduction to Test-Driven DevelopmentSpeaker(s): Dave Nicollette
Test-driven development (TDD) is among of most controversial and least understood leading-edge software development techniques. What exactly is TDD and what effects does it have on the things project managers care about: Project timeline, team productivity, product quality; longevity and supportability of the product in production; total cost of ownership? We demonstrate the workflow of TDD using a tool familiar to most managers: Microsot Excel. The demonstration is followed by a presentation of the financial impact of TDD on a project and the product the team builds. Finally, there is an open question/answer period when managers can ask anything related to managing agile projects and teams.
History: Presented internally at a company in Cleveland in May, 2006; publicly at Agile 2007 (Washington DC), XP Days Germany 2007 (Karlsruhe), and Agile 2008 (Toronto). Scheduled for Agile Business 2008 in September (London).
| Oct 10th |
|
| An Introduction to Behavior Driven DesignSpeaker(s): Raymond Lewallen
I am a firm believer that TDD is an outdated standalone practice. After years and years of practicing and learning TDD, there is a revolution going on towards BDD, Behavior Driven Design. In this session, we will look at how BDD improves on the concepts of TDD, helps write better tests and makes you think more thoroughly through the problem you are attempting to solve. We will be replacing what you know about fixtures and tests with concepts such as contexts and specifications, concerns and observations and how to organize your specifications and use specunit to introduce better language into your tests and build specification reports. We do all of this in C# and Visual Studio 2008.
| Oct 10th |
|
| Agile MetricsSpeaker(s): Dave Nicollette
What information should be measured and tracked for agile software development projects? What does it mean to measure "outcomes" rather than "activity?" Which metrics are useful and which are just useless busywork, and how does it differ for a mature agile team vs. a novice agile team? Which stakeholders are interested in which sorts of information, and what is different for an agile project in an agile organization vs. an agile project in a traditional organization? How can metrics be used for project planning and projecting completion dates, when agile projects do not do detailed design or estimation up front? Which metrics are informational and which are motivational? What happens when metrics are mis-used?
History: Presented at the OKC APLN in (I think) February 2008; scheduled for Agile Development Practices 2008 in November (Orlando).
| Oct 10th |
|
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
|