Sprint 1 (12.02 ‐ 25.02) - IT2901-24-2018/vapi GitHub Wiki

Sprint Goal:

The goal is to have a website with a map

  • We did not reach this goal as we did not finish any user stories

Sprint Planning:

We made tasks for the stories 12/2/2018

Sprint Demo:

No official demo held this sprint, however we showed the customer an example page we had made. This resulted in changing which map we will use due to cost.

Sprint Retrospective:

Short summary

  • A lot of sickness
  • A lot of report work and remnants of sprint 0
  • Data confusion with the data from SVV. Clarified later with Johan.
    • In "the_geom" field, each data point had a duplicate linestring. In total there were two linestrings, with each data point having one of the two. We were told by Johan to exclude these linestrings from the application.
    • "vegref" had IDs not corresponding with actual road IDs. An employee later informed us that these IDs change over time.
    • Some fields were in UTM and had to be converted to latlong.
  • Tutorials
    • Django Girls
    • Django Rest Framework
  • Map switching
    • Customer had not read release plan and was not aware we were using Google Maps
    • Google maps is not free when user base increases, SVV are making their own map. Leaflet is a good library for map functions.
    • Trying SVV Map + Leaflet instead of Google Maps API.

General feedback

  • We want to improve the overhead by shortening recap meetings. Set time restraint - 1 min per person
  • Recap every lunch
    • Main purpose is making sure people are making progress
    • We want to improve labeling of tasks by having a guide/how-to in the wiki to make sure everyone are on the same page
  • More in depth planning of tasks, check project board more often
    • Split up into more tasks
    • Use checklist on tasks
  • We want to improve planning and system design by being better to take time off and design our solution before we start coding
  • Keep track of neighbor
  • Be more strict with the customer. Explain in greater detail what we expect from them.
  • Be more active on the wiki, regarding both writing and reading about the project. Includes writing things in the wiki when learning something new, or doing something technical
  • Communicate better the status of the project (to the customer)

What we are happy about

  • Good moral in group, no absence due to shitty excuses
  • Great communication in group
  • Good technical set up for further development
  • Great work with preliminary report

Improvement matrix

Action Responsible Comment
Look at the project board more often Team This makes everyone more updated and prevents redundant work.
Plan how to implement tasks Team Do not run around like a headless chicken, planning makes perfect
Get team members back into focus if they spend to much time surfing the interwebs Team Break are fine, but we should strive to use the working hours at the project
More strict customer relation, make it clear what we expect from them Team, Customer Unstructured meetings does not seem to be very rewarding
Write new knowledge at wiki / update wiki Team This is to provide gathered information to the rest of the team

Additional notes:

No user stories finished, pushed down to Sprint 2. Re-estimating releaseplan based on the delayed tasks.