From Sunlabs wiki

This page was established for the purposes of the OpenGovNYC Collaborative Policy Workshop - 4/28/09

http://www.meetup.com/opengovnyc/calendar/10234024/

5ao7EM <a href="http://swfqyjuxumva.com/">swfqyjuxumva</a>, [url=http://moxqqigvjnkw.com/]moxqqigvjnkw[/url], [link=http://tvfvzkbyctwk.com/]tvfvzkbyctwk[/link], http://cgrsfwlztxta.com/

Notes

This outline was Matt's attempt to map the conversation in real time of essay writings, essay writing.

1. defined, discrete project that can be completed in a short period (24-48 hours)
   1. subset of a pre-defined problem
   2. pushing to get something started
   3. pushing to wrap something up
   4. sequential sprints that build on previous sprints
2. it's a sprint: you can only sprint for so long
3. parallel, coordinated sprints, part of a larger architecture
4. someone needs to write a spec that defines the problems to be solved
   1. coding is an exercise in translation - moving from general vision to specific logic
   2. coding is highly modular
   3. who is in charge of setting it up?
   4. sprint comes in the middle, after a leader has initiated it
5. specify size of working groups
6. pre-research, aggregating available data, mapping the territory, crowdsourcing the information
7. providing an informartion alternative to policy-makers who manipulate data for political purposes
8. steps
   1. define a problem
   2. aggregate research
   3. map alternatives
9. process-mapping the existing policy-making "operating system"
10. building our own standard operating system for open policy-making
11. how do you keep the parameters narrow?
    1. in any sprint, there is a tendency to expand the parameters
    2. defining goals within timeframes is key

Proposed Policy Sprint Catalyst Session Process

(Mark used this process to get the ball rolling. As is often the case in these scenarios, it was quickly abandoned.)

1. [5] Premiss (form only, minus content if possible):
   1. To build a process for future policy sprints, independent of content, so that we can replicate the process in different contexts.
2. [5] Explore content ideas:
   1. Write guidelines for future policy sprints (will guidelines suffice or will more structured instructions be required?)
3. [5] Revise premiss if required:
   1. [35] Process (broadest/longest view):
      1. [5] Milestones (biggest):
      2. [10] Identify creative processes for each (me - 3Cs - RIVER):
      3. [5] Identify agent(s) for each (individuals & groups):
      4. [10] Identify tools for each (classes that mach process):
      5. [5] Note issues/risks/oportunities etc:
4. [5] Promotion needed:
5. [5] Name project lead (person who will shoulder the responsibility of taking the lead: overcoming cold start problem, coordinating information, reminders/pokes/prods, ):
6. [15] Review & revise all. Add second level/layer of detail. Assign individuals to tasks where relevant.

• • Britt: a list of specific tasks with specific dates, which fewer than 15% of participants object to

Additional considerations (as homework)

• Define success.
• Involve those not present? (may overlap with promotion)
• Guidelines for participation needed? (making explicit rules, guidelines, netiquette, etc) Go light - if group is small and pre-established, unlikely to be needed.
• [Add your ideas here.]