Day 1
Mapping the technical and needs space
- 9:00 - 10:00 - Welcome - Background, Structure, Culture (Dorn, Greg, Kita, Rex)
- Dorn, social media person (hashtags, etc.), background, etc.
- Greg - Physical and community plumbing…
- physical, bathroom, kitchen, etc
- goat, openteam
- Get on the goat forum and sign up, riot
- day 2 Mud to Bricks
- Hats on, hats off…
- Keep in mind: What do you do, what do you want to support in 5 years, do you have a plan to do so?
- Decentralized North Star
- Kita + Rex - intro to human centered design
- 10:00 - 11:30 - Setting Demands and Needs (Gregory)
- Demands - list of things that the world demands of our technology
- Needs - list of things that users need
- Synthesize output together, post to forum, support final feedback + finalize (Greg)
- 11:30 - 12:00 - Create Map (Ankita)
- Summarize the goal of this thing, give simple brief example of a map
- Write down what your existing plans are
- 12:00 - 1:00 - LUNCH (keep working if you want!)
- 1:00 - 2:30 - Split the groups around specific personas (Dorn)
- LIST OF PERSONAS
- Ag Researchers (MSU, USDA CROWN, etc.)
- Farm and Ranch Managemers (the business of farming) (Picines, Angela)
- Ecosystem service quantificatiers (Nori)
- Certification and ag service providers (eg Terragensis Cacao)
- Land use planners (eg City of Boulder)
- Each group maps use cases in their personas
- 2:30 - 3:00 - We then compare those map to pre-defined map (Dorn)
- We update pre-defined map based on group maps
- 3:00 - 3:15 - break
- 3:15 - 4:30 - Facilitated session to create functional groups (Dorn)
- Present framework (work packages) (Ankita)
- who’s in what group, who is everyone working with
- Report back: who’s in what group. How is each group going to work together? Each group discuss…
- 4:30 - 4:40 - North Star time (Dorn)
- 4:40 - 5:00 - Daily wrap up (Dorn)
Outputs
- Create list of personas
- Demands and Needs list
- Define Draft Technical Map (shows flows of users through the tools)
- Define Functional Groups (tools with similar functionality grouped together)
Day 2
Testing the map
- (15m) Intro do day 2 -
- (5m) North Star (Dorn)
- What happened on day 1 (map) (Dorn)
- Goals for day 2 (Ankita) + mention Photo!
- Documentation, community plumbing… Keep in mind: clay to bricks… What do you do, what do you want to support in 5 years, do you have a plan to do so? Take accepting work projects seriously (Greg)… Intro to map, intro to functional groups, split into functional group,
- 9:15 - 10:15 - Break into persona groups (Greg)
- Refine / improve / adjust map based on community feedback
- 12:00 PHOTO (farmOS)
- (10:15 - 2:15) - Split (Ankita)
- (half the room) - Developer
- Mapping functional groups to working groups
- Inside the box is the…
- who’s gonna do it and quick description
- this is low hanging fruit
- community partner involvement
- (half the room) - Community Partners
- mapping year of participatory design opportunities
- Create timeline of design and testing capacity + opportunity (I have a cool use case that is easy to connect to, here’s how)
- Create list of feature requests which Dev’s can pull from directly (in real time)
- mapping year of participatory design opportunities
- 2:15 - 3:15 - Prioritization happens in real time based on these graphs
- (half the room) - Developer
- 3:15 - 4:45 - Cross Pollination (Ankita)
- Community group presents their list + priorities, Dev partners presents their list + priorities.
- Final synthesis, feedback.
- 4:45 - 5:00 - North Star (Dorn)
- 5:00 - 5:15 - Reflections on the day (Dorn)
GOAT HACK PORTION!
Community partners can identify dev partners via their work packages
Dev partners can identify community partners via their feature requests
Outputs
- List of features
- List of work packages
Day 3
- 9:00 - 12:00
- Intro do day 3 (Dorn)
- Continued Hacking
- 12:00 over lunch - presentations of hackers!
- 1:00 - conference over, but folks can stay and make sure we have final outputs.