The document discusses participatory programming which involves engaging local communities in the development of software projects designed to impact their lives. Participatory programming has several objectives including prolonging project impact, making projects more relevant, enhancing effectiveness, establishing relationships, making projects more responsive, increasing available resources, and improving efficiency as participants learn new skills. Both community development and software development use technical skills to solve complex real-world problems. The document asks who should participate in participatory programming and lists potential roles including users, administrators, requirement gatherers, translators, managers, testers, document writers, deployers, and software developers. It also discusses how to engage the community in participatory programming.

1. Participatory Programming
3 November 2010, SahanaCamp
Michael Howden
michael@sahanafoundation.org

2. Participatory Development
Engage local populations in the
implementation of a project designed to
change their lives.
Recognise
and use of local
capacities.
Avoid the imposition
of priorities from the
outside.

3. Why Participation?

4. Objectivesof Participation
• Prolongs impact
• Make project more relevant
• Enhances effectiveness
• Establishes relationships
• More responsive
• Increase resources available
• Improves efficiency
• Everyone learn new skills
www.urd.org - Humanitarian Participation Handbook

5. Community Development
vs.
SoftwareDevelopment
Both use TECHNICAL SKILLS to solve
COMPLEX REAL WORLD PROBLEMS

6. Participatory Programming
• Bottom Up vs. Top down
• Agile vs. Waterfall
• Open Source?

7. Who Should Participate?
• Software Developer
• User
• ???

8. Roles
• User
• Administrator
• Requirement
Gatherer
• Translator
• Managers
• Tester
• Document Writer
• Deployer
• Software
Developer

9. HowDoYouEngagewith
theCommunity?

10. HowDoYouEngagewith
theCommunity?