Sprint 3 (04.04 ‐ 15.04)

Sprint Goal:

Have a segmented road network to remove dependencies in backlog, write the last chapters of report and fix feedback from midterm.

Sprint Planning:

Sprint planning held 04.04.2018, three new tasks introduced to the backlog along with finalizing the last user story from Sprint 2. Definitons of done and How to demo defined for new tasks.

Sprint Demo:

Short demo will be held during meeting with customer 16.04.2018, focusing on the user stories implemented (ID28, ID23, ID27). Did not manage to finish ID24 due to dependencies inside Sprint. Should not plan depending tasks in same Sprint.

Sprint Retrospective:

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

What went well

• Better at breaks
• Better focus and productivity
• Better supervisor interaction
• Better task rotation
• Pair Programming
• Tests
• SPM was quick (but maybe not that precise?)
• We delivered user story #25, #23 & #27

Could have gone better

• Carl + Embrik were stuck on a bug to long
  • Testing earlier while developing
• Story 23 planning, two approaches?
  • Should have made choice earlier
  • No point in making the same task in two ways
• Need more report work from techs regarding the corresponding technical chapters
• More thorough QA
• Communicate vision of story
• We keep estimating incorrectly
• Terje meeting was informative but a little embarrassing, what did we deliver lol
• Story 25 remnants

Ideas for improvement

• Estimate with dependencies
• Better story > task division
• Stricter with cutting ?
• Story 25 bug/Story 23 research
• Milestones and deadlines inside sprints
• QA guide / checklist, bugs are not caught
  • pair QA
• clearer non-code estimate (SPM)
• Tech feedback QA before polish text
• communicate rotation wishes
• @channel QA needs
• Take time to plan/discuss
• SPM more pessimistic

Improvement matrix

Action	Responsible	Comment
Take task dependencies into account when planning Sprint	Team	If we spend the whole sprint implementing the first task we will never start at the depending task => Waste of resources
Divide stories into more and better tasks, spend more time planning how to implement them.	Team	Better planning should result in less errors/complications later.
Plan milestones inside sprints to know when we’re behind schedule	Team	Sprints are two weeks, we should do actions if we are too far behind schedule earlier in sprints.
Plan resources spent for administrative and report assignments, this is time not spent coding.	Team	We have previously known that we had to spend time doing other stuff without defining the amount of time.
Be more pessimistic under sprint planning, we have not delivered on time yet.	Team	We seem to be too optimistic about our pushed back tasks. #25 were estimated 2-3 days into sprint 3 but finalized at last day.

Additional notes:

Last feedback from supervisor are 26th April, report must be delivered Monday 23rd.