Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Minutes
Present: Matthias L, Tilmann B, Martin S, Manuele C, Kirstin S, Raphael F, Janina A, Philipp E
...
First: catch-up on the different expectations and summary of the last smaller product/structure meeting on 16020816-02-08.
Most important questions include: a clear way of decision making, getting on the same page, finding tasks for new programmers and ways to include them productively, define the launch date, getting a clearer image of what the product should look like and which features the MVP should include, differentiation of design dev and product team and getting more clear on their common workflow
...
TB: The purpose of the product team is to ask the question 'How can we fulfill the user's needs?' So... what should our specifications look like?
MS: We should priorititzeprioritize, e.g. focus on the food basket for the next weeks and distribute related tasks.
...
TB: Yes. That's how i see it. Of course all three teams need to work together really closelyclose, but it should always be clear in which team's sphere a task is located. I for example am dev and product and also have experience from foodsharing. But this experience shouldn't influence my work as a dev. That's why i'd like to clearly seperate the tasks, but not nessecarily keep people from participating in more than one of said teams.
...
TB: For communication it would be useful to not only have a head of the product team, but also heads of dev and desgindesign.
MC: To get quick answers i I want to have a person who has the overview, so that i don't have to read through all of the wiki all the time
...
Obviously there are problems and concerns regarding this approach, but it seems to be convenient for now.
TB: How does our goal gold standard look like? We have these wiki pages on different features. Is it detailed enough to be used by dev and design?
...
TB: Maybe we should make clear that there is a difference between original articles and dependent articles. A dependent article is like a summary of original articles and therefore needs to be changed accordingly, when changes on the original articles are made.
MS: Exactly, it's really difficult to work on things, since everything is inertwined. If i change something on a feature it could have unwanted consequences on other features.
...