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

Tue, 07 Feb 2006


Update: I forgot that Kevin Rutherford also suggested the word "director". Great minds, etc.

Mark Smeltzer has come up with an alternative to Appraisers: Product Directors. I like that. It puts the focus on the product, not on managing the team. It connotes movement and responsiveness. Unlike the common metaphor of driving projects, it doesn't imply that other people are passive passengers. Instead, they're active participants in a joint project. If the word makes you think of a movie director, it also brings to mind that person charged with having the clearest idea of the end product during production. It also ought to have connotations of balancing features and cost, of producing the most you can within a given budget. Sometimes it does, though directors get notorious for the opposite.

We also talked a bit about "ScrumMaster" and what might be a more business-friendly term. Mark points out:

Making an analogy to the film industry, the AD (Assistant Director) role embodies many of the ideas and responsibilities associated with ScrumMasters. In the end, that may be what I go with: Assistant Product Director.

One thing I learned from the smattering of email: if told to link a name to one property of the role, different people have very different ideas of what that one property should be. Trying to pick a name within the project might lead to a useful discussion (reminiscent of Gause and Weinberg's heuristic for naming projects in Exploring Requirements). Or, in the wrong hands, it might lead to the most tedious and pointless discussion possible.

## Posted at 04:16 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.




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

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


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



Agile Alliance Logo