FMS Innovation Lab Seminar 8th January 2013

Accelerating Development through Innovation:A Snapshot from University of Khartoum

Seminar by Innovation Lab Pilot Project at Faculty of Mathematical Sciences

8th January 2013

Khartoum University Innovation Lab Pilot Project Seminar 2

“Traditional development thinking has held that attempts to reach the very poorest, especially in remote areas, are too costly and too difficult. But

new technology and innovations are making it easier to reach the most deprived ... Focusing on the most disadvantaged is right in principle and right in

practice.”

Anthony Lake, UNICEF Executive Director

08/01/2013

3

An Innovation Lab: A Technology for Development Approach

• National facility set up by UNICEF to support to support the work of UNICEF and governments by building local technological capacities for humanitarian development

• Defined as “... a space and set of protocols for engaging young people, technologists, private sector, and civil society in problem-solving.”

08/01/2013

COLLABORATIVE SPACE

Khartoum University Innovation Lab Pilot Project Seminar

Source: Innovation Labs - A Do-it-yourself Guide - Version 1. Oct. 2012

4

Different Projects ... Different Lab Models

08/01/2013 Khartoum University Innovation Lab Pilot Project SeminarSource: Innovation Labs - A Do-it-yourself Guide - Version 1. Oct. 2012

5

Which Innovation Lab model?

Lab Models

1. Innovation Lab Kosovo

2. Uganda Innovation Lab

3. CCORE Zimbabwe Lab

4. Copenhagen Innovation Lab

5. IHUB Malagasy and UNICEF

Projects

08/01/2013

1. Outreach/Training

2. Product Development

3. Service Development

4. Operational Research

5. Broadcasting Content

FMS Lab is located in University


6

Innovation Lab Pilot Project in Sudan

Information Flow For Project Management Information Flow for Innovation Development

Consultant

Sudan University for Science & Technology

University ofKhartoum

Requirements

RapidSMSRapidSMS

School Kits Vaccination

Requirements

Khartoum University Innovation Lab Pilot Project Seminar08/01/2013

7

Innovation Lab Pilot Project in Sudan

September 2012

October November December January2013

February

WorkingGroups

ProjectTeam

CampusCoordinators

CampusCoordinators

RapidSMS

Tech4Dev

SCRUM

SCRUM Master

Development Team

Requirement Engineer

Social Media

Knowledge M

anager

March

08/01/2013 Khartoum University Innovation Lab Pilot Project Seminar

8

Innovation Lab

08/01/2013

Campus Coordinator

Knowledge Coach

Social Media

Coordinator

Development Team Leader

Requirements Engineer

Coordinator

SCRUM Master

Design Leader

Quality Assurer

Test Leader

Coding Leader

Assistant Assistant Assistant Assistant

@FMS



9

Campus Coordinator

• Safa Mohamed Ahmed – Campus Coordinator (Oct. – End)– SCRUM Working Group (Oct.); SCRUM Team (Nov.)

08/01/2013Khartoum University Innovation Lab Pilot Project Seminar9

08/01/2013


10

Requirements TeamTibyan Hussien

– Related Work Group (Oct.); Req. Team Leader (Nov. & Dec.);– Development Team Support (Jan.)

Riham Abdelraheem - Related Work Group (Oct.); Req. Team Member (Nov. & Dec.);

K.management Team member (Jan.)

Eshtiag TarigRelated Work Group (Oct.); Req. Team Member (Nov) Social media support (Dec & Jan).


08/01/2013


11

Scrum Team

• Abdelgader AbdallahSCRUM Working Group (Oct.); Scrum Master (Nov. – end).

• Amani Mahdi Scrum Master Assistant (Nov. – end).

08/01/201311Khartoum University Innovation Lab Pilot Project Seminar

08/01/2013


12

Development Team

Twassul Alrasheed–RapidSMS Group (Oct.); –Dev. Team Leader (Oct. – end); –Coding Team Member (Dec & Jan) .

Dev Team Divided to:.


08/01/2013


13

Coding Team:

Amro Hassan - Coding Team Leader(Nov. – end).

Mohammed Hassan: -Coding Team Member (Nov. - end).

Rania Omer: - RapidSMS Group (Oct.); Coding Team Member (Nov. - end).

08/01/2013


14

Tasneem SalahRapidSMS Group (Oct.); Coding Team Member (Nov. - end).

Shima MohammedRapidSMS Group (Oct.); Coding Team Member (Nov. - end).

Yosra HusianRapidSMS Group (Oct.); Coding Team Member (Nov. - end).

08/01/2013


Hind ElnigoumiRapidSMS Group (Oct.); Design Team Leader(Nov.-Dec.); Coding Team Member(Jan.).

Salma AlsirRapidSMS Group (Oct.); Design Team Member(Nov.-Dec.); Coding Team Member(Jan.)

