Weekly standup nr 3 » Historie » Verze 5
Jan Pašek, 2021-04-03 14:27
| 1 | 1 | Jan Pašek | h1. Weekly standup nr 3 |
|---|---|---|---|
| 2 | |||
| 3 | *Date:* 02.04. 2021, 13:00 |
||
| 4 | *Present:* Jan Pašek, Michal Seják, David Friesecký, Stanislav Král |
||
| 5 | |||
| 6 | h2. Agenda |
||
| 7 | |||
| 8 | # Current progress - each of us 3 minutes |
||
| 9 | # Branch naming conventions |
||
| 10 | # Responsibility for analysis before the implementation starts |
||
| 11 | # How to handle design changes |
||
| 12 | 2 | Jan Pašek | # Testing vs Implementation classification of issues. |
| 13 | 1 | Jan Pašek | |
| 14 | h2. Conclusion |
||
| 15 | |||
| 16 | 5 | Jan Pašek | # Based on the experience of Stanislav and David, the estimations for implementation issues were underestimated. In the next iteration, the estimations shall contain a larger buffer. |
| 17 | # The faced problems caused by insufficient analysis before the implementation started. However, the conclusion is that it was caused by the fact that at the beginning of the first implementation iteration, we implemented large pieces of code from scratch. Probably these problems will disappear and no process improvement is needed. |
||
| 18 | # Desing updates will be done on one branch, that is created for each iteration. Synchronization mutex in MS Teams will be used. Supporting classes/methods can be left out of the design. Public methods and parameters shall be kept updated in the main classes in the design so that the main interfaces are known. |
||
| 19 | # Current progress is ok. All iteration targets are feasible. |