Retrospective and planning after iteration 3¶

Date: 09.04. 2021, 15:00
Present: Jan Pašek, Michal Seják, Stanislav Král, David Friesecký

Agenda¶

1. 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
2. What shall be better in the next iteration?
3. How did we managed to change problematic points from the previous retrospective?
4. Other problems
5. Evaluate if we achieved the iteration targets
6. Synchronization discussion (short standup)
7. Planning of the next iteration

Conclusion¶

1. Evaluation of the iteration:
   • Honza: Targets were met, software architecture was built from scratch which was exhausting work.
   • David: Estimations shall be improved for the future, but it shall be better next time. The rest of the work was OK.
   • Michal: Best iteration, joyful tasks. No other comments.
   • Standa: Big overshoots of the task estimations. Architecture is implemented and ready to be extended.
2. Review process shall be improved. Maybe a walk-through review can be done.
3. Estimations shall be significantly better.
4. Design update process was established.
5. All iteration targets were met
6. _.srl file remains in the project root - serial number handling shall be treated in a different way
7. 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.
8. RestAPI cannot return code 409 - shall be removed from the specification
9. Currently RestAPI enables to create of a certificate signed by a certificate without CA option
10. 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.
11. Treating usages in the whole application was discussed - new issue