I am an ironing board

Session Notes for Open Space session at Agile Open, California, Thursday 9th October 2014. Around 25-30 people in attendance.


Session title: Metaphor—Why?

Introduction: (System) metaphor is one of the original XP principles, but has been neglected over time in favor of other, more actionable principles such as test-driven development and continuous integration. A system metaphor creates a shared understanding, and its absence often creates misunderstanding and misalignment. In this session I’m interested in exploring metaphor, not specifically for code, but for human systems,and also individuals. Metaphor can create new understanding, new ways of looking at familiar situations. What might it mean, for example, to say to someone, “you are an ironing board”.

Part #1

For want of a plan of any kind, I started the session with this question, and asked participants to pair up and explore what it meant to them. Some pairs explored it from a personal perspective, and some from the perspective of their work role, e.g. developer or Agile coach. In sharing we focused on “I” statements, and paraphrasing…

"When I am folded away in a closet I see the world differently to when I am out in the open, being of service."

"I seek something hot and steamy to be pressed against me."

"I am the body of workers that supports the change agent (the iron) in removing the wrinkles in my organization (the clothing). Without me there is no foundation for improvement"

A nice corollary for this last one, from the iron’s perspective, was “If I stay too long I will burn a hole, and ruin what I am trying to improve.”

The neat thing about facilitating an open space session, is the sense of release. The session goes where it goes, and all I needed to do was embrace the ideas that emerged, turn them into offers, and suggest some containment for the dialog.

Part #2

The “I am” statement led a participant to be reminded of an improv exercise called Invocation, where an object is identified of spoken of in four different ways, each one taking the speaker from objectivity to subjectivity: “It is…”, “You are…”, “Thou art…” and “I am…” We practiced this framework in the second part, people finding a new partner and offering an object of their own choice, e.g. bird, flipchart marker, redwood tree, highway… The use of this framework led people to greater empathy. Was that what we were seeking with metaphor? Perhaps. The following discussion looked at the difference between the incremental understanding and the immediate jump to “I am”. The latter is more of an analogy: I am like this thing because… opening up new ways of seeing self, while the former takes the speaker deeper into a place of understanding of the other (thing). 

Note: when my partner struggled with the “Thou art” part, I asked him to recite a love sonnet to the flipchart marker he was holding. “Thou art an extension of my imagination…”, he began. I don’t recall the rest but it was very eloquent, and oddly moving. When he tried to do the same in front of the group he wasn’t able to, and afterwards commented how wrong it felt to express intimacy in front of a large group.

Part #3

We discussed the idea of using another person as the “object”. A traffic cop. 1) It is an authority figure, uniformed, unwelcome. 2) You are a man with a job to do. You need to earn a living like the rest of us. 3) Thou art a keeper of the law, a man with a mission. Thou art possibly a family man, seeking to improve the life of your family in the best way you can. Thou enforces the law because thou believeth in justice.” 4) I am a man with a mission, a believer in truth and justice. I care for my community and want to help others do the same. This had now moved beyond metaphor into a pure empathy exercise. Time for a retrospective. Are we getting what we want from this session? Where do we want to go now?


I asked for the five most vocal people to form small teams. Their job was to facilitate a dialog and not speak themselves. One of them asked, what, not speak at all? I had rather meant that they did not offer input but made sure all voices were heard, but this was an idea worth exploring. Yes, facilitate in complete silence. Feedback from the facilitators was interesting. In general it improved the ability to listen. The retrospective gave us three topics to explore further, so we created an short open-space-within-open-space. 

Part #4

  1. The use of metaphor in retrospectives—how would it help to ask participants to come up with a metaphor for the last sprint? What new avenues of exploration/understanding might it encourage?
  2. Exploring common metaphors, e.g. herding cats, war room, firefighting. Many of our metaphors are negative, or derogatory, creating a (perhaps) undesirable mindset. We looked for new metaphors, and the one that shone for me was a new way at looking at “cat herder” (a typical description of a project manager). I am a builder of playgrounds. This idea completely changes how one might approach their job: don’t try to manage the chaos, embrace it and support it with fresh imagination.
  3. Empathy via Invocation. Some wanted to explore this further. I have no notes for this short session.

