We only completed 31 points of the 63 planned (the rest were unplanned): 49%
We added 5 unplanned points, increasing the total number of points on the sprint by 8%
We completed all the unplanned items: 100%
we manage to deliver a total 36 points out of 63 we wanted to do: 57%
we manage to deliver a total 36 points out of 68 (including unplanned): 53%
It looks like we are getting better at estimating, we are having less unplanned and we spend more time in BLISS
The burn down charts:
The sprint retrospective took a little bit longer than planned (1h30m) and the main points were:
Communication within the team is improving
There are less demands from BLs and unplanned items
The stories about discussing and planning were useful
WHAT DIDN'T GO WELL / THINGS WE CAN IMPROVE
The team thinks that we spent too much time in meetings, particularly daily scrum
We should communicate better with stakeholders outside the BLISS developers. How can we get other BCU team members more involved in the project and getting to know the architecture and code?
Time spent on non-BLISS items
Access to hardware can be difficult and takes time
Lack of involvement from the rest of the BCU
MAIN RISK FOR SUCCESS
Challenge when start to have BLISS in production while still developing it. How to manage this, what to put, when and where in production and how to handle support queries that will arise.
Hidden work that we still haven't realised of
Small pieces of work within BLISS that we will find out later
Lack of roadmap (this is in progress)
EXPD and users involvement
The team agreed that given that we do not work full time on BLISS having a daily scrum is a bit of an overload, with many instances when no much progress is reported, therefore the daily sprint will change from daily to 3 times a week: Mondays, Wednesdays and Fridays.
The team agreed to change the daily sprint back to the mornings, at 09:45h.
The team agreed to keep the sprint length as it is for now, to be revisited in January.
The team agreed with a low effort way to keep track of all stories completed in BLISS that are not yet in production. Jordi to document this and maintain it with help from the team.
The team asked for a guide and issue in GitLab for the Scrum Master tasks. Jordi to document this and present it before the end of the next sprint.
Whenever is possible a top priority for the sprint should be named during the sprint planning and the team should make the utmost effort to complete it.
The team agreed that it is useful for big tasks (>=13 points) to book a technical meeting to analyse the work and if possible split it in smaller, less complex stories.