FGZ Retrospective

involve team leads to the estimation of tricky tasks/features, approve estimations with the team leads. Explore tasks more carefully and ask questions if there are any doubts

keep tasks in different places (e.g. figma comments, doc files)

Daily calls

save all the pages from figma before starting project (so can check if there were changes). Or ask to clone project to our account – need to discuss

pass to QA till all TO DO and Comments to tasks are not implemented by FE/BE

specify before live
Domain name ________________
Hosting name+type ________________
Hosting CP: ________________
PHP Version: ________________
MySQL Version: ________________
Apache\Nginx: ________________
What access will be shared with us: FTP, SSH, access to the control panel.* If the domain is not added to the hosting, then access to the domain is still required.

involve team leads to the tricky tasks discussion in order to determine the best solution in each specific case.

separate subtasks for blocks? need to discuss the flow (the reason is to make tasks more visible on the board)

functional logic should be done at the beginning, can leave the blocks at the end

even when the CR/Fix is not global one, we need to make QA for all the page/functionality

switching between projects/tasks

Maintain a positive team spirit throughout the project

prepare the list of repeated blocks (during retro we didn’t determine who should make it Front or Back or maybe QA?)

describe in the internal documentation the one and only rule for working with GIT when more then two developers work on one project

when the new QA jump in the project to replace then it’s a must to make a regression test of already QA approved functionality