Time expired, so the small groups dissolved. I asked those remaining at the end to practice with each other during the event, by simply offering a “you are an [object]” challenge to one another at random moments, and see what happened. As I left the eception at the end of the day, I offered a colleague “You are a stuffed mushroom”. I look forward to hearing what he had to say to the others in the group when we next meet.



2014 Ads+Data design offsite. The talent at this table is immeasurable.

A colleague and collaborateur is moving on to new pastures. Farewell, Leonardo. I shall miss you, and our inspiring idea-building conversations.



2014 Ads+Data design offsite. The talent at this table is immeasurable.

A colleague and collaborateur is moving on to new pastures. Farewell, Leonardo. I shall miss you, and our inspiring idea-building conversations.

The Secondary Indirective

This is an alternative to the Prime Directive for opening a retrospective. It isn’t a directive, and it needn’t be primary, just something you may like to reflect on with your fellow workers.

We are emotional and vulnerable beings, subject to a continuous flow of influences from a myriad of sources. Sometimes we perform magnificently, other times we mess up. Mostly we are somewhere between these extremes. In this last period of work everyone did what they did, and likely had reasons for doing so. Accept what is. And now, what can we learn from our past actions and thinking that will inform and guide our future ones?


originally posted on AgileAnarchy in 2010

Self-management, really?

The term self-management has become popular recently, often replacing self-organization as the default term for describing agile teams. I don’t like it, and I don’t believe it carries the same meaning—at all.

Read More

Scaling Agile — a perfect method

There are lots of frameworks and suggestions these days for how to scale Agile to the enterprise. They all miss the point, because the proponents of these methods use the wrong definition for scaling. I have a perfect method for scaling Agile. To describe it I’ll use a fish metaphor. A fishmonger scales fish in just the same way we should be scaling Agile. I actually call this method Scaling and Filleting Agile, or SaFA for short (pronounced “safer”).

Read More

Don’t give me feedback

I don’t like feedback. I’ve never liked feedback. Not liking feedback has been problematic as people take it to mean that I don’t want to learn and grow. This mindset is so prevalent that I began to believe it myself. What’s wrong with me, I wondered, that I can’t hear critical feedback? Am I so arrogant as to believe I have nothing to learn from others? Intuitively, I know this isn’t true, and yet I balk every time someone offers me feedback. I’ve come to realize that my desire to learn through listening and reflection is misaligned with the primary technique we have to drive that learning. Feedback fails us.

Read More

Project Management. Sigh!

"Let’s organize this thing and take all the fun out of it" — Ashleigh Brilliant

I’m aware that some folk think I like to dismiss project/program managers as unnecessary overhead in organizations, so I’ll start by saying I know some wonderful people who work under these titles. This post is not about people, it is about roles. I strongly believe the PM/PgM role is a cop out. It is an excuse for poor collaboration, and a necessary role only as long as developers and customers refuse to talk to one another in healthy, collaborative ways.*

Read More

The Scrum Sacrifice

My upcoming talk at Scrum Day San Diego

Scrum is a paradigm-shifting ideology. Trouble is, most leaders and managers don’t want to be shifted. They’d rather have their existing beliefs endorsed, and so they look to Scrum as a methodology to put a better face on existing ways of working. They look to Scrum consultants the same way they may look to beauticians or plastic surgeons. 

Read More

The scrum board: dead on arrival

A few years ago I wrote

The longer I teach and coach scrum, the more I become convinced that the physical workflow board is the heart of scrum. Without the workflow board, a team has no center, no focus, no hub.

More recent experience has shown me that this heart has no beat.

Read More

Scrum: The Necessary Conditions

[Originally published on ThePeoplesForum 8/5/13]

The previous post Scrum: a 5-step guide for managers was (quite rightly) criticized for not describing Scrum. It was never intended to. In the text I describe the five steps as being for “managers and executives for starting a new Scrum process”. The title was intended to challenge, to have people ask, so what is Scrum?

Read More