View low bandwidth version

Archive for the ‘participation’ Category

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)

The Rise of Digital Resilience

Saturday, January 29th, 2011

What I really mean is “ICT Resilience” but that doesn’t sound as memorable.

I’ve been wanting to write some thoughts about Digital Resilience for a while and reading Janet Gunter’s blog post about Mobile Blackouts and the Poor has prompted me into finally doing it.

I think we’re going to see the subject of Digital Resilience rising in our consciousness over the coming years… at least we should. What do I mean by it? We regularly allow ourselves to rely on information and communication technologies but these tools can be  fragile and have many modes of failure. Often this fragility is not taken into account. I see this all the time.

Here’s a typically example. I’m on the phone to a friend organising an evening out. How many times have I heard the phrase “I’ll call you when I get to town”? This relies on us both having signal, on our batteries not running out and on our phones not breaking, being lost or stolen. Modern “smart” phones eat through their batteries at a tremendous rate and sometimes crash or reboot so these failure scenarios are not that unusual. If any of the things that our phones rely upon fail what is our back-up plan? Are we going to wander around the city, aimlessly, hoping to bump in to each other? Or go home?

A failed night out is not the end of the world. The point I’m wanting to make is that most of the time people seem oblivious to the failure modes of the technology they use or the need for back-up plans. And yet when you’re in the habit of considering technological risks it becomes second nature, like finishing a sentence with a full-stop
.

So when I hear “I’ll call you when I get to town” I usually can’t help myself say “And if I don’t hear from you, I’ll meet you at the station…”

The situation gets a little more serious in a business context. Take the example of a conference call. Scheduling a call between several people can take a lot of planning trying to find a time when everyone is free. If this time-slot is missed it can represent a significant opportunity cost to the organisations involved. The duration of the call itself represents a cost when you consider the time of the people involved. There is growing use of Skype for conference calls in the professional community. Sometimes Skype works very well but in my experience it frequently doesn’t work at all. Many times I have been asked to participate in a Skype conference call with no back-up even when many of the participants are in developing countries. When the Skype call fails much time is wasted, sometimes several participants are excluded and sometimes the call is abandoned all together. My automatic response to a Skype invitation is usually to send round the number of a phone conference service just in case.

OK, failed conference calls are still not the end of the world. For someone poor or vulnerable a technology failure could be much worse. At the recent ICTD2010 conference I was very interested to hear for the first time a few people talking about vulnerabilities to the poor caused by reliance on ICTs. For years the ICT4D community has been promoting the use of ICTs in poverty reduction. There has been a fair amount of work in adapting technologies for harsh environments. However these technologies still have failure modes and it was very encouraging to hear the resulting vulnerabilities being discussed.

Digital resilience is less about building robust technologies and more about building an understanding of its failure… and the habit of back-up plans.

ICTs for Rural Development Seminar

Wednesday, October 27th, 2010

Just attended a very interesting seminar on The Rural Information Economy and ICTs, hosted by the UN Food and Agriculture Organisation (FAO), a major actor in this area, at their headquarters in Rome.

This is an area in which Aptivate is also very interested, and one in which I’ve done some research and been following developments. I still managed to learn quite a bit from three very interesting presentations:

Information Economy Report 2010 (UNCTAD)

The informational dimension of poverty, i.e. where information can help to alleviate or reduce poverty:

  • Market price information
  • Income-earning opportunities (e.g. jobs)
  • Weather information and warnings
  • Correct use of pesticides and fertilisers
  • Health information and education
  • Disaster risk reduction

Communication up and down the supply chain, and with peers and advisors, also helps.

There is an increasing trend to direct involvement of the beneficiaries in the production of ICTs:

  • As ICT workers
  • Manufacturing of ICTs (as an alternative occupation to subsistence farming)
  • Providing IT and ICT-enabled services (answering questions, finding information, running telecentres)

Mobile phone penetration has exceeded all other ICTs in growth in developing countries. On average in the least developed countries, it has increased from 2% to 26% of the population (1000% growth) from 2000 to 2009. Possibly the fastest-spreading technology ever in the history of the world.

