Sprint 1 planning 20th of April 2015

1. Summary of results of the workshop on April 11th

Andreas has tried to sum up the results of the shared efforts of the team at the start-up workshop on April 11th. He presented a first draft for a vision for the project, and a set of core values to help guide the project:

One line description

FoodNet is an open source web application that provides simple and flexible infrastructure for organizing food coops and other local community-driven projects.


For food coops and other community-driven projects whose members want to coordinate shared resources, tasks and products, FoodNet is an open source web application that provides a simple and flexible infrastructure for organizing local communities.

Unlike other groupware such as Wiki, Google Docs, Facebook and Podio and other membership systems such as CiviCRM, FoodNet offers an integrated dashboard/toolbox that allows both members and administrators to participate and have an overview of their community.

FoodNet – Core values

We are committed to making the FoodNet platform:

1. Useful – This platform exists to support the needs of local communities. It should support these needs as effectively as possible.

2. Simple – visually appealing and easy to use and manage.

3. Flexible – Modular and scalable – easy for others to develop and adapt to their needs.

4. Sustainable – Reliable and easy to maintain.

5. Free – Both libre (open source, or free as in freedom) and gratis (free as in ‘free beer’)

Working together, we strive to be:

6. Open and transparent – our community is founded on democratic principles, and we strive to make it easy for everyone to participate, use and learn from the work we do.

7. Ambitious (and have fun!) – we want to have fun while changing the world!

8. Inclusive and respectful – our community is a user-friendly, learner-friendly and developer-friendly. It is a space for learning, where everybody feels comfortable to ask for help when they are unsure.

9. Realistic and effective – we don’t bite off more than we can chew. We take responsibility for the work we do, and when somebody leaves or disengages from the project, we expect that they do so in a way that minimises disruption to the project.

The people present didn’t have any objections to the draft, this will be what we’re basing the project on for now, developing and refining it as we go along.

We didn’t go into the name discussion again, but there is a long list of suggestions on Slack. Please add more of help qualify the ones already there. 🙂

2. Establishing activities for the sprint for Team Green and Team Blue, respectively


Facilitating Scrum


Team Green (exploring user needs, validating assumptions, defining product)

The team members will work on the following tasks for the Sprint:

Desk research / reading existing material

Observation and/or interviews in local KBHFF shops
Kim (primarily focusing on mobile use)
Maria (primarily focusing on new members of the coop)

Defining the product: Writing user stories, describing functionality, developing the concept
Andreas (will coordinate with Tine and the ØkoStartpakke project which will also be doing fieldwork in the food coops in the coming months)
Martin (Martin will write a frame for gathering user stories and invite other members of the Green Team to participate)

Defining the product: Wireframing on a simple level

Advertising the project, Recruiting more interested developers

Team Blue (Building product)

The team members will work on the following tasks for the Sprint:

Defining the product: Drafting on the logical model of the system

Implementing: Agreeing on the first take on technology stack (Voting about it, Coding challenge, )

Implementing: Coding

3. Getting aligned on the availability of people

Team Green
Maria: 2-4 hours three times a week.
Nana: Has a masters thesis coming up, so won’t be able to contribute much this sprint.
Kim: Remote work. No clear estimate.
Martin: 30 hours per sprint
Andreas: 4 hours per week coordinating with the food coops, ~5 hours a week on top of that as Product Owner and part of Team Green.

Team Blue
Thomas: 2-3 hours per week.
Mikkel: 15-20 hours per sprint (month)
Francesco: 1-2 evenings in the week, maybe half a day per weekend (in Italy the first two weeks)
Sean: 5-6 hours per week (unless it’s extremely fun)
Kræn: ~10 hours per sprint
Socialsquare programmer to join the team from next week: 30 hours per sprint

4. Introduction to the product backlog

Andreas walked the team through the product backlog as it is set up now in Taiga. We’ve only begun to unfold the first Epic focusing on Memberships. Both teams will add their tasks for the sprint to the backlog to get used to working with the tool and show the work they’re doing.

5. Planning the sprint (next four weeks)

We seperated into the two teams committing ourselves on a sprint backlog.

For the blue team to start estimating the workload required of the various user stories, the team felt the need to become more concrete on the first take on what technology they would be working with for the first sprint. They choose to go through the survey submissions (to be published) from all the volunteer developers writing on the whiteboard what suggestions for frameworks and technology each of the respondees had.

A majority (4 votes over 5 frameworks / languages with one vote each) named the high-level Python Web framework Django as an interesting technology to pursue in sprint #1. The team agreed that this is in no means a final decision on technology – one voiced the need to decide if the team wanted to use any client side frameworks as-well (React was mentioned), but this will be up to the team to decide as they work their way through the sprints.

We’ll finish the sprint on Monday the 18th of May (following the long Kristi Himmelfart weekend). We’ll have a Sprint Review meeting followed by a Sprint Planning meeting for the upcoming sprint. And dinner in between! Agenda for the evening can be found here.

We’ll have a backlog refinement meeting in the first week of May. Kræn will send out a doodle so that we can agree on a date.

We will also have weekly check-ins (instead of the “Daily Scrum” meetings) – either synchronous on Skype or asynchronous on Slack. Kræn will set these up.

Leave a Reply

Your email address will not be published. Required fields are marked *