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

Sat, 17 Feb 2007

Chet's idea - training for charity

At SDTconf, there was a session on how to improve skills. It is too easy for people to come into a job not knowing enough and then get stuck at that level. Perhaps they deserve being stuck; perhaps they should be studying on their own. Nevertheless, they aren't, and their lack of skill sometimes (often?) prevents really successful Agile projects from forming.

What to do, given that your typical 2-3 day course delivers some knowledge and some motivation, but not skill?

Chet Hendrickson had an idea. This is how I remember it:

  • Find a deserving charity that needs software. Some stable organization (such as the Agile Alliance) offers to build it for them. The charity has to promise to be involved: onsite customer, for example. The project would have to be located where the charity is.

  • The project would be started and anchored by people who really know Agile.

  • Corporations, especially big ones, contribute to charities. Sometimes they contribute the time of some of their people. We'd be asking them to contribute two weeks of the time of software people to our project.

  • Those people join the project at staggered one week intervals (so that each week has some "old timers" and some new people).

  • They learn by doing.

I'd like to be involved in this, but I don't see myself starting it up.

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