Retro Sprint 87

General info

Initiated by	Andrii Kupriianov (PM)
Date	30.12.2024
Members	Oleksii Fedorchuk Andrii Kupriianov Anton Poliakov Olexandr Tikan Yurii Tymchuk Viktoriia Malysh Anton Liakh Ihor Bushtakov Dasha Rozhniatovska Ivan Hodoniuk Roman Kliuiko Serhii Karashkevych
Link to the board	Retro Sprint 87 – https://www.figma.com/board/7WuCUMVh0dhVsS2Ald6Xgk/Rocken-Retro?node-id=0-1&p=f&t=hfiaFzntKhbPQ96x-0

Liked	Lacked	Learned	Longed for
quick fix even for unplanned bugs sandboxes started The team considers each problem comprehensively, which is very cool designer are working with current tasks from the sprint less bugs CI/CD ready Sandbox ready. Autotests are being written. Great team! It’s great that access for further work of the business analyst is set up	some terms in the project are not clear chaotic change of priorities, lack of estimations bug hunter problems with PDF RJ not in the docker Client-facing issues moved to the next sprint due to changing priorities Add extra data to the Sandbox damp. Would be nice to add some .trim() to email/pass inputs for RT/CRM/Jobs Simplify changing statuses in Jira. In this sprint, these things with changes in requirements are a little unclear whether they are final Mismatch between design and product – design is far “ahead” and there is not enough time to redesign the current system	–	–

Do not take on new tasks in the current sprint after the new architecture is stabilized (management)
non-critical bugs should not be created in the current sprint if they are not related to the tasks worked on in the sprint (PM+QA)
connect jira to the new Sentry (management+administrator)
Bugs and tasks should be with criteria and clear structure
Adjust Jira workflow for non testable tickets
Report problems with pass/email fields (.trim() to email/pass inputs for RT/CRM/Jobs) – dev+QA
Finish redesign of RT