Retrospective and planning after iteration 3 » Historie » Verze 16
Jan Pašek, 2021-04-10 14:12
| 1 | 1 | Jan Pašek | h1. Retrospective and planning after iteration 3 |
|---|---|---|---|
| 2 | |||
| 3 | 16 | Jan Pašek | *Date:* 09.04. 2021, 15:00, 10.04. 2021, 09:00 |
| 4 | 1 | Jan Pašek | *Present:* Jan Pašek, Michal Seják, Stanislav Král, David Friesecký |
| 5 | |||
| 6 | h2. Agenda |
||
| 7 | |||
| 8 | # Each of the team briefly evaluates the pros and cons of the iteration based on the following points: project state, project plan, team cooperation, tools, artefacts |
||
| 9 | # What shall be better in the next iteration? |
||
| 10 | # How did we managed to change problematic points from the previous retrospective? |
||
| 11 | # Other problems |
||
| 12 | # Evaluate if we achieved the iteration targets |
||
| 13 | # Synchronization discussion (short standup) |
||
| 14 | # Planning of the next iteration |
||
| 15 | |||
| 16 | h2. Conclusion |
||
| 17 | |||
| 18 | # Evaluation of the iteration: |
||
| 19 | |||
| 20 | 3 | Jan Pašek | * Honza: Targets were met, software architecture was built from scratch which was exhausting work. |
| 21 | 1 | Jan Pašek | |
| 22 | 3 | Jan Pašek | * David: Estimations shall be improved for the future, but it shall be better next time. The rest of the work was OK. |
| 23 | 1 | Jan Pašek | |
| 24 | 3 | Jan Pašek | * Michal: Best iteration, joyful tasks. No other comments. |
| 25 | 1 | Jan Pašek | |
| 26 | 3 | Jan Pašek | * Standa: Big overshoots of the task estimations. Architecture is implemented and ready to be extended. |
| 27 | 4 | Jan Pašek | # Review process shall be improved. Maybe a walk-through review can be done. |
| 28 | # Estimations shall be significantly better. |
||
| 29 | 6 | Jan Pašek | # Design update process was established. |
| 30 | 1 | Jan Pašek | # *All iteration targets were met* |
| 31 | 6 | Jan Pašek | # _.srl file remains in the project root - serial number handling shall be treated in a different way |
| 32 | 7 | Jan Pašek | # GUI - if self-signed is selected, CA shall be checked and blocked. Self-signed certificates are automatically enforced to be CA in the application core. |
| 33 | 8 | Jan Pašek | # RestAPI cannot return code 409 - shall be removed from the specification |
| 34 | 11 | Jan Pašek | # Currently RestAPI enables to create of a certificate signed by a certificate without CA option |
| 35 | # If an unknown usage option is passed to the application core from the controller, the unknown usage is stored in the database as a string. |
||
| 36 | 14 | Jan Pašek | # Treating usages in the whole application were discussed - new issue |
| 37 | # Rest API - response code 204 shall be replaced with an empty list or 404 response |
||
| 38 | 15 | Jan Pašek | # In case of an error in the application code, an exception is thrown. The exception type shall explain what happen and the controller will translate the type to the error message. |
| 39 | # Next iteration was planned. |