Skip to main content

William C. Wake

William C. Wake is an independent software consultant, coach, and trainer. His interests include agile methods, impossible objects, and games and simulations for teaching. He's been using Java since 1.0.2. Bill is the author of the 'Refactoring Workbook' and 'Extreme Programming Explored.' His web home is at


wwake's blog

ScrumGathering '07

Posted by wwake on June 5, 2007 at 4:08 AM PDT

The last ScrumGathering was held in Portland, OR, May 7-11.

On Tuesday, Mike Cohn and I taught a course centered around a series of case studies. Wednesday and Thursday were Open Space sessions.

The overall site for the Gathering is here".

Stories for

Posted by wwake on May 10, 2007 at 7:21 AM PDT

William Pietri provided a list of the user stories his team used in creating

Schools of Software Testing

Posted by wwake on March 22, 2007 at 5:34 PM PDT

I ran across an interesting talk by Brett Pettichord: "Schools of
Software Testing":

CFP - Tabletop 2007

Posted by wwake on March 6, 2007 at 6:04 PM PST

Call For Participation

The Second IEEE International Workshop on Horizontal Interactive Human-Computer
System (Tabletop2007)

Newport, Rhode Island, USA, October 10-12, 2007.
Held in conjunction with ACM UIST 2007

Supported by IEEE

The use of the tabletop as an input/output device is an exciti

Project portfolios and agile

Posted by wwake on March 5, 2007 at 5:14 AM PST

Project management from a portfolio or stage-gate perspective (including how agile development fits in): "Rockets, Cars and Gardens: Visualizing waterfall, agile and stage gate."

Leadership Reading List

Posted by wwake on January 30, 2007 at 4:59 PM PST

Tom Mellor, Alan Shalloway, Bob Schatz, and I put together a reading list on leadership, available on the ScrumAlliance web site.

Using actuals with estimates - an experiment

Posted by wwake on December 15, 2006 at 4:48 AM PST

I work with a group that's been estimating in pair hours for a while. We'll describe a story, everybody will write their estimate on a card, somebody collects the estimates, and we make an overall estimate. (The tricky part is that an estimate needs to include the tasks that aren't yet known but that will be discovered.)

We also track actuals.

Set-Based Concurrent Engineering

Posted by wwake on December 3, 2006 at 7:54 PM PST

Just a pointer to an article I created, exploring lean product development and how set-based concurrent engineering relates to software.

ScrumGathering '06, Open Space

Posted by wwake on November 16, 2006 at 7:06 PM PST

The fall ScrumGathering is in Minneapolis, MN, this week. I'm here for the two-day open space and the trainer's meeting.
Groups are using as the conference proceedings.

Alistair Cockburn article on improving bottlenecks

Posted by wwake on November 11, 2006 at 6:46 AM PST

"Two Case Studies Motivating Efficiency as a "Spendable" Quantity", by Alistair Cockburn.

A bottleneck limits the rate of production of a system. Clearly we want to improve its performance. But what should we do about non-bottlenecks?