Growth is uneven. There are still some LDCs where less than 10% of the population have a mobile phone. In Ethiopia for example, only 5% have a phone. This was largely attributed to lack of liberalisation of telecomms markets.

Half of rural population in LDCs have no access to a mobile phone signal, which will limit the further growth of mobile usage. Many Universal Service Funds are sitting unused. In some cases this is because they are mandated only to be used on the fixed line network, which is nearly obsolete.

Mobile micro-insurance has become a big topic. For example:

  • Kilimo Salama in Kenya
  • Burkina Faso, Mali (index-based crop insurance)
  • Alliance Afrique

Kilimo Salama recently made their first payouts to farmers because weather conditions exceeded their thresholds. The payouts are automatic and don’t have to be claimed by the farmers. The largest was about $30.

Even those who don’t have access to ICTs themselves can benefit from more transparent markets when enough participants use ICTs.

Download the full report (PDF, 171 Pages, 1240Kb).

Enabling role of ICTs to transform smallholder farmers to entrepreneurs (IFAD)

IFAD offers grants and loans to governments for argicultural development programmes. They are starting to offer grants (but not loans) to the private sector as well.

Grameen and BRAC had limited success with mobile banking (so far), because most of their customers are groups, not individuals, and mobile phones tend to be personal devices.

IFAD and WFP are running a joint project called the Weather Risk Management Facility (WRMF), a micro-insurance project. Half of the insurance premiums are paid by the farmers, and half by the sellers of inputs (seeds, fertilizer, pesticides) as they benefit from farmers being willing to buy more of their products due to reduced risk of crop failure.

ICTs enhancing plant production at the field level (FAO)

e-Locust2 uses vehicles with GPS, laptops and HF radio modems to send real-time information on locust swarms to governments, which can help to warn and prepare neighbouring villages and allow the targeted use of pesticides to control the pests. Time is critical to achieve this.

Digital Pens are being used to capture information entered on forms. The pen recognises what is being written, and where on the form, and captures the data for later upload. This makes it possible to have electronic filing with minimal training, minimal unreliable ICTs, an inherent fallback to paper-based methods, and hard copies of the forms that can be given to farmers or stored in local offices.

There are problems getting pest monitoring officials to enter high quality data when there is no incentive (reward) for accurate data, e.g. in one-way monitoring systems. If governments used this data to target their interventions, villagers would have a much more obvious incentive to ensure that the data was entered accurately and on time.

Thanks

Thanks to FAO for hosting this excellent seminar, and to the World Food Programme for allowing me time off to attend it.

Several of us expressed an interest in continuing the discussion online, we have been heard, and Michael Riggs, lead facilitator of the e-Agriculture Community, is working on enabling this to happen. There will also be a follow-on discussion at the ICTD 2010 Conference in London.

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.

R&D: Robots and Development

Tuesday, March 16th, 2010

The Samfya Resource Centre is a telecentre (Internet cafe) run by young women in Samfya, Zambia for other local young women – a component of Camfed‘s “CAMA” network. As part of our ongoing support for the Samfya Resource Centre, we have sent them robots.

drawbot

(c) Fatuma Iseje

Why robots? As a child I grew up programming the Sinclair ZX81. A small computer about the size of a book, with a touch-(in)sensitive membrane keyboard and 1kB of memory. With computers we spend long hours staring at the screen interacting with a virtual world made of intangible pixels. I remember being constantly frustrated that my computer couldn’t do anything in the REAL world. It couldn’t turn lights on and off, it couldn’t move and back then it couldn’t even makes noises. In fact I killed the poor thing when I dropped a soldering iron through the CPU while trying to interface it to my physical world.

It’s all different now. With the advent of devices like the Arduino it’s now easy and cheap to get the computer to reach out into our world. And we can reach into its world. Not only does an Arduino let us physically interact with the computer it can also be automonous. We can make things that interact with us without needing the computer attached to the other end of its USB umbilical cord.

