Retrospective and planning after iteration 3 » Historie » Revize 12
Revize 11 (Jan Pašek, 2021-04-09 13:13) → Revize 12/16 (Jan Pašek, 2021-04-09 13:13)
h1. Retrospective and planning after iteration 3 *Date:* 09.04. 2021, 15:00 *Present:* Jan Pašek, Michal Seják, Stanislav Král, David Friesecký h2. Agenda # 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 # What shall be better in the next iteration? # How did we managed to change problematic points from the previous retrospective? # Other problems # Evaluate if we achieved the iteration targets # Synchronization discussion (short standup) # Planning of the next iteration h2. Conclusion # 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. # Review process shall be improved. Maybe a walk-through review can be done. # Estimations shall be significantly better. # Design update process was established. # *All iteration targets were met* # _.srl file remains in the project root - serial number handling shall be treated in a different way # 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. # RestAPI cannot return code 409 - shall be removed from the specification # Currently RestAPI enables to create of a certificate signed by a certificate without CA option # 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. # Treating usages in the whole application was discussed - new issue discussed.