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, 06 Feb 2007

Shifting work to the product director

I realized recently that we on the development side of the Agile house have shifted work onto the already-overworked product director.

Once upon a time, the business gave the development team a big chunk of work to do. They also asked the team to estimate the work. The team's estimates were almost always wildly wrong. Badness.

A solution appeared: break the chunk down into small stories. (I like them to be half a day to three ideal days long.) Not only will the individual estimates be off by a smaller percentage, a sort of law of large numbers will cause the errors to average out, making the estimate for a whole iteration accurate.

That's good for estimation, but programmers tend to think of system building as getting the infrastructure right and then popping features onto it. You can't take three weeks—or months—to build infrastructure if you have to finish the story in three days. So programmers wonder why the result of small stories isn't a big, unwieldy pile of disconnected code. I answer that there are tricks and tools to help: refactoring, the removal of duplication, IDEs that make large renamings and restructurings safe, reduction of code ownership, and so on. It is possible, I say, for the end result of small-story development to be a system that looks as if it had had an infrastructure designed in from the start.

Swell. But something's been lost. In the old days, it was (somewhat) easy for the business representatives to wrap their heads around the release. They could talk about it as a large conceptual piece that hung together from the point of view of an end user. To some extent, the programmers were responsible for living up to that conceptual vision. Now, they no longer are. It's the product director who must keep track of all the small pieces and make sure they add up. Moreover, she must do that not all at once, but continually as the product grows throughout a release cycle.

I think that's hard. The tools and tricks for doing it are not nearly so developed as are refactoring, etc. (There are some, such as Jeff Patton's span planning and feature thinning.)

So we on the development side have made our estimation job easier by shifting work onto the business. Nice trick.

## Posted at 09:24 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