SCRUM is an agile project development methodology made for a flexible software development process.
For more information of SCRUM basics, see -> https://www.scrum.org/
# Our SCRUM
Our SCRUM Process is modified to the strict origins as we have a special situation.
Reasons why we differ:
* Remote work
* Part time work
* Lots of stakeholders
* Less of (current) dev-team members
## Sprints
Our sprints have a length of 21 days.
They start and end on Wednesdays.
We are using the https://git.wechange.de/code/redesign/-/wikis/SCRUM%20Meetings Planning, Review and Retrospective - and Standups.
## Storypoints
Within the SCRUM process we use storypoints to estimate the complexity of issues, in GitLab it's called weight. The estimation will be done within the sprint planning or the sprint refinement. It is not about estimating working hours, but about getting a feeling for the complexity of an issue.
After the estimation the storypoints are stored within the issue as issue weight.
### How are story points assigned?
Assigning story points is a team task.
### Poker scale
We use the following scale:
* 1
* 2
* 3
* 5
* 8
* 13
* 21
* 40
The storypoints could not be converted to a certain amount of hours, but there is a rough conversion possible.
one working day is roughly 4 hours
* 1 -> less than half working day
* 2 -> about one working day
* 3 -> more than one working day
* 5 -> about one week, 5 days - maybe less
* 8 -> at least one week - maybe a bit more
* 13 -> about 2/3 of a sprint, 10 days
* 21 -> about one sprint, ca. 15 days
* 40 -> more than one and a half sprint
* 100 -> too big, several sprints - needs division
## Special occasions
### How to deal with new tasks that arise while working on one ticket?
Talk within the dev team or talk to the POs. Issue weight from the planning poker should not be changed. Increasing is possible, we will see this in the burndown for a ticket or the sprint. If a lot more work or tasks are necessary, please consider creating a new related ticket for the additional work.
### Who is creating the new ticket?
New tickets could be created either by the dev team itself or by the POs.
## DoD Definition of Done
Basically we have two definitions of done. One for the Dev process within the sprint itself and one for the deployment to production.
DoD in sprint: deployed on test environment (if possible) and passed QC by the POs
