Sprint 2 (26.02 ‐ 18.03)

Sprint Goal:

Have a website with a map and weather data, deliver about fullworthy report for feedback

Sprint Planning:

SPM meeting held 26th of February. Re-estimated releaseplan with several tasks pushed back.

Sprint Demo:

Short demo will be held in meeting with customer 06.04.2018, focusing on the user story implemented (taking input from production data and storing this data).

Sprint Retrospective:

In our Sprint retrospective held 16.03.2018 we discussed what we felt had gone good, bad and possible improvements.

What went well

• Organizing of our project
• Focus factors
• Project board (better at updating)
• Customer interaction (stricter)
• "Hour debt" (we introduced it so people cannot leave early without contributing enough)
• Comments in the report (regarding the text, possible improvements etc.)
• Better knowledge regarding the report in the group, all members had contributed in the writing.
• We delivered our first user storty #28

Could have gone better

• "Hour debt" (should have a set time to "pay" back to the group. We are all Lannisters.
• Supervisor meetings (we had some misunderstandings hence wasting time discussing when we agreed)
• Homework (we did set to short time frames for tasks to be done at home)
• Better task distribution
• Knowledge spread (code base)
• Communicate report status/needs
• Stop breaks (we tend to chill for to long)
• Report issues are inconsistent
• Rotate tasks (all members should code, not only a few)

Ideas for improvement

• Make ourself understood with our supervisor
• Whip neighbours when they chill for too long
• Homework planned earlier (24h is not sufficient)
• Slackbot reminder for breaks
• Communicate better status/needs in the report
• Poke at others for report QA, do not just move card to QA
• Rotate tasks

Improvement matrix

Action	Responsible	Comment
Try to be more clear when discussing with our supervisor. Do not get irritated by misunderstandings.	Group, Supervisor	Mostly group, should be more understanding and clearer ourselves
Rotate tasks in between members	Group	All members wish to code, knowledge should be spread amongst all members
Reduce "hour debt"	Group	Debt shall be paid within two weeks
Whip neighbour	Group	If you see that someone does not work when it is not break, get them back in focus
Homework needs to be given further in advance	Group	There should at least be one work day between given assignment and due date.

Additional notes:

It is important to deliver the mid-term report before 18. march due to feedback from supervisor.