Present: Douglas Webb, Raphael Fellmer, Martin Schott, Be, Manuele Carlini, Chrisi, Matthias Larisch, Selina Camile, Monika, Tess
Apologies: Tilmann, Joachim Thome (get better soon!)
Notary/ies:  Douglas Webb
Location: Kirchheim 

Animals and/or Ice-cream 

Douglas Webb: A cone of mint, with ants all over it.

...

Not so good, puzzling and good.

Not so good 

• Under-utilization of available resources due to insufficient communication/information-flow. AP: Have responsible figures for each department who have an overview of the area and should be contacted first. Generally ask for help/talk more. Make available information visible (document). Announce things in a way that everyone can keep up to date: hashing people in conversations and not relying on Slack. Document on wiki, subscribe to daily update. Consider more direct messages. Summaries on wiki blog (for Doug).
• Break in work flow between WuppDays and different starting times. Availability of contributors is irregular. AP: Improve communication within teams (how?). Concern: People are busy/not motivated when not at WuppDays. AP: Still have Scrum events online when not at wuppdays. Concern: Unwanted pressure
• Insufficient knowledge base with regards to more technical detail (debugging, etc). AP: Mentor base: people who know more being able to help people who understand less.
• Vague task description. AP: Tasks being finishable within 24 hours (subdivided if necessary)

Still puzzling  

• How to create a stable work flow going forwards, especially wrt. contributor availability?
• How can we make it easier for contributors to find their way to contribute? (Buddy system started, how can we optimize it further?)
• How to integrate new contributors with useful energy and skills but with differing primary objectives to yunity? (i.e. not directly or indirectly getting platform online)
• Is the current MVP spec actually the minimum viable product?
• How do we find the right balance of openness and closedness? (e.g. new people and new ideas vs a common agreed goal which everyone works on)
• How to engage the whole yunity community to really support getting the product done?

What went well 

• Scrum facilitation. AP: Continue being nice to Doug and he will continue doing so.
• Feeling of progress.
• People who did heroic amounts of cooking. AP: Continue asking for people who are especially interested in cooking
• Having the flexibility to work in way that suits everyone. AP: Continue adapting process to people (not other way round)
• New contributor integration. AP: Documentation, buddying, etc
  
• Silent room. AP: always have a silent room (dev voov!)
• Nice balance between wupp and play. AP: Continue to have a good balance of old to new contributors. continue having awesome activities.
• Amazing building! AP: Selecting properties based on need not availability. Have meetings to make this the case.
• Amazing food! AP: Incredible cooks must be thanked/massaged/etc
• Existing foodsharing infrastructure. AP: Consider as a building requirement.
• Amazing foodsavers! AP. Be near them and nice to them, always. Thanks foodsavers.