FoodNet+udviklerworkshop+11.+april+2015

RasmusErik, Nana, Jonas, Adam, Kasper, Lorena, Juan, Mikkel, Sofie, Thomas, Henrik, Troels, Lars, Kim, Maria ||
 * **When:** || d. 11/04-2015 kl. 14:00 - 18:00 ||
 * **Where:** || Vestergade 20C, 1456 København C ||
 * **Participants:** || Andreas, Christian, Kræn, Martin, Birgit, Gunilla, Sean, Stephane, Rosario,
 * **Can't make it:** || Kent, Maria O, Helena, ||


 * Minutes (and [|check out all of the photos here!]) **

Christian presented a little about Socialsquare, and Andreas led a little "conversation salon" to warm people up and get to know each other a little bit.
 * 1. Introductions **

Andreas gave a brief intro to the food coops and how this project has come about. [|You can find Andreas' presentation here].
 * 2. Background and vision **

Martin gave an introduction to the design challenges for the project, and led the team in a group exercise to identify the vision for the project. [|You can find Martin's presentation here].
 * 3. Design challenges **

The four groups summed up their visions in the form:

**For** [target group] **Who** [statement of need] **Our platform is a** [product category] **That provides** [key benefits, compelling reasons to use] **Unlike** [primary alternatives] **Our platform offers** [what makes this product different]

members food coops, new coops starting up passive members, community-driven projects (in the long run) farmers
 * ==Group 1== || ==Group 2== || ==Group 3== || ==Group 4== ||
 * **For …**

wants to particpate, wants to stay updated wants to coordinate wants buy/order products build community make the boring stuff easy to do
 * Who …**

web app self-service dashboard an administration system community organising tool webshop
 * Our platform is a …**

an integrated platform (no silos!) mobile app interfacing with other systems (online banking, facebook, etc.)- API
 * That provides …**

Other consumer relations management systems (such as Microsoft Dynamic CMS or CiviCRM)
 * Unlike …**

Lets members organise rather than merely letting administrators organise members. || **For …** members administrators tech illiterates, old people farmers potential members nerds vs. newbies potential coops
 * Our platform offers …**

(members) has problems with roles and tasks, who to ask (admins) plan, manage, no oversight, who to ask? (old, tech illiterate) the one not "online" (farmers) needs consistency
 * Who …**

management for food coops - social group - digital backend - collaborative enabler - coop enabler - continuity met - software as service vs. installable package - customizable look, feel, function
 * Our platform is a …**

easy way to join and participate in a coop from .. to full member from consumer to contributor easy way to communicate and organise easy way to manage secure payment / planning usability structured knowledge ad hoc communication
 * That provides …**

Facebook / Podio /Slack / the mess we use today / MS Project
 * Unlike …**

hooks for online mobile first! (SMS / texts) dumb phone, maybe functional core with modular open source (github!) || **For …** coop admin coop members coop volunteers coop consumers
 * Our platform offers …**

-- community farmers

overview contacts plan resources easy to use and make people happy! to buy process efficiency
 * Who …**

web mobile platform membership platform enterprise resource planning
 * Our platform is a …**

front end:
 * That provides …**
 * user administration
 * toolbox for all users
 * resource planning
 * shop
 * decision making system

back end:
 * accounting purchasing
 * complaints handling

CMS Wiki Google Docs
 * Unlike …**


 * Our platform offers …**

All of the above (except unlike!) || **For …** loosely organised groups of people

- members administrators volunteers activists "customers" different levels/roles purchasers

decluttering "voluntary condition/challenge" expectation management transparency need coordination (tools) less need for physical meetings ordering / payments organize shifts
 * Who …**

organization tool + webshop tool, system collaboration area common memory a "game" - only winners
 * Our platform is a …**

needed overview single access point decision support
 * That provides …**

email google docs facebook homemade specific undocumented systems
 * Unlike …**


 * Our platform offers …** ||

Kræn gave an introduction to the Scrum project management framework: The sprints, the roles, the meetings, the tools, the teams. <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">[|You can find Kræn's presentation here]. He ended suggesting that we use the open source tool Taiga to coordinate and collaborate on the product backlog for the project. [|You can access the project Taiga installation here]. <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">**UPDATE:** We now use Pivotal Tracker to manage User Stories and tickets. More here: https://www.pivotaltracker.com/n/projects/1337462
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">4. How can we collaborate as a group? **

<span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Kræn suggested that we establish a Green team and a Blue team:
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">**Team Green** focuses on user research, exploring needs and writing user stories and refining the product backlog
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">**Team Blue** focuses on building the product based on the items on the product backlog

<span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Andreas led a workshop where the team sought to define the shared values and goals for the project. So that we all have a shared understanding of the kind project we are starting together. <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">[|You can find Andreas' presentation on core values here] (at the end of the presentation).
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">5. Core values for the project **

<span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">The groups suggestions for core values for the projects were:

Group 1

 * Simple (Keep it simple, stupid!)
 * Flexible (A flexible product, a community that embraces flexible commitment)
 * Sustainable (easy to maintain)
 * Open (honest, transparent, Room for learning, considerate)
 * Easy to use
 * Effective
 * Fun

Group 2

 * Ambitious and fun
 * Inclusive and learner-friendly
 * Modular and scalable
 * Open community and platform
 * Transparent process and product

Group 3

 * Realistic
 * Democratic
 * Open and friendly
 * Both user-friendly and developer-friendly
 * Effective
 * Fun
 * Ambitious

Group 4

 * Free as in freedom (Open source)
 * Free as in beer
 * Democratic
 * Easy to use / "visually edible"
 * Useful / effective / supports actual needs
 * Respectful

<span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Andreas, Christian, Kræn and Martin suggested the following next steps:
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">6. Next Steps **
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">The whole team (Green and Blue) meets for a Sprint Planning meeting on Monday the 20th of April at 17.00 at Socialsquare HQ, Vestergade 20c to plan out Sprint 1. This includes defining tasks for both Team Green and Team Blue so that they can get started with their work.
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Andreas will sum up the work from the workshop and write a first draft of a vision for the project and a set of core values to be presented at the Sprint Planning meeting.
 * All members of the team will be invited to [|the project Taiga installation] so that they can familiarise themselves with the tool. <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">**UPDATE:** We now use Pivotal Tracker to manage User Stories and tickets. More here: https://www.pivotaltracker.com/n/projects/1337462
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Andreas has set up [|a Slack group] where all team members can coordinate their work between sprint meetings. You should all have received an invitation to your mail account. If not, let us know at foodnet@kbhff.dk :-)
 * <span style="background-color: transparent; color: #000000; font-family: Arial; font-size: 15px; text-decoration: none; vertical-align: baseline;">Oh, and we have to decide on a real name for the project. [|You can see all the suggestions so far here]. :-)