Retro New Architecture

 General info

 What needs to be improved in processes (1)?

• Add additional meetings in small groups before refinement
• Involve additional stakeholders to our team meetings
• Add more context and problematic info to the tasks for designers
• Build a processes on how to use glossary of terms

 What needs to be improved in documentation (2)?

• Write DevOps documentation
• Add onboarding and offboarding descriptions
• Use Definition of ready when preparing descriptions and tickets
• Keep up-to-date the descriptions and design before, during and after implementing features
• Involve more team members to update descriptions

 What needs to be improved in team collaboration (3)?

• Unclear topics should be covered better so that no reopens, follow-up bugs and tickets appear
• Introducing the stakeholders into the dev presentations can improve the collaboration
• Everyone should be involved on retrospectives for improvements

 What needs to be improved in management and planning (4)?

• implement process of change management
• switch to story points
• Planning based on understanding why we do things and how it will help users.
• bugs should not accumulate in the backlog in large numbers
• prepare more detail roadmap
• clean up the backlog

 What needs to be improved in visual design (5)?

• Sync storybook and design (list of variables)
• prepare a plan for RT new design implementation

 What needs to be improved in development (6)?

• Introduce team meetings before implementing a big feature like markets/role system before implementing so everyone is up to date
• Move to Vue3

 What needs to be improved in testing and quality (7)?

• Need to make new frontend with tests
• Need to add test coverage and metrics
• Add Test case like TestRail
• Involve QA at the stage of creating a description of tickets, and acceptance criteria (to describe more scenarios)

 What needs to be improved in release and support phase (8)?

• –

 What needs to be improved from our lessons (9)?

• –