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

Wed, 14 Apr 2004

Gift exchange

[Update: added link to Marcel Mauss's The Gift. Thanks to Finlay Cannon for correcting the misspelling that made me unable to find it.]

The gift exchange, as opposed to barter or contractual exchange, is particularly well suited to social systems in which great reliance is placed on the ability of well-socialized persons to operate independently of formal controls.

W.O. Hagstrom, The Scientific Community, p. 21

An agile team is such a social system. A company within which agile projects flourish might be one too. What kind of gifts are exchanged?

Given my niche, I'm interested in gift exchange between testers and other team members. It seems to me that the gift the testers (at least those on the left side of the matrix) give is to increase the velocity of the team. They help the programmers produce more features per iteration, enhancing their credibility, giving them more scope to do the kinds of things they want to do. They help the customer demonstrate more features per iteration to the interest groups hovering over her shoulder, thus enhancing her credibility etc.

But what gift do the testers get in return? Testability support. A feeling of being more central to the team. Influence into the shape of the product. And...? I'm giving three talks this year about the role of testers on agile projects. I want to concentrate on the team support half of that role (as opposed to the product critique half). Thinking about how testers fit into a gift economy may help me.

## Posted at 07:20 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