Research to Impact Hackathon ....and the winner was...

Well, we were all winners, if truth be told, in the sense that we all learned a lot from the experience of the Hackathon at iHub Research in Nairobi last week. To begin with, the iHub itself is still under three years old yet has blossomed into an extraordinary innovation centre at the centre of a buzzing ecosystem of developers, projects, events, people, good coffee and, well, more people. There are over 10,000 registered members of the iHub community and it was through those networks that we were able to attract so many creative and plugged-in developers.

One of the newer projects is iHub Research, one of the co-organisers of the event. Leo Mukutu is Research Manager there and she was one of the judges of the competition. In this clip Leo describes the role of iHub Research and the criteria she used to judge the entries.



There were six entries in all, and in this video clip people from each team describe their proposals - and you can see who won!

(Update: a summary blog from iHub research) 

'Let me Hackathon that thing'

'Every good piece of software starts by scratching a developer's personal itch', says Eric Raymond, author of the fabulous book on Open Source software, The Cathedral and the Bazaar. Hackathons evolved to harness that personal passion of software developers to create interesting code that solves problems - or sometimes, just create elegant, interesting code simply to see what happens. Organisers provide a context - for example software platforms such as Ushahidi that constantly need to to be improved or movements and campaigns such as development data or aid transparency which need lots of programmes to import and aggregate data or present the data in a form usable by others and the public - and a space, with coffee, cakes and chocolate. Developers who enjoy working individually or in teams and are moved by the spirit of the organisers come together and have fun.

The Research to Impact Hackathon is different in significant ways to a standard hackathon. Firstly, there is often criticism that these events produce a lot of interesting but unfinished code, which is either taken over by the sponsor and developed internally or simply abandoned, with the developers un-engaged in the follow up. The sponsors of this event, IDS/ELDIS and CABI/R4D see this event as Phase One in a longer term process. They are providing small prizes for the best products but committing larger sums to supporting the development of particularly promising ideas and prototypes that have the potential to increase the use of research data.

Secondly, we wanted to provide focus to the developers based on an informed understanding of specific challenges faced on the ground, in East Africa, by those working in agriculture and nutrition, challenges which constrain the use of development data and opportunities it offers to enrich the development process. However, we had to steer carefully between being too directive of the developers - which could reduce creative and risk appearing to be asking for some free labour to help large organisations solve their problems - and not providing a clear enough set of scenarios.

So we were a bit anxious about how Day Two of the Hackathon would develop, especially since we were joined by some new developers who hadn't had the introduction to the personas, challenges and triggers which emerged from Day One of the Hackathon nor been part of the Ideation session. We should have known better: we are in the iHub, in Nairobi, Kenya, at the centre of a vibrant developer community, supported by the ideas and contacts of iHub Research. Many of the participants had been trained in mobile application development at the mLab - yet another source of energy within the iHub ecosystem (and the iHub is not even three years old!). And all the developers were in some way or another connected or developing software solutions to the needs of those in the agriculture value chain.

We introduced the data available from ELDIS, R4D and other relevant open data sources, including the World Bank's data site and the rapidly growing Kenyan Government OpenData portal; the ways to access the data through the ELDIS open API and the tools which Tim Davies is developing to access the data, including in Linked Data formats. Finally we introduced the personas from Day One, together with the ideas which had been rated as having the highest potential impact and most viable as the basis for developing a Proof of Concept in only two days (and nights!).

Chaos of the most productive kind ensued. People discussed ideas; formed, and reformed, teams; ate sausages; asked for more information about the personas; drank coffee; got support in exploring the data and learning to use the access tools available; fed-back ideas for discussion; storyboarded and planned; ate cake; began to hack. By the end of the day four groupings of ideas and people had emerged, all interesting and within the frameworks we had established, and some with the beginnings of demonstration code - either created or imported. Then we went for beer.

Day Three is a hack-day: teams will continue working on their ideas, preparing for a presentation on the morning of the fourth day, in some kind of Dragon's Den format. While the progress has been remarkable for two days, the acid test is, of course, what the teams can present on Day Four. Given their commitment to the longer term, the organisers are looking as much for coherent plans and realistic assumptions as finished code - but watch this space.

Research to Impact Hackathon with iHub Research, Nairobi

Open data on the web makes it possible to take information on research from many sources, and to generate ‘mash-ups’ that make it available in different places, on different platforms, and in ways that support action and impact. Open data can be remixed to answer key questions in ways that were not possible before.

One of the most interesting developments in the R4D project, which we have been supporting with CommsConsult and CABI, has been converting the metadata in the R4D database of DfID funded research to Open and Linked Data formats. The Institute for Development Studies (IDS) ELDIS team have been travelling in the same direction - working to open up access to their research information including by creating open APIs allowing anyone to tap into their 15+ years of curated development research. The rationale for this is that every year institutions, researchers and practitioners generate thousands of datasets, reports and articles about development issues. To give some idea of scale, DfID funds £200 million worth of research every year. Yet, much of this knowledge remains underused, locked away in online repositories such as R4D and ELDIS.

Presenting personas at the Research to Impact Hackathon

We tested this, perhaps a little unfairly, by asking the participants during the first day of the Hackathon we're working on this week in Nairobi, most of whom were subject experts we'd invited to provide context and scenarios for the developers to get their teeth into, how much they used either R4D or ELDIS data. About half had accessed the sites, very few accessed them more than once or twice a year. Yet these were researchers, information scientists and knowledge workers with intermediary NGOs like ALIN, all prime targets from the materials.

"Hackathons" (also known as a hackfest or hack day) are events in which computer programmers join forces with a number of other experts, such as designers, investors, project managers, and spend a short intense period together to develop technical ideas and solutions. The Research to Impact hackathon is focusing on the research data from R4D, ELDIS and other relevant sources - including those from Kenya such as KAINET - relating to agriculture and nutrition. We brought together subject matter experts with technical developers to explore and create innovative prototypes to increase the use and impact of research in development. The hackathon is being at the Nairobi iHub by iHub Research, a new programme within this open innovation space.

The first day focused on generating scenarios - use cases - for the developers to work on. We started by asking participants to identify some of the reasons that research data isn't accessed or used. The group then selected seven typical 'user types' who represent key potential audiences for the data. These personas included extension workers, researchers and knowledge workers - key intermediary roles for re-purposing data and linking with primary players in the agricultural value chain such as farmers, input suppliers and market intermediaries. The group also prioritised fleshing out the role of policy actors, key to addressing the whole range of issues which impact those working directly in agriculture. Working in groups these types were profiled and linked to the challenges previously identified. After rapid peer review specific 'triggers' were identified for each of the personas, things which might motivate them to change their behaviour in relation to the data. The personas will be shared in the EuforicWeb wiki as the Hackathon develops.

Evaluating ideas at the Research to Impact Hackathon

A group of developers joined in the afternoon. They were presented with the personas and had time to interrogate the subject specialists. We finished with an ideation session, when all participants were given 10 minutes to come up with at least 10 suggestions for technical developments - mobile or pad apps, web widgets or small pieces of linking or bridging code. Those ideas were located on a matrix representing high/low impact, high/low viability - in terms of being able to develop a proof of concept in the succeeding two days. There were an extraordinary number and range of ideas, both creative and very applied. The ideas which were voted as high/high will be taken into the hackdays to help kick-start the process.