Retro Sprint 72

General info

Initiated by	Andrii Kupriianov (PM)
Reason	Finished sprint
Date	02.07.2024
Members	Andrii Kupriianov Ivan Hodoniuk Dasha Rozhniatovska Anton Liakh Anton Poliakov Olexandr Tikan Valya Stelmashenko (Unlicensed) Julia Yurii Tymchuk
Link to the board	Retro Sprint 72 – https://ideaboardz.com/for/Rocken%20Sprint%2072/5321694

Liked	Lacked	Learned	Longed for
The system is more stable, there are fewer bugs It’s great that there are more processes, but it’s important not to overdo it the new internal chat allows us to slowly solve new issues in the team positive atmosphere in the team, everyone is interested in the result I liked the demo I enjoy the transformations in the design file and work with components, as well as the fact that it is slowly synchronizing with the live	A lot of time is spent on deployments A more detailed understanding of certain tasks It’s not always clear when something is needed. It’s obvious that there is some kind of synchronization (especially between design and implementation) We need to improve CRM design, but it’s not clear when It seems that many of the bugs are superficial and could have been caught at the projecting phase Strive to ensure that the design in drafts is relevant to what is being realized	learned more about the project and its specifics	Perhaps a more feature-oriented bugfix, i.e. the result of the bugfix should be a working feature. Somehow to formalize it. If possible, prepare designs of all basic inputs and states used in the redesign

Revise the deployment process. Possible solution: remove tests on gitlab, more powerful runner, etc.
Use comments in the feature and on tickets more often
Break tasks into Epics and finish features, add team members to the epic in the form of sub-tasks
Prepare the design of all elements and all their states – in progress
Separate in the design what is ready for development