|
|
End of 4th Sprint
|
|
|
------------------
|
|
|
|
|
|
The 4th sprint took place from 13/11/2017 to 01/12/2017 (3 weeks).
|
|
|
|
|
|
The **sprint review** and **retrospective** took place on Friday 1st December as planned. Demos during the review took 1 hour as planned and all completed items were shown.
|
|
|
|
|
|
| **Priority** | **Story** | **Points** | **Completed** |
|
|
|
| ------------ | --------- | ---------- |-------------- |
|
|
|
| Continuation | #105 Kb Focus | 5 | |
|
|
|
| Continuation | #156 P201 in scans| 13 | 01/12/2017 |
|
|
|
| Continuation | #172 Refactoring data handling| 13 | |
|
|
|
| | #140 1D Data handling | 8 | 23/11/2017 |
|
|
|
| | #132 motor symhexa v1 | 3 | |
|
|
|
| | #133 motor pi e712 | 5 | |
|
|
|
| | #165 Data file not always closed | 2 | 29/11/2017 |
|
|
|
| | #173 MCA: further design specs | 5 | 30/11/2017 |
|
|
|
| | #175 Discussion about "session" | 3 | 30/11/2017 |
|
|
|
| | #174 hardware init discussion | 3 | |
|
|
|
| | #177 Scan info dictionary & watch session scans | 3 | |
|
|
|
| U 21/11/2017 | #180 Banner when BLISS starts | 1 | 28/11/2017 |
|
|
|
| U 22/11/2017 | #181 'Pip install' doesn't work | 2 | 24/11/2017 |
|
|
|
| U 28/11/2017 | #182 Improve musst controller | 1 | 28/11/2017 |
|
|
|
| U 30/11/2017 | #183 No subdirectories allowed in motor scans | 1 | 30/11/2017 |
|
|
|
| | **Planned Total** | **63** | 31 |
|
|
|
| | **Unplanned Total** | **5** | 5 |
|
|
|
| | **Grand Total** | **68** | 36 |
|
|
|
|
|
|
| Team Member | week 1 | week 2 | week 3 | **Average**
|
|
|
| ------------------ | ------ | -------- | -------- | --------
|
|
|
| S. Petitdemange | 30% | 20% | ??% | **25% estimated**
|
|
|
| T. coutinho | 90% | 30% | 40% | **60%**
|
|
|
| C. Guilloud | 50% | 50% | 60% | **50%**
|
|
|
| V. Michel | 40% | 10% | -------- | **25%**
|
|
|
| M. Guijarro | 20% | 20% | 30% | **20%**
|
|
|
| E. Papillon | 80% | 70% | 80% | **75%**
|
|
|
|Total non-BLISS | 310% FTE | 200% FTE | 210% FTE | **47%**
|
|
|
|
|
|
As we can see,
|
|
|
* 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%
|
|
|
![image](/uploads/fc2a9e3fe49dfa7ab9636ffbdc0599d8/image.png)
|
|
|
* 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**:
|
|
|
![image](/uploads/137c4402c17ebd710c115e356130c2ea/image.png)
|
|
|
![image](/uploads/a202195e929799095fb49d01d28bf5fd/image.png)
|
|
|
|
|
|
The **sprint retrospective** took a little bit longer than planned (1h30m) and the main points were:
|
|
|
|
|
|
WENT WELL
|
|
|
1. Communication within the team is improving
|
|
|
2. There are less demands from BLs and unplanned items
|
|
|
3. The stories about discussing and planning were useful
|
|
|
|
|
|
WHAT DIDN'T GO WELL / THINGS WE CAN IMPROVE
|
|
|
1. The team thinks that we spent too much time in meetings, particularly daily scrum
|
|
|
2. 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?
|
|
|
|
|
|
MAIN IMPEDIMENTS
|
|
|
1. Time spent on non-BLISS items
|
|
|
2. Access to hardware can be difficult and takes time
|
|
|
3. Lack of involvement from the rest of the BCU
|
|
|
|
|
|
MAIN RISK FOR SUCCESS
|
|
|
1. 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.
|
|
|
2. Hidden work that we still haven't realised of
|
|
|
3. Small pieces of work within BLISS that we will find out later
|
|
|
4. Lack of roadmap (this is in progress)
|
|
|
5. EXPD and users involvement
|
|
|
|
|
|
CHANGES
|
|
|
1. 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**.
|
|
|
2. The team agreed to change the **daily sprint back to the mornings, at 09:45h**.
|
|
|
3. The team agreed to **keep the sprint length** as it is for now, to be revisited in January.
|
|
|
4. 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.
|
|
|
5. 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.
|
|
|
6. 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.
|
|
|
7. 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. |