SOP of starting a sprint (WIP)

from QA, devs, or product team here We will have a meeting tomorrow

From Detta :

• break down the task into detailed task (not too general)
• PRD and design discussion before sprint planning
• have fixed design and PRD to help qa create the test cases early
• inform qa if there is / are change(s)
• give label to task as small / medium / large based on effort / time to help qa estimate test time

From Andi :

• maybe at sprint planning little talk about task and assign to someone capable (also due date)
• after sprint planning we can just have discussion about the task in team, so it will more detail and help new member to begin work in that day we can just have a meeting to start the sprint (dedicated half day or one day to plan and discuss)

From nesya:

• on sprint planning please disscuss about API Contract too, like if there is a change on 1 API please breakdown the payload and the Response so from BE and FE already have agreement about what will they changes before they work on it.
• Maybe the sprint planning doc can be shared 1 day before the meeting so engineering team can read and understand it first, before sprint planning meeting. and they can discuss the API Contract on sprint planning meeting
• When we start print planing it means the design, requirement, and the API Contract was locked so from engineering or product team can’t change it when the sprint is running.