Agile 2009 - Demonstration

Deep Democracy: A Radical Approach to Hearing from Every Voice

mspayd — Wed, 04 Mar 2009 04:36:32 +0000

This session is an explanation and demonstration of Deep Democracy, primarily aimed at coaches interested in learning new techniques. Deep Democracy—originated by Arnold Mindell—maintains that a well functioning group is dependent on all the voices, positions and views in the group being heard and valued. We will start with the definition, origins and applications of Deep Democracy, then conduct a Large Group Process in which all can directly experience the power of this approach. In our debrief, we will harvest the wisdom of the group, and explore practical uses in Agile team situations.

The Ogre and The Wimp: Clever Influencing Tricks - Help the Most Reluctant Teams

anda — Tue, 03 Mar 2009 06:07:46 +0000

What happens when the CIO decides the dev team needs to adopt agile practices and the dev team nods their heads but don’t plan on doing zilch? It is time to leverage those fancy shmancy influencing skills we agilists are so famous for. We’ll cover new fun tactics that have not yet been explored in some of the prevalent literature. All fresh information from the field.

Color Modeling Improv

dja — Sat, 28 Feb 2009 22:34:37 +0000

Peter Coad’s Color Modeling method is a simple, effective technique for building robust, elegant object models. One of the best ways to learn the Color Modeling approach is through an interactive demonstration. In this session, Daniel Vacanti and David Anderson will solicit examples from the audience and—with no preparation and using the Color Modeling approach—build a real, working model for each selected problem domain in the short time given. Both David and Daniel have used this demonstration technique with great success at previous conferences, tutorials, and commercial engagements.

Agile Lightweight Project Management with Google Docs

blomseth — Mon, 09 Feb 2009 14:27:39 +0000

Using Google Docs you can create your own lightweight project management tools and through simple and powerful visual management provide the people involved with shared information that will give transparency into progress and problems

Compared to most commercial project management tools using Google Docs is very flexible. That way the tools can be adapted to how the processes of the project continuously improve. And not the other way around.

The demonstration is based on more than 2 years of experience using Google Docs for Agile processes in a distributed development context.

Continuous Integration of the World

jedi4ever — Fri, 06 Feb 2009 15:36:54 +0000

Ok, maybe we exaggerated a bit. CI deployments focus on the testing and deployment of the application. The ‘world’ (OS, Application & DB server) within a CI doesn’t change that much. But what if you could define your applications environment from a kind of ‘source’ and build and unit test it? f.i. Test security patches by using unit tests of your application?

Agile testers toolkit

ecp — Fri, 06 Feb 2009 04:19:09 +0000

This session will introduce and demonstrate some of the free or near free tools available for a functional tester (or developer) to assist with test planning, execution, analysis and test support. We’ll look at mind mapping tools, portable applications, firefox extensions, and various other tools including an amazing test data generator. These tools will help organize ideas, look “under the hood”, verify compliance to various standards, record test results and assist in breaking software from a functional and security point of view. We”ll also look at some general tools as well.

Ineffective Pairing, How To

brett.schuchert — Wed, 04 Feb 2009 15:15:09 +0000

Most sessions show us how to do various agile practices right. What is sorely lacking is the opportunity to learn how to do the practices wrong. How can we be expected to bring agile into an organization successfully without mastery of that key skill?

Pairing isn’t controversial, done effectively it: * reduces defects (by up to 86%, according to the 2000 University of Utah study), * improves productivity (up to three-fold, according to the 1975 US Army study)

However, learning by doing wrong is actually an effective learning technique, and that’s what you’ll see here.

Test Driven Development in Java: Live and Uncensored

bjrady — Fri, 30 Jan 2009 04:00:26 +0000

One of the barriers to wider adoption of TDD is that it is best taught from within a team, and the technical challenges of writing tests frequently thwart those looking to teach themselves. This session will be a live demonstration of Test Driven Development in Java, using Eclipse and JUnit, aimed at those new to TDD and looking to learn. Audience members will be encouraged to follow along on their own laptops as we walk through common scenarios that frequently discourage new TDDers, and demonstrate some techniques for overcoming them in a live coding session.

Continuous Testing Evolved

bjrady — Fri, 30 Jan 2009 02:40:55 +0000

Continuous Testing (CT) is a developer practice that shortens the feedback loop established by Test Driven Development. It gives you near instant feedback about the correctness of your code, and helps you find bugs as quickly as syntax errors. This session will cover how CT has evolved in the last year, it’s current capabilities, and limitations. The presenters will also show several demos of the practice using freely available continuous testing tools, and examine how these tools can be integrated with existing infrastructure to bring the benefits of CT to a wider audience.

Acceptance Test Driven Development (ATDD) in Practice

peke — Wed, 28 Jan 2009 20:30:09 +0000

Agile teams practicing Acceptance Test Driven Development (ATDD) define acceptance tests collaboratively while discussing each story. This practice helps uncover assumptions and confirm that everyone has a shared understanding of “Done”. During implementation, the technical team automates the natural-language Acceptance Tests by writing code to wire them to the emerging software. In this way, ATDD tests become executable requirements. This session is a demo of the full ATDD workflow from initial discussions to distilling tests into an automatable format to implementing code to the final demo.