Category Archives: Uncategorized

mistake to write down values without necessary ambiguity – use stories. @snowded #lssc11

i followed Snowden’s talk on LSSC 11 via twitter, i.e., via reactions and thoughts by people being there, and Snowden’s own blog posts.

One of the points I made in yesterday’s keynote was that it is a mistake to write down your values, as the act of codification results in their loss. In effect we shift an ideation culture (the way we do things around here that we all understand but can’t really articulate) to an explicit rule based culture. Aside from the fact that I have yet to see a set of organisational values that were not a set of well meaning platitudes, all you are really doing is teaching the politically manipulative the language of power.

….
we need to [articulate values] in a way that carries with it necessary ambiguity so that the statements can adapt to context, and also so that their form allows for verification of actions, not just linguistic form.

Parables, fables, short sayings – often paradoxical in nature, archetypal stories and characters:

…. more pedigree and more sustainability than a few pious banalities on a motivational poster. All of them involve small, pithy and frequently paradoxical stories. The point here is that a story carries context with it, as well as the ability to create resonance. Critically it allows for ethical validation; saying that action X was consistent with a mission statement is easy, matching it against a story is far more difficult.

(emphasis mine)
Tw4
Tw1
Tw2
Tw3

 

sw dev, design: iterating, incrementing vs backlog mapping

Jeff Patton illustrates iterating and incrementing well:

Incrementing

incremental development – we build a piece at a time, having a finished design upfront, expecting no changes.

Iterating

iterative development – we build something, then evaluate, then make changes to it, i.e., we expect to change it.

(i don’t quite like that both illustrations end up in the exact same Mona Lisa…)

i just saw a very nice description of a backlog mapping by Energized Work, described by Simon Baker. Lisa Crispin also blogged about it after a visit – The Whole Team Approach in Practice.

what i really like about this is the support for starting small, iterate+ increment, while keeping functionality and value visible.

Backlogmapping

Update:

There’s also a post about a mind-map form illustration high-level user experience replacing backlog, also at Energized Work.

Energizdwork-backlog

The pink Post-It notes represent the different users. The blue Post-It notes represent the user activities and the yellow Post-It notes represent the high-level user tasks.

Another quote from this (emphasis mine):

We don’t use a burn-down chart to illustrate how much of the backlog is done. We consider this to be waste because the product is a moving target and the backlog can never done until the product is no longer available. However, we do visualize the investment made in the product to date.