Sprints
- Our sprints are two weeks long, starting on Wednesday and ending on Tuesday.
- We structure our work into projects of 4 sprints, followed by a one-week cool-off sprint for planning and bug fixes.
- Here is how our sprint is structured:
- We have a sprint planning meeting on Tuesday (day -1) where we focus on the outcomes of each sprint.
- Start the sprint on day 1 (Wednesday)
- We demo the features on the second Friday (day 8) of the sprint and gather feedback.
- Spend Friday to Tuesday working on the release any minor changes and planning the next sprint.
- We Release and deploy on Monday morning.
- Other than that we try to have a focus day for everyone (Wednesday) where we have no meetings other than the standup and try to focus on large tasks without disturbanece
- We have a retro in the cool-off sprint at the end of each four sprints.
Definition of Done
An issue is done when:
In summary, any feature that has anything to do with the developer workflow needs to be documented as part of the PR. See more details in the Link.
It is properly communicated
Mahmoud is notified about the change in Slack with a short description (and in the case of UI, a screenshot) of the change that he can use in the changelog and social media.