| Date | 16th September |
|---|---|
| Participants | |
| Facilitator |
Action Points:
- Set a code freeze / merge cut-off policy at least one day before sprint end to allow sufficient QA regression time.
- Schedule a technical collaboration session to align on approaches, coding standards, and best practices before sprint start.
- Ensure teams share prioritized stories and capacity details with the Scrum Master before sprint planningIf there are any issues related to the cherry-pick then ream members must highlight merge or cherry-pick risks during refinement or early in the sprint.
- Maintain a centralized troubleshooting guide.
- Capture all requirement changes in writing (JIRA/Confluence). Obtain documented design approval before starting development.
