... | ... | @@ -14,4 +14,6 @@ These were the main points of the retrospective: |
|
|
1. We overestimate the time available for BLISS work in the sprint and at the same time we might be underestimating the size of the stories in the sprints. Left over work from before we started the sprints eventually will dry up and we aim to get better at estimating.
|
|
|
2. We like the idea of public regular BLISS sessions on what has been done and what to focus on next every few sprints.
|
|
|
3. We will formalise a plan for obtaining a road map for BLISS in 2018, however at the moment there is enough work for the rest of the year.
|
|
|
4. We may try out something in the daily sprint to make it more lively. Currently we do not have users attending the Sprint Demo and our Product Owner is a proxy for the real users, so we could shift demos into daily scrum. |
|
|
\ No newline at end of file |
|
|
4. We may try out something in the daily sprint to make it more lively. Currently we do not have users attending the Sprint Demo and our Product Owner is a proxy for the real users, so we could shift demos into daily scrum.
|
|
|
|
|
|
**UPDATE 16/10/2017**: While the burndown chart looks quite bad, it is fair to point out that while some stories where not completed during the sprint (and therefore the points not counted), we were very close to finish them. In fact, a couple of days later stories totaling around 20 points were completed. |
|
|
\ No newline at end of file |