View low bandwidth version

Archive for the ‘participation’ Category

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!