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

Point of view in standups

It seems to me that standups are often about what people did and are doing. They're like little slices of people's lives. Shouldn't they be more about the stories from this iteration? About how stories are progressing toward becoming complete?

Holding standups in front of a story wall helps. People tend to gesture at the stories while they speak, making them the focus of attention.

I was wondering today what it would be like if people pretended it were the stories themselves speaking:

Convert font changes into table cells (as interpreted by Dawn): Brian and Dawn worked on me all day yesterday. They plan to work more today. One of them should probably swap out, since they're getting stale.

Ajaxy update of main page (as interpreted by Chet): I'm done, coded and tested. I'm moving over to the Finished swim lane. [It uses Chet to move it over.]

That's too silly, except maybe for teams neophilic enough not to need it. I don't think I have the nerve to recommend it.

## Posted at 20:47 in category /agile [permalink] [top]

A snippet

... I told her there was hope for the Big Apple yet.

"It all depends on our ability to devise a set of robust arguments favoring either scientific materialism or theistic revelation and then commmunicating the salient points to the Martians in their nonlinguistic language, which was apparently deciphered several years ago by a paranoid schizophrenic named Annie Porlock," I told Valerie.

"That's not a sentence you hear every day," she replied.

—James Morrow, in The Cat's Pajamas and Other Stories, "The War of the Worldviews"

## Posted at 20:47 in category /misc [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