technology for development workshops · software basics 37 vivek veeramani thoughtworks • there...
TRANSCRIPT
Technology for Development Workshops
An opportunity for ESARO staff to share and learn from each other.
Synthesis
Wednesday, 30 October 13
2
Wednesday, 30 October 13
© 2013
Day 1
Setting context and sharing experiencesUnderstanding the challenges that arise from trying to integrate technology in programmes
3
Wednesday, 30 October 13
© 2013 4
Wednesday, 30 October 13
© 2013
Introduction:
Regional Update
5
Karim GhalainiESARO
• Project management is critical to success.
• Programme must be in the driver’s seat.
• ESARO objectives:• Assist COs• Strengthen capacity• Maximise potential
Wednesday, 30 October 13
© 2013
Case Study:
eNutrition
6
Hawi BedasaTanzania CO
• Developed an Android application using OpenMRS, piloted in 6 municipalities
• Project had relevancy, but government wasn’t on board
• Take-away: need to involve technologists from the beginning and do an evaluation to know when to stop a project or scale
Wednesday, 30 October 13
© 2013
Case Study:
Learning from failure
7
Stuart OcampoSouth Sudan CO
• Connecting Classrooms: an education program in Madagascar to get equipment in the hands of students
• Insufficient field testing before deployment, supply woes
• Take-away: project failed because of a failure to field test. But cost of failure shouldn’t stop us from trying to innovate.
Wednesday, 30 October 13
© 2013 8
Wednesday, 30 October 13
© 2013
Case Study:
LLIN Distribution
9
Vivek VeeramaniThoughtWorks
• LLIN: goal was to monitor the distribution of bednets in Uganda
• A successful delivery from ICT did not mean that the programme was implemented.
• Take-away: Focus on impact over output. External factors can waylay even the best projects.
Wednesday, 30 October 13
© 2013
Activity:
Anchors & Engines
10
David Peter SimonThoughtWorks
• Engines: • leadership• partnership• ownership & vision• funding• communication• project management
• Anchors: • Bureaucracy • Lack of clear roles & responsibilities• Knowledge management (e.g. consultants)• Risk aversion
Wednesday, 30 October 13
© 2013 11
Wednesday, 30 October 13
© 2013 12
Wednesday, 30 October 13
© 2013
Case Study:
Exploring and Prototyping for T4D
13
Felicia TakavarashaZimbabwe CO
• Programme (Essential Medicine Tracking in Zimbabwe) used user acceptability testing and surveys to discover which devices people are more comfortable with.
• Real time data collection: who is responsible for collecting?
• Take-away: We need to be asking what data people want to see/use beforehand.
Wednesday, 30 October 13
© 2013
Case Study:
Scaling T4D projects
14
Landry TsagueZambia CO
• Project Mwana: goal was to reduce turn around time on EID
• Challenging relationship with telecoms, meeting recurrent cost of programme at scale to ensure business continuity
• Take-away: government ownership from pilot phase was key to scaling success
Wednesday, 30 October 13
© 2013 15
Wednesday, 30 October 13
© 2013
Case Study:
Adapting initiatives from other COs
16
Priscilla Chomba-KinywaZambia CO
• Zambia wanted new tool for HIV prevention, adapted Ureport for their needs
• Hired a local developer, worked on developing local capacity
• Take-away: analysis of unstructured texts can be challenging, sometimes we need to involve others, e.g. train counsellors
Wednesday, 30 October 13
© 2013
Talk:
UNICEF Global Overview
17
Chris FabianGlobal Innovations
• Open source collaboration worldwide, technology is attached to human systems.
• Innovation funding is available for COs - assessment after pilot phase.
• Key question: How does one project build capacity in the government, service providers and the programming community for other projects in the future?
Wednesday, 30 October 13
© 2013 18
Wednesday, 30 October 13
© 2013
Day 2
Opportunities for integrating T4D in programmesTalking about the bigger picture of how things fit together.
19
Wednesday, 30 October 13
© 2013 20
Wednesday, 30 October 13
© 2013
Introduction:
T4D: Getting Started
21
Karim GhalainiESARO
• Some tasks can be done internally, some must be outsourced.
• There are pros and cons for different organisational structures for T4D (e.g. task forces vs. coordinators)
• Take-away: must consider models based on the context of your office.
Wednesday, 30 October 13
© 2013
Talk:
Getting to Common Awareness for Data Collection
22
Matt BergTechnologist, Africa Geek
• We need common forms, common indicators, common places to get common data.
• Interoperability and keeping data “open” can be key for working with partners and governments
• Take-away: Feedback loops are essential. Results should get shared with frontline workers.
Wednesday, 30 October 13
© 2013 23
We need to think about the process. What data we want to collect? How do we
want to use that data?
Matt Berg
Wednesday, 30 October 13
© 2013
Talk:
Opportunities and Trends in ICT4D
24
Gautam Shahaccenture
• Understanding the projected trends in technology is key for sustainability.
• Is technology driven by culture/trends or is it possible to have ICT4D influence the market?
• Take-away: accenture believes UNICEF should focus first on programmes because technology can be handled externally.
Wednesday, 30 October 13
© 2013 25
Wednesday, 30 October 13
© 2013
Activity:
How might we ...?
26
David Peter SimonThoughtWorks
• Key themes that emerged:• need to raise awareness• enhance information sharing• increase buy-in• make evidence-based decisions• integrate cross-sectoral
• “We know what we need to make projects more successful, but collaborating and sharing is essential.”
Wednesday, 30 October 13
© 2013 27
Wednesday, 30 October 13
© 2013 28
Wednesday, 30 October 13
© 2013
Case Study:
Level 3 Monitoring in Kenya
29
Andrew CunninghamKenya CO
• Level 3 monitoring helped identify new opportunities for UNICEF programming (emergency, response, advocacy, etc.)
• Programme delivered important feedback to beneficiaries
• Take-away: SMS allowed for better reach for M&E
Wednesday, 30 October 13
© 2013
Case Study:
Youth Engagement in South Africa
30
Gerrit MaritzSouth Africa CO
• Programme worked with a well-established partner to allow for excellent access to the targeted beneficiaries
• Education outcomes were positively impacted.
• Take-away: partners can help success without many of the usual challenges to uptake tech.
Wednesday, 30 October 13
© 2013 31
Wednesday, 30 October 13
© 2013
Day 3
Working with External Partners and Vendors The basic roles and techniques used in software development
32
Wednesday, 30 October 13
© 2013 33
Wednesday, 30 October 13
© 2013
Talk:
Business-Driven Technology Solutions
34
Gautam Shahaccenture
• We often overestimate what can happen in the short term & underestimate what can happen in long term.
• Technology is going to happen, we can’t control or shape the market.
• Take-away: we need to concentrate on our business (programs) first, maybe let other people handle the tech solution.
Wednesday, 30 October 13
© 2013
Talk:
Business Analysis 101
35
Liz Cruickshankaccenture
• Requirements need to be accurate. It’s about what it needs to do, not how.
• Avoid too many requirements in one and perhaps even include a glossary to help agree on language.
• Take-away: some of these activities happen in parallel with other business practices, need to integrate the two.
Wednesday, 30 October 13
© 2013 36
One of the things we do in analysis is having structure to terminology. Everyone
needs to be able to interpret our requirements.
Liz Cruickshank
Wednesday, 30 October 13
© 2013
Talk:
Software basics
37
Vivek VeeramaniThoughtWorks
• There are many different models when it comes to software development. Get to know your vendor’s model.
• Agile recognises that communication and iteration is key to successful delivery.
• Take-away: focus on the Minimum Viable Product (“MVP”).
Wednesday, 30 October 13
© 2013
Activity:
Pros & Cons
38
David Peter SimonThoughtWorks
• Private sector has technical skills, but can be too expensive.
• Academia is not always local, but can be cheaper.
• NGOs helpful for ground info, but sometimes have their own agenda.
• Individual consultants can assist with office work, but continuity is not there.
Wednesday, 30 October 13
© 2013 39
Wednesday, 30 October 13
© 2013 40
Wednesday, 30 October 13
© 2013
Talk:
Vendor, partners, technology choices
41
Karim GhalainiESARO
• Work packages include business analysis, project management, design/coding/technical delivery, maintenance and training
• Engaging with a third party at UNICEF may mean working with PCAs/SSFAs, SSAs, LTAs, MoUs
• Take-away: tools and technology choice must be based on context
Wednesday, 30 October 13
© 2013
Case Study:
Contracting for Tech4Dev
42
Robert JohnsonESARO
• Contracted with DevInfo for nutrition monitoring data, cost and time overruns.
• The problem statement was critical.
• Take-away: get to know your vendors. Get high level support from superiors.
Wednesday, 30 October 13
© 2013
Case Study:
On working with consultants
43
Simon MwirigiMalawi CO
• Consultant evaluation of UNICEF - deliverables were not understood and not feasible.
• Consultants want to move fast, sometimes making commitment without consulting UNICEF
• Take-away: spend time in the beginning help the consultant to understand processes and rules/regulations
Wednesday, 30 October 13
© 2013
Case Study:
Tips working with vendors
44
B.P. PanwarUganda CO
• Development of survey tool by using the Agile approach
• Key message is importance of connectivity.
• Take-away: be careful of contracts, one vendor resold their code to another country office
Wednesday, 30 October 13
© 2013
Case Study:
Cloud version of Ureport
45
Issmail NnafieUganda CO
• Ureport is a free SMS-based system that allows for citizen engagement
• No need for hosting locally, connectivity and electricity become non-issues.
• Take-away: cloud deployment time moves delivery from months to weeks
Wednesday, 30 October 13
© 2013 46
Wednesday, 30 October 13
© 2013
Day 4
Alternative solutionsWidening our horizons through case studies and feedback
47
Wednesday, 30 October 13
© 2013 48
Wednesday, 30 October 13
© 2013
Case Study:
Solar Innovations
49
Chelsey LapageBurundi CO
• Mandate as the ICT4D unit was nutrition choices based on energy costs.
• Focused on off-grid energy solutions, so as to figure out how to entice people to invest in energy in a place like Burundi
• Take-away: develop business models quickly, test in the field
Wednesday, 30 October 13
© 2013
Case Study:
GIS for Emergency Response
50
Minu LimbuKenya CO
• GIS used to monitor deprivation areas
• Sharing data across sections really helped. Need to have some sort of idea about the spatial information you would like.
• Take-away: need to have the right set of data/indicators first.
Wednesday, 30 October 13
© 2013
Talk & Activity:
Intro to Human-Centred Design
51
Kagonya AworiiHub UX Lab
• Human-centred design (HCD) is an approach to design that grounds the process in information about the people who will use it.
• There are many different ways of approaching it. One model is Hear > Create > Deliver
• Take-away: HCD is not a step in the process or the role of one person.
Wednesday, 30 October 13
© 2013 52
Wednesday, 30 October 13
© 2013 53
Wednesday, 30 October 13
© 2013 54
UX best practices promote improving the quality of user’s
interactions along with enhancing the perceptions of your product or any related
service.
Kagonya Awori
Wednesday, 30 October 13
© 2013 55
Wednesday, 30 October 13
© 2013
Appendix
Resources & links mentionedIn case you want to learn further
56
Wednesday, 30 October 13
© 2013
Technology for Development (T4D): An emerging field indicating areas where technology is used to support humanitarian operations & development programmes.
Cloud computing: Network-based services which appear to be provided by real server hardware (like in your office), which in fact are served up by virtual hardware. In layman’s terms it lets you use files and applications over the Internet rather than hosting them locally. Most common example would be gmail.
USSD: A global feature on cellular phones for interacting with the users. Most common example is topping up your feature phone using a *nnn# and then you follow the menu options.
Open data: Open data is the idea that certain data should be freely available to everyone to use and republish as they wish, without restrictions from copyright,
GIS: A geographic information system - something designed to capture, store, manipulate, analyse, manage, and present all types of geographical data.
User Experience: The behaviours, attitudes, and emotions about using a particular product, system or service.
Agile: A software development mindset that encourages adaptive planning and less up-front requirement defining.
Waterfall: A software design and development process in which progress is seen as flowing steadily downwards, with lots of planning up-front and design/delivery afterwards.
Definitions
57
Wednesday, 30 October 13
© 2013
“Why is it so hard to try something new in ICT4D?”http://www.youtube.com/watch?v=hIRkipQ7nPw
Nokia’s momaths program in South Africa: http://www.youtube.com/watch?v=PQSu6tlxNkA
Videos
58
“Worst Practices in ICT in Education” http://blogs.worldbank.org/edutech/worst-practice
Child Friendly Technology Frameworkhttp://unicefstories.org/2013/08/06/child-friendly-technology-framework/
Blog posts
Wednesday, 30 October 13
© 2013
Mobile data collection:http://formhub.org/
Interactive SMS application:http://textit.in/
Innovative smartphone hardware:http://www.phonebloks.com/
Free framework for human-centred design:http://www.hcdconnect.org
TechChange.org Online Courseshttp://techchange.org/
d.School 90 Minute Design Thinking Crash Coursehttp://dschool.stanford.edu/dgift/
mHealth Alliance:http://www.mhealthalliance.org/
Interesting links
59
Wednesday, 30 October 13
© 2013
Day 1: https://www.dropbox.com/sh/bzkpwlu2u4dtrnn/aUbUnXh91x
Day 2: https://www.dropbox.com/sh/xxhks6wl17nyg7s/kUOhX4OArH
Day 3:https://www.dropbox.com/sh/cmy7lbm1gwjop2h/qd8gyaDSm8
Day 4:https://www.dropbox.com/sh/ua4n2zm3s7dyiac/gTIKzUkOr6
Dropbox Folders
60
Wednesday, 30 October 13
© 2013
Workshop coordinators
61
Jessica TribbeESAR T4D [email protected]
Georgia HillESAR T4D [email protected]
Karim GhalainiRegional [email protected]
Marietta Muwanga-SsevumeESAR Regional Chief of [email protected]
Wednesday, 30 October 13
Thank you!
We appreciate your participation.
Please share this document with your CO colleagues so as to keep the conversation going. Any further feedback can be sent to the ESARO workshop coordinators.
62
Wednesday, 30 October 13