Goal: Publish a functional MVP proposal
Subgoal that popped up spontaniously: make quick syscon tool for internal use
Achivements main goal:Â Presentable front end, partly functional with backend code including: registration and log in, make groups , make stores
Missing for main goal:Â Most functions connected to functional backend: pick up creation, participate in pick ups, leave groups, have stores in groups, chat backend, chatusers in groups.Â
Bonus: A in the making subgoal of having a quick syscon app for internal use.
Alex
Tasks that i commited to do:
What worked out?
What did not work out?
What will i need to change to make things working out better in future sprints?
Requests i have towards specific other participants in this sprint for future teamwork:
Â
Â
 Joachim
Tasks that i commited to do:
   -make wireframes for yunity mvp proposalÂ
   -hold focus on sprint goal and communicate with sprint participants
   -scrum master for daily scrum
What worked out?Â
-WireframesÂ
 -communicate with sprint participants
 -daily scrum
What did not work out?Â
holding focus on sprint goal...quick syscon tool was too tempting
What will i need to change to make things working out better in future sprints?
make better communication of who commits to do which work and which dependencies come from that > centralization of sprint communication in a well documented way
Requests i have towards specific other participants in this sprint for future teamwork:
   Matthias: Hold focus on current sprint goal (not on future isuues) and communicate with sprintparticipants more clearly what works and what not.Â
Tilmann: Hold focus on current sprint and the active participants(not on future issues and people not participating, have clearer tasks and responsibilities.
Â
 Lars
Tasks that i commited to do:
- - Implement all backend-api functions that are currently working
What worked out?
- - Implementing / designing of the frontend idea
- - Integrating backend functions (even though not everything on the page is working yet)
- - Scrum meetings: great way of beeing up-to-date
What did not work out?
- - Building the frontend-proposal with AngularJs (used jQuery & plain javascript instead)
- - Updating my already running backend to current versions of github (errors renewing databases etc..)
- - personally: "yunity - wide" communication, being more informed about other processes
What will i need to change to make things working out better in future sprints?
- - Communicate even more with backend developers
- - Aim at a more specific goal
Requests i have towards specific other participants in this sprint for future teamwork:
- @all: keep our common goal in mind, especially when communicating with other team members.
Â
Â
 Matthias
Tasks that i commited to do:
What worked out?
What did not work out?
What will i need to change to make things working out better in future sprints?
Requests i have towards specific other participants in this sprint for future teamwork:
Â
 Tilmann
Tasks that i commited to do: (did not track completely, see Trello)
What worked out?
- - Make remove unused code from Backend
- - Implement new endpoints for API and Store
- - Research into frontend frameworks
- - Learning & testing Slack integration for Quick SysCon tool
What did not work out?
- - Open team-wide communication
- - Refactoring & fixing the existing AngularJS frontend
What will i need to change to make things working out better in future sprints?
- - Communication in an open way (be it Trello, Slack public channels or GitHub issues)
- - Short feedback loops, direct response from frontend
Requests i have towards specific other participants in this sprint for future teamwork:
- - @Lars: let's find a communcation channel that others can follow and join in
Â
Â
Thanks to everyone surrounding us making that sprint possible, the people from the Muehle Heichelheim and all the other yuniteers for their support on essential needs.
