program selection system

Automated unit testing is the agile software development equivalent of “in-process inspection” in Lean Production systems. xUnit is the generic name given to the family of tools/frameworks used by developers when developing automated unit tests. The community has now had enough experience with using XUnit to start cataloging “best practices” and “not so best practices” as patterns and smells. This tutorial introduces a number of these “test smells”, describes their root causes, and suggests possible solutions expressed in the form of patterns.

Program Guide Description:

At Salesforce.com a waterfall-based process bogged down our first attempt at generating a traditional pattern library. In keeping with our development team’s agile transformation we revisited the process and invented Postcard Patterns – a highly visual, easy to maintain, and easy to produce communication tool.

Attendees will learn how to:
Identify Their Audience:
Who needs the patterns?
De-construct Their Application:
What are the unique building blocks?

Printed Program Guide Blurb
Books on Test-Driven Development abound for C# and Java, but there are few directed towards C++ programmers. Yet much software is written is C++, and C++ is an extremely powerful language, one that I’ve found to be quite well-suited for doing TDD. I will present a series of practical and efficient testing patterns specifically for C++. Most of the techniques involve templates; one of them involves lexical closure. Many of these techniques are also well-suited for dealing with legacy code.

Scrum & XP may sound deceptively simple. But once you get down to the everyday practical stuff there are many subtle traps hiding about. Common mistakes that are easy to make and hard to detect, mistakes that cancel out many of the benefits that Agile methods were supposed to give. In this talk I’ll go through some of these traps, how to detect them, what the effect is, and what can be done about them.

__The Agile movement has largely ignored the experiences of CTOs and senior leaders in an Agile enterprise. In this session, we move toward a pattern language of CTO-level Agile practices and underlying principles, with supporting or constraining forces. Presenters will explain survey data and a CTO panel will contribute their stories.

Modelling agile methods in the classroom also allows students to see the depth and power of agile methods as a general approach to working, and simultaneously confirms that the instructor actually walks the talk. In this workshop, attendees will explore using agile methods to deliver agile training. The first half will go through the methods used by Mishkin Berteig, an experienced agile trainer. These methods will be presented as a set of patterns. In the second half of the workshop participants will collaboratively discover and refine more patterns.

In 2005 Tim Joyce and I published collections of patterns and proto-patterns capturing the common features of every then-current description of successful distributed Agile development we could find, including our own.

In the years since then, many more teams have found their way to a successful accommodation between their desire to be Agile and their business’s need or desire not to co-locate. So, it’s time to update the patterns.

A workshop where experience is reported.