Nodumo Dhlamini, Agnes Akwang Obua-Ogwal, Claire Akun-Ntwali, Sylvia Mkandawire, George Flatters

1. Developing a web-based information management system A Foundation for realizing the RUFORUM Theory of Change Nodumo Dhlamini, Agnes Akwang Obua-Ogwal, Claire Akun-Ntwali, Sylvia Mkandawire, George Flatters The Regional Universities Forum for Capacity Building in Agriculture (RUFORUM – www.ruforum.org) 7th AFREA Conference 5-7 March 2014 Yaounde, Cameroon

2. Outline / Objectives • Overview of the RUFORUM Theory of Change • The Approach and Methodology for developing the RUFORUM Information Management System • Achievements • Lessons and way forward • Lessons learnt designing M&E data collection systems • Opportunities presented by open source platforms to non-profit organisations

3. Definition of Terms • A web based information management system is defined as a computerised database management information system that is accessible for use via the internet. • It allows both users and technical support staff to access, populate and use it online – improving online data collection, management and analysis.

4. OVERVIEW OF THE RUFORUM THEORY OF CHANGE, VISION AND MISSION

5. RUFORUM Vision A vibrant agricultural sector linked to African universities which can produce high performing graduates and high-quality research responsive to the demands of Africa’s farmers for innovations and able to generate sustainable livelihoods and national economic development

6. RUFORUM Mission To strengthen the capacities of Universities to foster innovations responsive to demands of smallholder farmers through the training of high quality researchers, the output of impact oriented research, and the maintenance of collaborative working relations among researchers, farmers, national agricultural research institutions and governments.

7. RUFORUM Theory of Change

8. The Justification for a web-based RUFORUM Information Management System

9. Why a web-based RUFORUM Information Management System? • Built to fulfil the requirements of the RUFORUM Theory of Change that recognizes strong management information systems as focal to the effectiveness of the RUFORUM Secretariat Core Programs. • The success of our interventions in the universities depend on strong systems for information management, information tracking and program evaluation.

10. Why a web-based RUFORUM Information Management System? • To facilitate efficient and flexible data capturing and data / information access • To improve monitoring of the implementation of research grants through web-based reporting • To strengthen learning in the RUFORUM Network • To provide data, information and knowledge for decision-making and justifying investments

11. The Situation Before the web-based RUFORUM Information Management System (RIMS) • Used Microsoft Word and Excel templates – with researchers submitting these templates and related attachments by email. • The emails tended to be bulky • The templates asked the researchers the same questions at each reporting period because static information was not accommodated. • The method of storage and retrieval of information was inefficient – if information was required it took time for it to be extracted and formatted for use • The information could not be viewed online and the information was not easily accessible to other key stakeholders.

12. The RUFORUM Information Management System (RIMS) • An open source platform built on a Django application, written in Python, running on a MySQL relational database management system and runs on a Linux server. Components of RIMS include • Contacts database that tracks students, alumni, principal investigators, university faculty and other stakeholders that network with RUFORUM • Online Reporting for grant awardees to report at 6,12,18,24 and 30 months • Events module • Module for capturing grant details and grant calls • Online Scholarship Applications for MSc and PhD Students • Managing Templates • Back end system for managing user rights and access.

13. The Approach and Methodology for developing the RUFORUM Information Management System

14. Methodology used to develop the web based RIMS Agile Methods – used to get an agreed understanding of what needed to be done, for whom, and what resources would be required: • A persona session where participants create fictional personas to represent users' perspectives on the MIS product • A user journey session where we examined the key tasks that each user (represented by the personas) wants to accomplish • A user story session where we captured detailed information about selected steps in the user journeys

15. Methodology used to develop the web based RIMS Agile Methods • embedded users to provide requirements • divided project into discrete runs that are developed individually • Used the scrum concept • Daily status meetings. • Minimized paperwork and accelerated development speeds are top goals of agile.

