Retro Sprint 78

General info

Initiated by	Andrii Kupriianov (PM)
Reason	Finished sprint
Date	24.09.2024
Members	Andrii Kupriianov Ivan Hodoniuk Dasha Rozhniatovska Anton Poliakov Olexandr Tikan Yurii Tymchuk Viktoriia Malysh Roman Kliuiko Anton Liakh
Link to the board	Retro Sprint 78 – https://ideaboardz.com/for/Rocken%20Sprint%2078/5387809

Liked	Lacked	Learned	Longed for
closed more important tasks in the sprint, good progress feeling that we’are moving forward with a release. it seems the most important part for migrations are done	Design are working too much forward from development. So it can be a problem in a future. Lack of planning for the design tasks. To see a bigger picture. Design periodical tasks organization. Technical problem of communication inside the team. relations for process migrations was not identified at the beginning Fullstack tasks optimization sql, slow requests on a new production	creates separated board for design tasks Elastic Search not standard certificate generation process some new types of DNS records	start work with risks during estimations of the user story Setup percentage of code covering tests Work on design task estimation and overall preparation.

We need a plan for the implementation redesign of Rocken Talent (maybe on some separate meeting with the whole team) – post-release activity
For better estimation of big tasks use investigation tickets.
Arrange regular meeting for design tasks. Review ticket structure for design tasks (e.g. sections problem, goal, use cases, etc) – not relevant so far
Create and plan tasks for optimization of production
Create tasks for design documentation
Communication in the team in one environment (see the calendars each other, how to arrange a meetings, etc) – will be later in the Microsoft teams
Pay attention to the code quality, percentage of covering the code by tests. Optimization of test for memory – create a task for percentage of covering the code