timeout - when play is temporarily suspended at the
request of a team to discuss strategy
One of our team
norms is
anyone can call a timeout . When people are busy,
either
pair-programming or otherwise engaged, and
someone needs to discuss or share something with the rest of the
team, they can call a timeout. In response, we huddle in the
bullpen or congregate around a
whiteboard. A timeout is not called lightly because everyone knows
it interrupts
flow . And it takes each person
15 to 20 minutes to get back into their
flow following the interruption.
However, our team is
self-organising and we make all
our decisions by
consensus . Calling a timeout
causes everyone to down-tools and brings everyone together to focus
on the reason for the timeout. It creates an opportunity for
everyone to express their opinions and for the team to arrive at a
sustainable agreement about the steps forward.
Tuesday, 25 July 2006
Calling 'Timeout!'
Posted by Simon Baker - Permalink
