Participatory Programming

699 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
699
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • DM is not a stable environment – hard to train, implement, test Different org. values – grey vs black/white. The industries are weak on quantitive KPIs High staff turn around Project based funding Different culture / Language Remote locations Power imbalance
  • From the 70s Why: Appropriate Ownership -> Sustainable Empowering users Mutual Learning
  • Group dynamics learning contracts, role reversals, feedback sessions Sampling transect walks, wealth ranking, social mapping Interviewing focus group discussions, semi-structured interviews, triangulation Visualization venn diagrams, matrix scoring, timelines
  • Getting off on the wrong foot with Denise
  • Participatory Programming

    1. 1. Participatory Programming 2 nd July 2010 SahanaCamp Michael Howden [email_address]
    2. 2. Overview <ul><li>Challenges of programming in the fields of Disaster Management and Development. </li></ul><ul><li>Participatory Development </li></ul><ul><li>The Power of Questions </li></ul><ul><li>User Testing </li></ul><ul><li>Training </li></ul><ul><li>Support </li></ul>
    3. 3. What are some of the challenges in developing software in the fields of Disaster Management and Development?
    4. 4. Participatory Development <ul><li>“ Participation refers to involvement whereby local populations engage in the creation, content and conduct of a program or policy designed to change their lives. Participation requires recognition and use of local capacities and avoids the imposition of priorities from the outside.” </li></ul>
    5. 5. Participatory Software Development <ul><li>Both use technical skills to solve complex real world problems </li></ul><ul><li>Bottom Up vs. </li></ul><ul><li>Top down </li></ul><ul><li>Agile vs. Waterfall </li></ul><ul><li>Open Source? </li></ul>
    6. 6. Participatory Rural Appraisal <ul><li>Group dynamics </li></ul><ul><li>Sampling </li></ul><ul><li>Interviewing </li></ul><ul><li>Visualization </li></ul>
    7. 7. Participatory Rural Appraisal <ul><li>Group dynamics </li></ul><ul><ul><li>learning contracts, role reversals, feedback sessions </li></ul></ul><ul><li>Sampling </li></ul><ul><ul><li>transect walks, wealth ranking, social mapping </li></ul></ul><ul><li>Interviewing </li></ul><ul><ul><li>focus group discussions, semi-structured interviews, triangulation </li></ul></ul><ul><li>Visualization </li></ul><ul><ul><li>venn diagrams, matrix scoring, timelines </li></ul></ul>
    8. 8. The Question Game
    9. 9. User Testing <ul><li>Test Early, Test Often </li></ul><ul><ul><li>3-4 Users </li></ul></ul><ul><li>Test with Anyone </li></ul><ul><li>Don’t be defensive! </li></ul><ul><li>Testing Triage </li></ul><ul><ul><li>Long Hanging Fruit </li></ul></ul><ul><li>Testing = Participation </li></ul><ul><ul><li>But also has a cost </li></ul></ul><ul><li>www.sensible.com/secondedition </li></ul>
    10. 10. Training <ul><li>Technical or Processes? </li></ul><ul><li>Interactive </li></ul><ul><ul><li>Simulations </li></ul></ul><ul><ul><li>Participation </li></ul></ul><ul><li>How does the software fit into their jobs? </li></ul><ul><li>How does the software create value for them? </li></ul>
    11. 11. Support <ul><li>Approachable </li></ul><ul><li>Responsive </li></ul><ul><li>Clear </li></ul><ul><li>Objective </li></ul>
    12. 12. Conclusion <ul><li>Participation can increase the chances of success of a project </li></ul><ul><li>Involve all stakeholders in the programming process. </li></ul><ul><li>Engage people with questions </li></ul><ul><li>Don’t forget User Testing, Training and Support </li></ul>

    ×