Agile '05 conference, part 1
The Agile '05 conference was July 24-29, 2005, in Denver, Colorado, USA. There were about ten or twelve tracks at all times, so this report is necessarily only a limited bit. Usually I teach, but this time I was an organizer so I got to be more like an attendee in some ways.
Brian Marick and Bob Martin Keynote: Where were we, where are we, where are we going?
Brian Marick: We have different disciplines. We become multi-specialists. "A team of multi-specialists can knock the socks off a team of specialists." But there's no career path for multi-specialists - what conference would you go to?
Brian invited Jim Highsmith up to announce the formation of the Agile Project Leadership Network (APLN). Its focus is on applying agile principles to all projects, not just software. Relative to the Agile Alliance, this organization has consistent principles and intends to collaborate; it just has a different focus.
Bob Martin: "Value the flow of value."
The software industry: was either no process or waterfall. Now we're recognizing the failure of waterfall and the need to measure in-process work. It's time to do "software at home." Where we're going is to resolve this challenge, with short cycles, feedback, testing, craftsmanship.
The agile community: The Scrum paper in '95, XP in '99: resonated with the community. But we were fractured into many agile methods; branding. Now, industry is learning to pull and mix practices; we're at the moment of convergence. Future: head away from brands, strong focus on project management. At the end, we'll have a definition of agile.
Users: Were small teams with a programming focus; limited acceptance tests, project managers "lost." We are a community that has grown. We see 80-people teams often mixing Scrum and XP. 300-person teams exist. A company of thousands doing transitions. Future: we'll grow. Agile project management will happen. Automated acceptance tests will be regarded as the measure of progress.
Brian Marick: There was a group of English cyberneticians. They made discoveries of performance, adaptation, surprise. But oops... no (single) institutional home, no acknowledged base body of techniques, no grooming of successors. Their tradition is gone.
To avoid this, "we gotta take over a university department." He announced the "Gordon Pask award", to honor people whose recent contributions demonstrate their potential to be leaders of the field.
There were a lot of topics; see the web site. One was "XP Rituals", where we identified a number of fun things:
- Breath mints
- Haiku written on card before starting a task
- Hacky sack at standup
- Traffic light for builds
- Darts when a pair finishes a task
- "Story starting" gong
- Story completion frog (noise-maker) or bell
- Daily progress chart - two thermometers, showing days used and points locked in
- Automatic break program
- Smiley stickers for story cards
Metaphors, by Dave West
In 2001, metaphor was listed as an official XP practice (part of architecture); in 2005, it was not. Kent has said its redundant as a practice since you can't help using it. (Dave argues it's a learned skill.)
Metaphor has a lifecycle from poetry through use. Lakoff and Johnson say all thought is based on metaphor. Dave argues:
- If you don't choose consciously, you get one unconsciously.
- Metaphor selection has a real effect on software design (architecture).
- Metaphor is a skill you can develop.
- Therefore, it should be an agile practice.
We have many default metaphors: machine, org chart, entity, dualism, computer science, software engineering, product manufacturing. There are alternatives: e.g., object as person.
To use metaphors well, learn: reflect, experiment, read widely, liberal arts, point of view.
Tim Lister: XP Denver Invited Talk
- Managers are lonely - they don't have a collegial environment.
- QA is a bottleneck, and no wonder: it's done late and in serial rather than in parallel.
- Getting agreement on requirements is not neat. "Gathering requirements" sounds like they're Easter eggs in the yard. But really, most requirements have to be invented.
- Problem: people believe the customer.
- It's messy, so model and prototype. Don't prototype solutions - prototype wrong things on purpose (so they can laugh at it).
- Estimating is overwhelmed by expectations: skew (never early). Separate goals from estimates.
- Software in general is uninteresting. "One right way" is anti-intellectual.
- "Never lose the satisfying feeling of making something valuable, together with your colleagues."
Related Topics >>