Skip to content
This repository has been archived by the owner on May 21, 2020. It is now read-only.

Home

Jump to bottom
Michelle Hertzfeld edited this page Jul 20, 2016 · 3 revisions

Code for Tucson Working Hypotheses

We believe that: changing the content on the website to look/feel less ‘code-y’

Will result in: more balanced teams at Code for Tucson

We will know that we are right when: more designers, product managers, non-coders come to Code for Tucson meetings

We believe that: focusing on one or two projects, and managing them well

Will result in: providing a vehicle for learning and teaching about the entire project process; satisfaction!; better quality project; work more efficiently; provide structure/direction to the volunteer group; opportunity to engage more than twice a month

We will know that we are right when: projects are completed; people are more committed to projects (ie, more repeat folks); more contributions between meetings

We believe that: having more classes, and perhaps classes that build towards our projects, or at least help conceptualize what’s going on.

Will result in: people leaving with a sense of purpose and accomplishment

We will know that we are right when: people report feeling connected to Code for Tucson events; people are more committed to projects (ie, more repeat folks); more ability to have folks contribute between meetings

more to come

Clone this wiki locally