Exploration Through Example

Example-driven development, Agile testing, context-driven testing, Agile programming, Ruby, and other things of interest to Brian Marick
191.8 167.2 186.2 183.6 184.0 183.2 184.6

Mon, 10 May 2004

Agile customer mailing list

Inspired by a couple of consulting trips, I've started a new mailing list: Agile-Customer-Today. Here's the blurb:

This group is to serve those people whose role on an agile team is to guide the project. They're called, variously, "customers", "product owners", "business experts", "Goal Donors", etc. It's a really hard job, so this group is for those people to ask questions, share ideas, and describe their experiences.

A typical conversational thread might start with one customer saying, "I am having real trouble explaining my stories clearly enough that they're really 'done' when the programmers think they're finished. For example, [...]. What do other people do?" Then other people on other projects will share tricks of the trade.

This group isn't only for customers. Having worked with customers on past projects, programmers, testers, and managers can help other customers today. But this is not a group *about* customers; it's a group *for* them. The acid test for posting should be: "Will my words, read today, help some customer on some project do her job better?"

You can sign up by sending mail to agile-customer-today-subscribe@yahoogroups.com or visiting: http://groups.yahoo.com/group/agile-customer-today.

## Posted at 12:30 in category /agile [permalink] [top]

About Brian Marick
I consult mainly on Agile software development, with a special focus on how testing fits in.

Contact me here: marick@exampler.com.

 

Syndication

 

Agile Testing Directions
Introduction
Tests and examples
Technology-facing programmer support
Business-facing team support
Business-facing product critiques
Technology-facing product critiques
Testers on agile projects
Postscript

Permalink to this list

 

Working your way out of the automated GUI testing tarpit
  1. Three ways of writing the same test
  2. A test should deduce its setup path
  3. Convert the suite one failure at a time
  4. You should be able to get to any page in one step
  5. Extract fast tests about single pages
  6. Link checking without clicking on links
  7. Workflow tests remain GUI tests
Permalink to this list

 

Design-Driven Test-Driven Design
Creating a test
Making it (barely) run
Views and presenters appear
Hooking up the real GUI

 

Popular Articles
A roadmap for testing on an agile project: When consulting on testing in Agile projects, I like to call this plan "what I'm biased toward."

Tacit knowledge: Experts often have no theory of their work. They simply perform skillfully.

Process and personality: Every article on methodology implicitly begins "Let's talk about me."

 

Related Weblogs

Wayne Allen
James Bach
Laurent Bossavit
William Caputo
Mike Clark
Rachel Davies
Esther Derby
Michael Feathers
Developer Testing
Chad Fowler
Martin Fowler
Alan Francis
Elisabeth Hendrickson
Grig Gheorghiu
Andy Hunt
Ben Hyde
Ron Jeffries
Jonathan Kohl
Dave Liebreich
Jeff Patton
Bret Pettichord
Hiring Johanna Rothman
Managing Johanna Rothman
Kevin Rutherford
Christian Sepulveda
James Shore
Jeff Sutherland
Pragmatic Dave Thomas
Glenn Vanderburg
Greg Vaughn
Eugene Wallingford
Jim Weirich

 

Where to Find Me


Software Practice Advancement

 

Archives
All of 2006
All of 2005
All of 2004
All of 2003

 

Join!

Agile Alliance Logo