Red Squirrel Reflections
Dave Hoover explores the psychology of software development

Dave Hoover
dave.hoover@gmail.com

Categories
All [Atom]
Craftsmanship [Atom]
Dynamic [Atom]
Intersection [Atom]
Learning [Atom]
Links [Atom]
Polyglot [Atom]
Projects [Atom]
XP [Atom]
Old Blog

Obtivian Blogs

Andy Maleh
Colin Harris
Fred Polgardy
Jake Scruggs
Kevin Taylor
Renzo Borgatti
Ryan Platte
Todd Webb
Tyler Jennings

Archives

June 2008 (4)
April 2008 (3)
March 2008 (1)
February 2008 (1)
August 2007 (1)
July 2007 (1)
June 2007 (1)
May 2007 (4)
April 2007 (3)
March 2007 (5)
February 2007 (6)
January 2007 (6)
December 2006 (10)
November 2006 (5)
October 2006 (8)
September 2006 (8)
August 2006 (5)
July 2006 (12)
June 2006 (7)
May 2006 (5)
April 2006 (5)
March 2006 (4)
February 2006 (2)
January 2006 (5)
December 2005 (5)
November 2005 (3)
October 2005 (3)
September 2005 (6)
August 2005 (4)
July 2005 (7)
June 2005 (14)
May 2005 (6)
April 2005 (8)
March 2005 (9)
February 2005 (11)
January 2005 (16)
Old Archives

 

Tue, 01 Mar 2005

Be the Worst

When asked to give advice for young musicians, Pat Metheny said...
"I have one kind of stock response that I use, which I feel is really good. And it's 'always be the worst guy in every band you're in.' If you're the best guy there, you need to be in a different band. And I think that works for almost everything that's out there as well.
This sums up perfectly why I came to ThoughtWorks. It also feels like it could be a seed for an apprenticeship pattern language. More on this in the weeks ahead...

(Via Chris Morris.)

[/links] permanent link

Crisis Acceleration

In their excellent Organizational Patterns of Agile Software Development, Jim Coplien and Neil Harrison pointed out...
"...changes at this [the organizational] level do not come easily. It may take years, or perhaps even a crisis, to shake the foundation of the organization--it's value system." page 311
Whenever I hear "crisis" and "change" in the same breath, I think back to a child and family therapy technique called raising the bottom. And I ponder anew how this concept could be applied appropriately to software development.

Agents of change are well aware of how difficult it can be to affect change in others. But they also know that the fastest route to significant change is a crisis. They have a challenging problem with a tricky solution.

The good news is, we have the solution. The bad news is that humans tend to dislike this solution (a crisis) even more than change itself. Even worse, no one wants to be the cause of a crisis, because those people tend to be targets of blame. But what if we could openly and responsibily accelerate an organization or a team into a crisis in order to bring about change and avoid a more dangerous crisis down the road?

The classic example of a crisis acceleration: Parents who cut off their drug-addicted child, leaving him to fend for himself. The parents would have already engaged the system around the child to help him have a controlled landing. They coordinate with the police, the school, therapists, friends, relatives, as much of their child's system as possible. What sort of parents would do this? Parents who are convinced that their child is going to end up dead in a gutter. They would rather have their child hit rock bottom on their terms.

Food for thought...

"It may look like a crisis, but it's only the end of an illusion." --The Secrets of Consulting

[/intersection] permanent link


powered by blosxom