Your SlideShare is downloading. ×
Implementing IT Solutions for Disaster Management (SahanaCamp 1.2)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Implementing IT Solutions for Disaster Management (SahanaCamp 1.2)

435
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
435
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Get people to think back to the morning – perhaps think of their work, and design a Information System
  • This will be done as an exercise in the afternoon – get people to write specifications for the information systems which they designed.
  • Transcript

    • 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?
    • 6. Software Development Cycle Requirements Gathering Specifications Development Testing Training Support
    • 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

    ×