Esraa AliRapidSMS Group (Oct.); Design Team Member(Nov.-Dec.); Coding Team Member(Jan.)

Design Team:

08/01/2013


Testing Team:

Khalid Mohammed

- Testing Team Leader (Nov.- end).

Ahamed Ali

- Testing Team Leader (Nov.- end).

Hiba SalahRapidSMS Group (Oct.); Testing Team Leader (Nov.- end).

08/01/2013


Quality Assurance:

08/01/201317Khartoum University Innovation Lab Pilot Project Seminar

Shaza MohammedRapidSMS Group (Oct.); Quality Assurance Team Leader

(Dec. & Jan.).

Isbah Eltigani:

RapidSMS Group (Oct.); Quality Assurance Team Member(Dec. & Jan.).

08/01/2013


18

Team’s Knowledge Management

Abdelkareem Omer (Knowledge Coach) SCRUM Working Group (Oct.); Knowledge Coach ( Nov. – end).

Alaa AbdelazeemRelated Work Group (Oct.); Req. Team Leader Assistant (Nov. & Dec.); K.management Team Support(Jan.)


08/01/2013


19

Team’s Social Media & Activities

Haifaa Abdelazeez (Coordinator)

RapidSMS Group (Oct.); Social Team Coordinator

( Nov. – end)

Iman Ibrahim Social Team Member(Dec. Jan.).

Mawda SaudRapidSMS Group (Oct.); Support Team(Nov- end).


08/01/2013

20

System Requirements


21

The School Kit Distribution Monitoring System

• This system is a collaboration between UNICEF Sudan CO and Ministry of General Education to monitor the distribution and use of the four types of school kits supplied to the school system in Sudan.

• Distribution monitoring will involve:– Time– Quality– Use


22

Scope of System

08/01/2013

UNICEF KhartoumWarehouse

Supplier

School

Children

MoE/UNICEFField Warehouse

Procurement

Utilisation

Dist

ributi

on


23

System Functions

1. Monitor supplies through SMS based service.a) Calculate the duration of time it takes kits to reach the school.b) Assess the general quality (using a scale defined by UNICEF to assess

the condition of supply boxes) of kits when they reach delivery points in the distribution chain.

2. Generate reports about the supplies quality and quantity.

3. Send mass messages to survey children use of school kits to a defined set of receivers; established by UNICEF and MoE.

4. Query the existing database via a web-based interface.


24

System UsersUNICEF • Education Officer: UNICEF staff in Khartoum responsible for school kit

distribution program.• Khartoum Warehouse Assistant: Receive order information from

UNICEF Education Officer.

• Field Store Keeper: UNICEF staff at field warehouse in States.

Ministry of Education• Education Officer (State & Locality): MoE staff responsible for

government education services at Locality level.

• School Headmaster: is responsible for receiving equipment delivered at his/her school.


25

How the system works?

08/01/2013

UNICEF & Government Partners

SchoolHeadmaster

- UNICEF/MoE Officers- Warehouse Officers

The Central System sends feedback to message sender

Aggregated data is published to secure website and periodically sent t key stakeholders

System users send on kits dispatch/release data and receipt

at school


26

Software Project Management using SCRUM



Brief Description of System

• SMS Based monitoring System:– SMS server (receive, send)– 2 kinds of SMSs (informative , Alert )– 4 sources of SMSs (UNICEF Khartoum Warehouse

Assistant, Ministry of Education, Localities, Schools )

– Reporting Mechanism

08/01/2013

28

Classification of System’s SMSes

08/01/2013

SMS

Informative

Release

W-H MoE Locality

Receive

W-H MoE Locality School

Alert


29

Project Phases

08/01/2013

•receiving SMSs "by dev. team“ Done

•sending SMSs "by dev. team“ Done

•language issue "by dev. team“ Canceled

•determine the SMSs formats "by design. team“ DONE

•design the DB architecture "by design. team“ DONE

•The Outcome : Demo of SMS server

1. Basic functionalities & DB architecture

1st sprintDur : 14 days DONE

•implementing the DB design

•Determine SMSs kind

•Determine the SMSs sources

•filling up the DB "collaborative work dev. & design"

•The Outcome : full integrated DB & SMS server

2. Building the DB & SMSs classification

2nd sprintDur : 19 days GOING

•Remainder SMSs

•Web design

•By SMSs•By web

solution "collaborative work dev. & design"

•The Outcome : clear & informative Reporting mechanism

3. Feedback & Reporting mechanism3rd sprint

Dur : 13 PLANNED



30

Second Phase Plan

08/01/2013

SPRINT 2 TASKS TEAM DURATION RELEASE DATE

From : 23/12/2012

Triggers PRO.TEAM 8 30/12/2012

To : 10/1/2013

