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, 31 Jan 2005

I'm a Customer on an Agile project

The Agile Alliance is revamping our website. Micah Martin of ObjectMentor wrote the first version and did a fine job, but the site's been around for four years, and technology moves on. I've been keeping it up for a year, tinkering here and there, but I don't have time to do the complete rewrite we need.

So we took bids for the revamp. Unsurprisingly, we're running the project in an Agile style. (If the second iteration goes well, we're going to start deploying in two weeks.) And I'm the partly-on-site Customer for the project, since I live about five miles from the company that's doing the work.

I'm having a blast so far. It's great fun steering the project against the background of our original story list. But it's serious fun, because all three bids came in at about the same price, and it was about twice what we wanted to pay. So we're paying what we wanted to pay, which means that I'm steering the project knowing that I have to pack the most value into the time we have, since a lot of stories will fall off the end.

I hope this will give me a hint of the insider's view of what product owners go through, especially since I hope to concentrate a chunk of my effort this year on supporting them.

## Posted at 20:06 in category /aa-project [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