For those that haven’t come across it yet, an Arduino is a simple micro-controller board. OK… what’s so amazing about that, there’s been micro-controller boards around for decades? Well, a few things. Firstly it has a USB port so you can easily connect it to your computer. It has its own simple programming environment using a variant of the C programming language. So it’s not dumbed down at all – no visual programming environment or anything like that. And critically there is a large on-line community eager to share and support people who do not come from a technical background. Its design is open source, it’s cheap (£20) and you can find even cheaper clones.

This exploding field called “Physical Computing” is making computing more fun, more compelling and also sometimes more useful.

Ok robots might be fun, but why send them to Zambia?

The computer used to be like a calculator on steroids. It could “compute” things. If you knew a bit about SIN or COS you could make it draw a circle. Or calculate a volume. Now, although computers are enormously more powerful than the Sinclair ZX81, most of us use them like some mash-up of a TV and a phone. They give us access to information and lets us communicate. These are important and useful functions. But I worry most of us are in danger of treating our computers like new cars – like devices with “no user serviceable parts inside“.  Instead of seeing them as tools that we can fix, modify, improve, re-invent and tailor to our needs.

It’s more than that. Computers aren’t just useful for the stuff they do. I believe that programming computers, tinkering with them, making electronic circuits and building robots builds highly transferable skills. Critical thinking, logical and abstract reasoning and problem solving. In addition, programming an Arduino makes you a dab hand at searching the Internet.

I got into robots at BuildBrightonBrightonRobot – the Brighton hacker-spaces based out of The Skiff – and in particular through Steve Carpenter’s amazing kits.

Eva with the Drawbot - (c) Fatuma Iseje

As an introduction to robotics, we’ve used the “DrawBot” packaged up by Steve with excellent instructions. How complicated and expensive do you think an autonomous drawing robot would be? How about 6 components that require no soldering costing about £3?

Steve has also designed a great robot kit based around the Arduino – the BoxBot. The kit is designed using the Interlocking T-Bolt Construction method, a cost-effective technique for low volume manufacture. With servos and everything you need minus the Arduino, the kit’s about £60. It’s a very flexible kit, you can bolt sensors or motors all over it – but this is not Lego. You need to drill holes in it.

Reading the educational posts about robotics I can see that from a teacher’s point of view an Arduino and the BoxBot may not be ideal. They don’t neatly fit into lesson plans. They don’t just leap into life in a way that keeps a lesson of 30+ students moving along. They take a bit more application and research to use. But unlike Lego, Meccano and other modular systems, they blur the distinction between the kit and the rest of the world. Once you’re empowered to drill holes and wire up your BoxBot you find you’re up for drilling holes and wiring up anything.

Using robots in this context is an experiment for us. We don’t know how it will go. But it’s an experiment the young women of the Samfya Resource Centre are excited about.

We’ll keep you posted on the progress of our latest bit of R&D.

Hi” and “Mulishani” to Bridget, Everlyn, Fatuma, Mary, Mildred and Penelope at the SRC from the Aptivate gang!

Getting Ready for Crisis Camp London – Day 2

Thursday, January 28th, 2010
Crisis Camp London

Crisis Camp London

We’re getting ready for the second Crisis Camp London day, this Saturday, at the London Knowledge Lab.

Considering how quickly last Saturday was put together we had a great turn out. We’re hoping for, and expecting, an even larger turn out this time.

We’re getting out all the laptops, network gear, and spare projectors we can find. We’ve got enough flip-charts to paper the Albert Hall. I even heard that Domino’s were considering sponsoring the pizza again – and with added vegan options too. Many thanks to them!

We’re on conference calls to the US Crisis Camps and projects. We’re part of a strong team looking after the organisation, infrastructure and facilitation of the London event.

It really is quite something the speed with which this is coming together and the level of interest and motivation. This looks set to become an important movement.

If you are technical (eg. an IT project manager, a coder, a user experience person) or have relief experience and want to help Crisis Camp London support Haiti, then please come along.

You can also help by printing out and displaying the Crisis Camp London Poster

#CrisisCampLDN

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!