DB IMP PRO.TEAM 12 3/1/2013

Duration : 19 Days

Reports Design DES.TEAM 5 27/12/2012

Web site Design

DES.TEAM 9 6/1/2013

Triggers & DB integration

PRO.TEAM 4 8/1/2013


Third Phase Plan

1. 2nd Sprint Review Meeting– Provide final feedback about the current sprint release– Prepare for the next sprint

2. 3rd Sprint Planning Meeting– Present tasks must be implemented– Schedule sprint tasks and time– Divide tasks between team members– Produce sprint backlog

08/01/2013


Software Development Work

• Starting …

• Team Description

• Where are we?

08/01/2013


System Design

08/01/2013

08/01/2013 Khartoum University Innovation Lab Pilot Project Seminar 34

Use case diagrams


Client SideServer Side

Mobile communication

network

Application server

Database

Laptop/Desktop

Component Diagram

Low / High end Mobile phone


GSM modem

Rapid SMS Framework

My SQL

Web service

Informative SMS

Saving

Querying database

Replying the query

Query process

Deployment Diagram

Server Side

-Warehouse assistant - State- Locality- School head master


Client Side

Interface DesignLogin screen :

Main screen :

Username

Password

Login

Monitor supplies

Calculate Duration

cancel


Monitor Supplies

Search by location

Search all location

Delivered locations

Non Delivered locations

school locality stateschool locality state

: Location

warehouse,State,locality,school

search cancel

Main screen/ Monitor Supplies Button :


In case the entrance is a State:

By Choosing A1 locality; new window appears display all the schools under the locality A1 in table.

locality State Locality A1 State A

Locality A2

Locality B1 State B

Locality B2

status schools locality

Delivered A11 A1

Not Delivered A12

Time1 Types Quality Quantity school

A11

Main screen/ Calculate Duration Button :

When The UNICEF/ MoE officer press this functionality; new window appears showing the time the supplies take to received schools as shown in the below table.

Duration school Locality State

9 days A11 A1 A

5 days A12

6 days A21 A2

20 days A22

3 days B12 B1 B

Calculate Duration



Coding

08/01/2013

43

RapidSMS Architecture



RapidSMS Configuration

• Operating System (Ubuntu).

• Install Django framework.

• Install RAPIDSMS Packages.

• Install Database System.

08/01/2013


Configure Backbend

• Why GSM modem?

• Installing and configuring PYGSM.

• Testing PYGSM.

08/01/2013


Understand RapidSMS File Structure

project

apps App.pyModels.py

Urls.pyViews.pyAdmin.py

Manage.py

Urls.py

Settings.py

static

Css,js,img

templates HTML

08/01/2013


RapidSMS Apps

• SMS Configuration

• Query

08/01/2013


Demo

08/01/2013

0929618420


Support Members

• Dealing with problems or errors

• Search for the problem and the solution

• Implementing the solution with coding team

Experience (last problem)

• From error message: NO MODULE installed>> pygsm.py file

• Download mox and unittest packages

08/01/2013


Outside support

• Local support

