| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Files spread between Dropbox, Google Drive, Gmail, Slack, and more? Dokkio, a new product from the PBworks team, integrates and organizes them for you. Try it for free today.

View
 

FrontPage

Page history last edited by PBworks 13 years, 9 months ago

This Pro-Bono Web Dev wiki has it's roots in a presentation given at BarCampLA.

 

My assumption is that many of us have been in the situation of having to consider whether or not we will volunteer to lend our skills and/or expertise to help some deserving person or institution out by taking on their web project for little or no money.

 

It might look like this. "The web would be the perfect tool for 'non-profit community group X' to get it's message out and serve it stakeholders. People could come together. Interact online. Find out about events. Join a mailing list, an online discussion forum, I could set that up in no time." If you are a stakeholder/member of this hypothetical community you will be served by whatever web tool the group comes up with so you want it to be good and serve your own needs well. There are lots of cheap/free resources available to make this happen seemingly effortlessly. You can set up a blog/cms software on your server, tweak some templates and you're done.

 

But that isn't the whole story.

 

How do we take this project on so that it will be successful while at the same time still have a job and time to see family and friends. How do we structure it so that once it's launched it no longer depends on us.

 

Why do it?

 

 

We are stake-holders who will be served by this website. Since we will use it we want it to be good, right?.

We believe in the mission.

 

Guidelines

 

Out of the box project management to go along with your out of the box 'blog/cms' solution.

 

Project Management

 

Manage the project like any other. 'Out of the box' project management plan to go with your 'out of the box' CMS. The idea is that most projects have the same needs/components.

 

Define

User Personas

Scope

Business Rules

 

develop

UI

IA

Visual design

admin tool

database

 

Roles and Responsibilities

 

Change Management Procedures

 

It may sound silly if you are the only person doing all these things but defining them means when you burn out someone else can pick up where you left off. It will allow others to come along and add their talents without stepping on toes. New visual design? No problem, follow this.

 

Moderation Guidelines for Online Forums

 

Posting Guidelines for Non-Profit Board Members

Comments (0)

You don't have permission to comment on this page.