16. Online Project Management Tools Used • Django administration (https://www.djangoproject.com/), a high-level Python Web framework that encourages rapid development and clean, pragmatic design • Kanban Tool (http://kanbantool.com/), a visual project management tool. • Lopad (http://lopad.org/), a public pad for recording meeting discussions • Redmine (http://www.redmine.org/) web-based Project Management Tool written using Ruby on Rails framework. Redmine is open source and released under the terms of the GNU General Public License v2 (GPL). • Online communication tools – Skype; Group email; Virtual Network Computing – VNC over skype for virtual demonstrations / progress reviews

17. The SCRUM Concept • A product owner creates a prioritized wish list called a product backlog. • During sprint planning, the team pulls a small portion from the top of that wish list, a sprint backlog, and decides how to implement those pieces. • The team has a certain amount of time — a sprint (usually two to four weeks) — to complete its work, but it meets each day to assess its progress (daily Scrum). • Along the way, the ScrumMaster keeps the team focused on its goal. • At the end of the sprint, the work should be potentially shippable: ready to hand to a customer. • The sprint ends with a sprint evaluation and retrospective. • As the next sprint begins, the team chooses another portion of the product backlog and begins working again.

18. THE TOOLS: Django, Kanban, Lopad, Redmine and Skype

19. Day to Day Management of the RIMS project • Clear deadlines and deliverables • Online check-in daily calls • Email Based Reminders for meetings • Regular review and feedback • Face to face discussions at the user site when possible • User Requirements signing off – to reduce lack of fit to expectations • Clear product owner from the client

20. ACHIEVEMENTS

21. Key Milestones Over 3800 RUFORUM Network contacts information 100 research grants information Online reporting templates developed Over 40 researchers submitted their progress reports online MEL and Grants Team able to read and provide feedback to grantees online Better understanding of the research being implemented by researchers

22. Lessons, Gaps and Conclusion

23. Lesson 1: software development methodologies • Choose a robust software development methodology such as AGILE to manage project risks e.g. • Scope Creep : Agile projects should add the missed requirements to the backlog, push off lesser value requirements, and drop unnecessary requirements • Requirement Error : Agile fleshes out the requirement when it is being implemented providing much more visibility and a shorter time frame to reduce costs.

24. Lesson 2: online project management and managing virtual teams • Daily online check-ins and feedback are very useful • Online projects can be implemented with African partners / clients. Virtual Team was based in Kampala, United Kingdom, Slovenia, Canada and other African countries where the RUFORUM team members frequently travel to • Kampala speed tests: • Wireless: upload = 1.53 MB/s download = 2.09 MB/s (Orange Uganda) • Dongle: upload = 0.447 MB/s download = 1.29 MB/s (Orange Uganda)

25. Lesson 3: Work flow understanding and change management • Encourage users to think more about the way that they work – use a retreat for reflection. During system testing encourage users to capture records to ensure the workflow is better understood • Involving some types of users (e.g. researchers at universities) at discovery phase was perhaps premature - would have been helpful to demo other systems in order to get useful input • Online project management tools were foreign to RUFORUM team members - accustomed to face to face interactions – help users deal with their fears.

26. Lesson 4:Budget Versus Needs Aim for basic functionality – and improve the system as you become clearer on additional needs Reduce “nice to have” functionalities Use open source software development tools Build internal capacity for support

27. Lesson 5: Sustaining RIMS Need for a function in the organization to sustain the computerized MIS - to handle future changes requested by users and to administer the databases Ensure that there is a clear champion for the MIS – don’t rely on consultants Ensure buy in from the CEO and user departments

28. Gaps and Way Forward Data Quality management Data completeness Continuous Training for increased ownership – and full migration towards full use of the system Resources for adding more functionality

29. Conclusions • A well-articulated and accepted monitoring and evaluation framework is critical in the development of fitting computerised and web-based management information systems. • Online tools for supporting project management could cut down budget costs for developing management information systems. • Capacities and experiences of product owners need to be understood and training provided • Managing the scope of computerized Management Information Systems Projects is critical – link to the available budget • The procurement of software development consultants needs to be handled carefully. Ensure there is a team member in your organization who has experience managing software development projects