List Info

Thread: (ISF) Advice for small nonprofits in drafting agreements with a web developer/designer




(ISF) Advice for small nonprofits in drafting agreements with a web developer/designer
country flaguser name
United States
2007-05-02 12:02:38

Dear ISF Colleagues,

A small nonprofit has selected a web consultant, and is looking for
tipsheets, checklists, and contract boilerplate. It's safe to assume
that the prospective clients have no experience with web development
or the usual cycle of a web development project.

If you have any materials that would be useful to the small nonprofits
(and that you are legally entitled to share), please feel free to post
links to the list or to email me the documents off list.

If possible, I prefer materials from nonprofits that have successfully
managed negotiation and implementation of web projects, rather than
materials from web consultants who work with nonprofits. It's all a
matter of point of view.

Many thanks from Deborah

Deborah Elizabeth Finn
Boston, Massachusetts, USA
deborah_elizabeth_finn%40post.harvard.edu">deborah_elizabeth_finnpost.harvard.edu
www.cyber-yenta.org

Recommended reading:
"Universal Declaration of Human Rights"
<http://en.wikisource.org/wiki/Universal_Declaration_of_Human_Rights>;

__._,_.___
.

__,_._,___
(ISF) RE: Advice for small nonprofits in drafting agreements with a web developer/designer
country flaguser name
United States
2007-05-02 12:27:06

Deborah,

I'm writing in clear violation of your note looking for tips from nonprofits - but couldn't resist. A fair bit of my work here at NPower Seattle is to help nonprofits be savvy about their web development - even if we're not doing it!. I have a handful of tips on my blog that might help:

1. Stuff about color - which is different on the web than in print: http://community.npowerseattle.org/patricks/2007/01/30/what-color-is-red -or-what-do-i-need-to-know-about-colors-for-my-website/ and http://community.npowerseattle.org/patricks/2007/02/16/more-about-color/

2. Stuff about DNS - which they'll need to launch: http://community.npowerseattle.org/patricks/2007/01/11/help-please-expla in-dns-domain-names-hosts-and-all-of-those-things/

3. Stuff about a final sign off process: http://community.npowerseattle.org/patricks/2007/01/04/signing-off-on-yo ur-new-website/

4. And some tips about providing feedback about design compositions: http://community.npowerseattle.org/patricks/2006/12/09/how-do-i-provide- feeback-about-my-new-web-design-comps/

I think the other items I'd mention (which may or may or may not help a lot) is that we try to implement in a series of stages:

I. Information architecture (and we hope that this stems from a tech savvy communications plan!)

II. Visual design (which meets the needs of the audience described in the communications plan!)

III. Coding and production

IV. Testing and publishing

V. Documentation and training

I think that helps nonprofits set milestones, estimate their own work effort (which can be a lot!) and gives them great check in points with their develpor.

Hope that helps!

Patrick Shaw

http://www.npowerseattle.org

-----original message-----
>&gt;A small nonprofit has selected a web consultant, and is looking for
tipsheets, checklists, and contract boilerplate. It's safe to assume
that the prospective clients have no experience with web development
or the usual cycle of a web development project. If you have any materials that would be useful to the small nonprofits (and that you are legally entitled to share), please feel free to post links to the list or to email me the documents off list. If possible, I prefer materials from nonprofits that have successfully managed negotiation and implementation of web projects, rather than materials from web consultants who work with nonprofits. It's all a matter of point of view. >>

[Non-text portions of this message have been removed]

__._,_.___
.

__,_._,___
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )