Why it is Hard to Identify Technical Research Problems in ICT4D and How to Make it Easier

My position is that a shortage of detailed and compelling problem statements is the primary bottleneck that prevents most computer scientists from conducting research in ICT4D. While interesting problems exist, they are usually discovered via months of fieldwork, and there is little incentive to formalize and disseminate problems for the benefit of other researchers. To address this bottleneck, I argue that we should create a prestigious venue for publishing problem descriptions, rather than problem solutions. I also propose that we establish problem-exchange websites to solicit problems from practitioners; organize structured design contests that aggregate knowledge in a problem area; and leverage the domain knowledge of funding agencies in defining technical research problems.

thies-ccc09.pdf
PDF file

In  CCC Workshop on Computer Science and Global Development

Details

TypeInproceedings
> Publications > Why it is Hard to Identify Technical Research Problems in ICT4D and How to Make it Easier