Implementing IT Solutions for Disaster Management (SahanaCamp 1.2)
Download as PPTX, PDF0 likes965 views
This document outlines the challenges and best practices for implementing IT solutions for disaster management. Some key challenges include uncertain and changing conditions during disasters, communication gaps between organizations and IT providers, and limited time and resources. The document recommends engaging end users during all stages of the software development cycle, from initial requirements gathering to ongoing support. It emphasizes listening to users, testing software early and often with users, and providing training that is interactive and collects feedback to ensure the IT solutions meet real user needs and create value for them.
Implementing IT Solutions for Disaster Management (SahanaCamp 1.2)
- 1. Implementing IT Solutions for Disaster Management 3 November 2010, SahanaCamp Michael Howden michael@sahanafoundation.org
- 2. What are the Challenges in Implementing IT Solutions for Disaster Management?
- 3. Challenges • Uncertain and changing conditions. • Communication Gap: • NPOs/Government IT Providers • Limited time and resources • Technology is Easy Getting people to use it is hard!
- 4. Implementing Information Management Systems Think about: • Value • People • Locations • Activities • Inputs • Outputs • Existing Systems and Processes
- 5. Engaging “Users” • Find a Champion • Engage across the spectrum • Get commitment • Respect different priorities • Consider: – How will the software change the way they work? – How will the software create value for them?
- 7. Requirement Gathering • From whom? – Talk to the end users • Listen • Be curious! • ‘Real needs’ vs. ‘perceived needs’ • What are their problems? – Then look for the solutions
- 8. Specifications • Document History • Background Scenarios • User Stories • Non-Goals • Definitions • Users • Data Model • Flow Charts • Menus • Screens - Wireframes • Technologies • References http://www.joelonsoftware.com/articles/fog0000000036.html http://www.joelonsoftware.com/articles/fog0000000035.html
- 9. User Testing • Test Early, Test Often – 3-4 Users • Test with Anyone • Don’t be defensive! • Testing Triage – Long Hanging Fruit • Testing = Participation – But also has a cost www.sensible.com/secondedition
- 10. Training • Software or Processes? • Ceremonial • Interactive – Simulations – Participation • Collect feedback on software
- 11. Support • Needs to be ongoing • Be approachable • Responsive • Clear • Objective