Minutes Neos Team Forming Meeting


(Gina Steiner) #1

Team Forming Meeting by the Neos Team, moderation by Gina
Tuesday 13th of October 2015, online via Gotomeeting, 12:00 - 13:30

Introduction
In this meeting we will build the teams!
In this meeting we will NOT decide on any roles, guidelines or tasks. This will be done in separate team meetings (retrospectives).

Rules

  1. Distribute the skills as evenly as possible.
  2. Distribute the size of the teams as evenly as possible
  3. Pick the team where you like the people most

People
Attending: Gina Steiner, Christian Müller, Christopher Hlubek, Sebastian Kurfürst, Alexander Berl, Karsten Dambekalns, Florian Heinze, Rens Admiraal, Ben van Kruistum, Robert Lemke, Daniel Lienert, Aske Ertmann, Bastian Waidelich, Andreas Förthner, Sebastian Helzle, Tobias Gruber, Markus Goldbeck
Absent: Dominique Feyer, Berit Hlubek, Dmitri Pisarev

Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

-> especially keep “Individuals and interactions over processes and tools” in mind!

http://www.agilemanifesto.org/

Team Building
Forming, Storming, Norming, Performing - please read this!

Build the Teams
We build the teams…
Team 1
Christian Müller, Christopher Hlubek, Berit Hlubek, Sebastian Kurfürst, Dominique Feyer, Alexander Berl
Team 2
Karsten Dambekalns, Florian Heinze, Rens Admiraal, Ben van Kruistum, Robert Lemke, Daniel Lienert, Dmitri Pisarev
Team 3
Aske Ertmann, Bastian Waidelich, Andreas Förthner, Sebastian Helzle, Tobias Gruber, Markus Goldbeck

Channels

  • Now there are three team channels - they need to be renamed by the teams
  • Synchronizer channel (private)
  • Prioritizer channel

ToDo CoP Transition

  • Add the team members to the respective team channels
  • Take care of the council of elders
  • Take care of the CoPs
  • Think about general meetings

ToDo Teams

  • Have a first meeting (retrospective) -> deadline 20th of October 2015
  • Choose a name - rename the channel
  • Do retrospectives regularly, publish minutes
  • Vote Synchronizer (at least in an election once a year)
  • Vote Prioritizer (at least in an election once a year)
  • Can get help by a moderator from the CoP transition. If so, please post this in the regarding channel.

ToDo Synchronizer

  • Have a first meeting (retrospective) -> deadline 27th of October 2015
  • Do retrospectives regularly, publish minutes
  • Work on the guidelines, publish them
  • Must get help/coaching by a moderator from the CoP transition

ToDo Prioritizer

  • Have a first meeting (retrospective) -> deadline 27th of October 2015
  • Do retros regularly, publish minutes
  • Work on the guidelines, publish them
  • Must get help/coaching by a moderator from the CoP transition
  • Come up with an idea about how to take care for the product strategy and put it on discuss