Present: Doug W, Tilmann B, Raphael F, Manuel W

Notary/ies: Doug W, Tilmann B, (later everybody wrote their statements themselves)

Location: jitsi

Outcomes:

• Doug will plan the first Scrum meeting for Rotterdam
• The exact implementation of Scrum at yunity needs to be figured out
• Doug is proposed as Scrum Master by Raphael and Martin, no resistance during this meeting
• We want to have a prioritized backlog, but people are free to choose the tasks they want to work on
• We plan and track all product-related work in the Product Trello board
• Development-only tasks will live in Waffle/GitHub issues
  

Meeting Notes

[Meeting begins: 20:30]

Expectations:

RF: Clarify and share what Martin, Holger and I have been doing and talked about. Schedule meetings for sprints.

DW: See what people are thinking and what we all mean by Scrum

MW: Clear the idea on how a Scrum set up would work.

TB: Clarify the usage and interactions of Product board, Waffle and Design board

Questions:

Raphael: 

• schedule the beginning and end of the 2-3 sprints during the WuppDays in Rotterdam (timeboxing)

• schedule Daily Scrum time and afterwords time with product owner team for clarification of issues

• schedule sprint review date for each sprint

• schedule retrospective for each sprint

• decide who gonna be the ScrumMaster

• decide if we want to try one product owner or 3 product owner test phase

Tilmann:

• Can I propose this sprint plan for the Rotterdam WuppDays and beyond?

• • https://yunity.atlassian.net/wiki/display/YUN/Rotterdam+Development+Plan

• • 1 week per sprint, retrospective and planning meeting on Sunday.

• • Daily meeting is not planned yet.

• Should we do the next product planning meeting today? I scheduled it for Sunday, 6pm. (This is more related to the Product board)

• Do you propose two Scrum processes, one in the Product board and one for developers?

• My proposal: three boards, which already exist and are used

• • Product Board: everything specification-related, high-level tasks for development and design

• • Design Board: design-specific tasks for the yunity product and other stuff (business cards, project page... )

• • GitHub+Waffle.io: development-specific tasks, split up into the backend/frontend repositories

Minutes

DW: Limit time to 22:00

DW: Everyone comfortable with the idea of what Scrum is.

DW: Is it helpful to have more than one Product Owner?

 RF: No, it can be confusing.

DW: This is then yunity-flavour Scrum, purists will be confused.

TB: the product owner is not actually involved in the scrum process

RF: Let's schedule when this starts.

TB: We don't schedule others people work.

RF: Agreed. I meant the first meeting. How about Tuesday

DW: Tuesday good, after lunch - 15:00

DW: Can Tilmann write to Dev and Manuel write to Design that we're gonna try this out?

DW: Schedule a Daily Scrum meeting at a fixed time.

DW: Hey guys, internet here is painful... I am going to fix that. I'm interested in Scrum and will continue reading. I think it could be very useful. I am cautious about making decisions set in stone now, but I think it would be good to tentatively put dates down and check everything is cool on Monday.

DW: I'm happy to let you guys shuffle Trello cards around, but if we are talking about Scrum - and we are - then addition and prioritisation of cards is the sole responsibility of the Product Owner team... 

TB: Don't forget that we are a non-paid open source project, so Devs and Designers will only work on things that they deem useful or enjoyful. 

RF: ;-)

DW: I would really love everyone to think about this whole more and then on Monday evening, or at some point on Tuesday someone would present the workflow as it is now, someone would present 'pure' Scrum then we could discuss how we want to make 'yunity -flavour' Scrum which we would then start and reevaluate soon.

RF: yeah I would like to prioritze the cards (there are actually already kind of prioritzed by numbers) and during the first sprint meeting this can be evaluated with Martin and the devs who will be there

RF: so what do you think Tilmann should we focus on the trello board of product with the user stories or extract from the user stories there the more detailed stories for waffle?

TB: (we switch to writing now) +1

TB: The cards in the Development Scrum board seem high-level enough to put them into the Product board. 

RF: OK

TB: Therefore, prioritatization should not be the sole responsibilty of the Product Owner.

RF: definetly, but with Nick, Martin and You we kind of prioritzed them in Berlin together, so the basic roadmap is already there, we have almost not changed anything from the prioritisation 

DW: I agree that 'pure' Scrum probably won't fit and that we'll need to make 'yunity-flavour Scrum'.

DW: Further to doers desiring agency over their work: just because there is a prioritised backlog doesn't mean people need to work on the priorities.

RF: ok my dears, than lets meet on the 22nd at 3pm - i will move everything from the development board into the product board

TB: We can use this calendar for planning the Product things: 
https://yunity.atlassian.net/wiki/display/YUN/Rotterdam+Development+Plan
Feel free to modify 

RF: OK

DW: I'm gonna put my feedback down and get back to doing things here.

Feedback

DW: Excited with the prospect of smoother workflow. Concerned that not all the affected parties are aware. Still not sure that everyone has the same thing in their head when they say 'Scrum'. Looking forward :)

RF: I am thankful that we got together, and even if I love to meet you all in person all the time and talk face to face, i believe it was very useful and the suggestions from new people (kirstin, Manu, Holger etc.) moving us into a more genuily working procedure like scrum is will be very benificial for the project as a whole and I am very glad and honored, that you lovely Doug will do the ScrumMaster! Lets all do further reading on it, there is plenty of information available and this will get us more on the same page

TB: I'm happy to bring people more closely together for development, design and specification writing.

[Meeting ends: 21:50]