• International support– Mailing list (google group)– IRC channel (#rapidsms)

08/01/2013


Software Testing

08/01/2013

Software testing

Software testing def. Software testing methodologies:

white box testing. Unit testing. Integration testing.

black box testing.

black box testing:◌Usability testing.◌Functional testing.◌Security testing.◌Performance.

Software testing activities:

Learning the product.Execute test case.Write bugs reports.


Test plan

Test Plan

Test IDTest environment

Roles and responsibilities

Schedule

Brief Introduction

Features to be tested

Features not to be tested

Test approach

Entry/Exit criteria

Test item

08/01/2013


Test Case

08/01/2013


Characteristics of a good test case

Test case

Simple

Updated Testability

Exact

08/01/2013


Quality Assurance

08/01/2013


Software Quality Assurance

• Used to Monitor and Improve the Software Development Process

• Making Sure That Standards and Procedures are Followed

• Ensures that Problems are Found and Dealt with

• Formal Technical Reviews

08/01/2013


What will be quality assured?

• Software Design process

• Software coding process

• Software testing process

• School Kit Monitoring System Non-functional requirements

– Interface

– Maintainability

– Inter-operability

– Security

08/01/2013

Management

Name Role Responsibilities

Shaza Mohamed Preparing standards for every stage

Before every stage(e.g. design) standards will be given to the Certain team

Iman Ibrahim

Isbah Eltigani Auditing work products After every work product is finished auditing will be done by the QA team

Eshtiag Tarig


Reviews and Auditing • Standards Used:

– IEEE Guide to Software Design Descriptions

– IEEE Testing Standards

• Software Design Description ( SDD):

– UML Diagrams.

– Database tables Design.

– Web interface Design.

– SDD Document.

08/01/2013


63

Management of Innovation Lab’s Knowledge

08/01/2013


The Beginning …• The UNICEF project and the new knowledge area’s• The first step we did was the pre-questionnaire so we can

assess the learning of our team• The questionnaire results show that it is completely new

concepts, tools and platforms as we will see in the following graph

• Our second step is a data collection from different teams, we collect all generated manuals, presentations, and even source files we used

• we use Dropbox to make the presentations and manuals be accessible to all as a knowledge sharing value

• Following are the questionnaire results:

08/01/2013

Questionnaire results

tec4dev scrum ubuntu python0

1

2

3

4

5

6

7

8

9

10

goodfairlittlevery littlenill

Way forward

• We intend to build our Lessons learned system and skills database.

• In term of this we chose our lessons learned template and we design our Excel sheet for the skills.

• Following is the lessons learned life-cycle and a snapshot for the lessons learned template that we will use.


Lessons learned lifecycle

08/01/2013


Snapshot from the lessons learned template

08/01/2013

Low end , Smart phone

RapidSMS : Mobile Side


Smart phone: Rapid Android

• Rapid Android is a supply chain management and data collection tool built on Android, the open source phone operating system.

• a phone can now be used not only as a data entry tool but a data aggregation platform.

• in addition to using phone as an SMS client, allowing users in the field to enter data, to create surveys, and rapidly analyze data in the field.

• Rapid Android is a complete two-way SMS solutions that unlike other tools on the market, allows for analysis and processing on the actual phone.

08/01/2013


Advantages of Rapid Android include:

• Price – Rapid Android is a free platform available on any Android Phone which runs around $300, and getting cheaper. Android on netbooks makes this even more exciting.

• Power – a phone requires much less power than a laptop, for example, can be charged from 12V, and has a built in UPS (battery).

• Technical Expertise – Rapid Android phones can be easily deployed with field staff minimizing the need for a technical person on the deployment side.

• Data entry – Android is an ideal data entry device with touch screen, keyboard, and form based error corrections.

08/01/2013

http://venturebeat.com/2009/01/01/android-netbooks-on-their-way-likely-by-2010/

http://venturebeat.com/2009/01/01/android-netbooks-on-their-way-likely-by-2010/


Low end phone• Mobile Active group .. Suitable for Nokia

Malnutrition reporting .. Jokko initiative.

08/01/2013


Advantages of Using Low end phone

Low cost

Large coverage of people

Easy interface and user friendly

08/01/2013

74

Innovation Lab’s Social Media & Activities



Social Media outputs

• Innovation Lab logo design• Innovation Lab facebook page• Meeting Sudan university Social Media team• Interviewing all members of the Innovation Lab

team• Producing two videos• Organized two social activities at one day

(breakfast meal at a restaurant and horse riding)

08/01/2013

Khartoum University Innovation Lab Pilot Project Seminar 7608/01/2013


Social Media Future plan

• Start tweeting.• Organizing more team social activities.• Working with UNICEF’s communication

section.• Contacting the conventional media.• Advertising campaign for the final event.• Working on a magazine to be distributed

online.

08/01/2013


How Social Media affects the Innovation Lab?

• Publicize the innovation lab activities and events.

• Help the KM team in gathering knowledge from the different teams.

• Strengthening the relationship between the innovation lab teams by organizing social activities.

08/01/2013


How is the pilot going?

08/01/2013

Weaknesses Strengths

Team Work • variable commitment• un/employment distractions

• self motivation• attachment to FMS

Capacity Building

• insufficient support• lack of lab infrastructure

• self/group learning• team flexibility

Software Development

• new tools• limited support network

• new tools• resilient members

Engagement with/by Stakeholders

• inadequate communication• new partnership model

• space/funding/new contacts• new partnership model


80

Benefits an Innovation Lab can bring to:

University1. Capacity building:

– Employment/entrepreneurship potential

– Application of concepts taught

2. Multidisciplinary and open access thinking

3. Real challenges and societal impact opportunity

4. Publicity and partnerships

5. Innovation structure and socially-relevant curricula

08/01/2013

UNICEF1. Prototype solution

for two priorities

2. Spread of Tech4Dev concepts

3. Documentation:‒ Pilot lessons‒ RapidSMS

application

4. Publicity and partnerships

5. Innovation structure / sustainability

Community1. Local capacity

development

2. Local responses to pressing needs

3. Collaboration space for different partners

4. Tuned partners to development problems

5. Cheaper solutions


What it takes?

• Creating a Lab is not easy ... It requires:– Steady Leadership– Stakeholders Support– Flexibility

• It can however:– Accelerate Innovation for Development– Utilise creativity and energy of young people– Create new partnerships– Adapt solutions across communities and countries

08/01/2013

FMS


Thank you

5 Jan. 2013