|
|
1st Sprint Review & Retrospective
|
|
|
---------------------------------
|
|
|
|
|
|
**Review**
|
|
|
|
|
|
The 1st sprint review and retrospective took place as planned on Friday afternoon on the last day of the 2 weeks long sprint.
|
|
|
|
|
|
For the review we had Any Goetz as a guest and validated the 3 items completed during the sprint:
|
|
|
* #113 motor_ice_shutter
|
|
|
* #116 transfoc_lenses
|
|
|
* #137 det_mca_core_for_Mercury
|
|
|
|
|
|
We didn't manage to complete all the items in the Sprint Backlog, mostly due to underestimating work to do outside the sprint during the last two weeks.
|
|
|
|
|
|
**Retrospective**
|
|
|
|
|
|
1. There was broad agreement that the sprint planning and the preparatory work for it were good
|
|
|
2. Sprint Reviews are a good way to inform everyone else of what has been completed
|
|
|
3. We started to experience a (small) decrease in disruptions from the beam lines. The team expects that it will take a while to have a significant reduction, however we are moving in the right direction and hope this will continue
|
|
|
4. We decided that the Estimation meeting was one meeting too much on top of the Sprint Planning, daily scrum, review and retrospective so items that we decide to do during the sprint will be instead estimated during the Sprint Planning
|
|
|
5. We agreed that doing *demos* of every single story is not feasible keeping in mind that hardware and BL are sometimes needed. Instead we will have a *validation*. If something can be demoed in the meeting room then a demo will be the validation, during the sprint planning we will decide what validation is suitable for each story
|
|
|
6. Attendance to all the meetings for the Sprint was very good, however we felt that the sprint length was too short keeping in mind other per-existing commitments and interruptions from beamlines, therefore we will extend Sprint length to 3 weeks (from two). We will review this again in the next sprint retrospective as there wasn't full agreement on this aspect (some members of the group preferred 4 weeks)
|
|
|
7. Daily scrum was mostly appreciated (there was a petition to have it every two days instead of daily but the team decided to continue with the daily schedule for now), however we will ensure it takes no longer than 15 minutes (we will cut it short whether we have finished or not after 15 minutes)
|
|
|
8. The initial schedule of the meetings was supported, so we will continue with the daily scrum at 09:45 with Sprint Planning on the first Monday at 09:45 and Review and Retrospective on the afternoon at the end of the sprint
|
|
|
9. The team highlighted that they were disrupted more often than expected / underestimated the interruptions during the sprint and that affected their capacity to deliver all the items.
|
|
|
|
|
|
Overall we support the Scrum process and we will have the next sprint planning next Monday 11th September at 09:45h |