View low bandwidth version

Posts Tagged ‘agile’

Jazz Talking: The Agile & Participation Event

Wednesday, September 28th, 2011

Robert and Alistair

For a while I’ve felt that the Agile methodologies from the software development world share a similar outlook to the Participatory methodologies from the international development world.

So we came up with an idea for an event. Wouldn’t it be great to get an expert from each discipline and have them talk to each other, in front of an audience?

Last night, thanks to support from the Humanitarian Centre, and our two esteemed guests, our idea became reality.

Alistair Cockburn, Agile guru, sat on a sofa next to Robert Chambers, expert on Participatory approaches, in front of an audience.

I thought it was fantastic and we’ve had a lot of positive feedback about the event. It was so good, I found myself afterwards wondering if this is in general a good format for an event.

So I wanted to write a post about the form of the event, rather than the content.

After the event I was chatting with Alistair and he’d already been thinking along similar lines. We called it a “Jazz Talk”. We were drawing an analogy with two jazz musicians improvising.

Jazz Talks

Here’s the format -

1) Get two affable speakers from different disciplines
2) Sit them on a sofa in front of an audience
3) Let them talk about the relationship between their disciplines
4) Periodically interrupt them with “Kibitzers”

Kibitzer

A “kibitzer” is a person who comments on the conversation.

“Kibitzer” was a term Alistair came up with. I had to look it up, literally it means an observer of a card game who gives (unwanted) commentary.

There’s two types of Kibitzer. A “content kibitzer” gives comment on the content of the conversation. In the event last night I played the role of one of the kibitzers and asked the question “How do we get funders to engage with agile / participatory proposals?”.  All of our kibitzers last night were content kibitzers.

Talking to Alistair afterwards, he was keen to push the idea of a “form kibitzer”. This is someone who gives a commentary on the form of the conversation, not the subject matter. For instance, “I liked how speaker-A extended speaker-B’s questions to the audience”, or “Can we hear more from speaker-A?”. I think form kibitzing is less natural but likely to be shorter. It also potentially plays a facilitatory role in guiding the conversation and could help address issues like one speaker dominating the conversation.

Perhaps a mix of both types could work. Each commentary would start with a short form kibitz followed by a content kibitz.

Timing

Here’s a suggested recipe:

  • a 90 minute conversation
  • kibitzing every 15 minutes (eg 5 interruptions)

Aptivate Speaking at Africa Gathering, London

Tuesday, June 22nd, 2010

africa gathering logoI (Alan) am going to be talking at Africa Gathering London about the reciprocal relationships between participation and IT.

Here’s the synopsis… (although Africa Gathering has previously been described as an “unconference” so I may be tempted to slip into a bit of “unpresentation” if the situation warrants it).

The reciprocal relationship between ICTs and Participation

Over the last few decades of software engineering there is a rising tide of emphasis on the value of participation. The growth of the “Agile” software methodologies is a good example. The finding, which really shouldn’t be that surprising, is that participation makes better software. Participation with the client, with the users with the
stakeholders etc.

Seven years ago, at the start of Aptivate, that’s how we saw participation. As a means to creating better software. Over the last year we have seen that relationship reverse. IT is a means for better participation. It’s not just that new technologies like web 2.0 enable people to collaborate. Engaging in software projects themselves are excellent excuses for participation and human development. Finally, the dog is wagging the tail again and not the other way round.

Africa Gathering will be in London on the 2nd and 3rd of July. Get your tickets now while there’s still some left! For more information see the Africa Gathering site.

Agile Development and Retrospectives: Learning from failure?

Friday, December 11th, 2009

I had an interesting chat with Alan last night about the role of “retrospectives” and it reminded me about the ICT4D Twitter Chat today around “Learning from Failure” being organised by the fine folks at Inveneo.

He was at the XPDay in London earlier this week – a 2-day hotbed of agile technology development geekery featuring a combination of traditional speaker sessions and open spaces.

Aptivate is a big advocate of using Agile methodologies. We see them as central to taking a participatory approach to international development. One thing we do after delivering a project is have a “debrief” or “retrospective” with the project stakeholders.

“Four key questions to focusing a community on learning and improvement” are described at www.retrospectives.com:

  1. What did we do well, that if we don’t discuss we might forget?
  2. What did we learn?
  3. What should we do differently next time?
  4. What still puzzles us?

Simple and sensible.

The key idea that Alan picked up on though was this: do a retrospective at the end of each iteration.

Every two weeks, every incremental release of a project, sit back, take an hour with your team and ask the above questions.

We’re certainly going to start doing this and from what was said at the XPDay – if you’re going to do one thing to improve your development process, do this.

Finally – ensure that all participants adhere to “Retrospective Prime Directive:”

Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.

Happy twitter chatting!