Drafting of Figma prototyped pages in React - it looks much better than in Figma;
More structured customer session organization - notes taking during the meeting;
Understanding major roles and responsibilities of each team member - separating github work with requirements prototyping;
Problems encountered
Generated frontend code requires time to refactor to be maintainable and consistent. Solution: improve prompts, understand the design and general architecture of the website - still in progress of solving;
Team unsyncronized on the responsibilites and vision of the development. Solution: we conducted an additional team meeting for synchronization to disscuss all the roles and product vision;
Changes for next Sprints
High impact: roles distribution - one team member will focus on managing github project (tables, backlog, tasks, etc.), another on requirements engineering, documentation and communication in team, others: backender and frontender mainly;
Medium impact: introduce development branches for backend and for frontend with further potential staging branch to merge them in - at the end of sprint merge to main;
Low impact: instruct all team members to check headers of md files in docs folder for proper static pages generation;