Quick Link to NORESM scrum

1. Oslo and Bergen can easily see what the others are working on
2. Better traceabilty of code changes (an issue can contain a reference to a code change)
3. Better work planning
4. Better communication between developers
5. Help us work as a team, not just a collection of individuals.

1. In github: Go to the “issues” tab. Sort by milestones or labels to see the ones you are interested in

1. Go to “create issue”. Note that in NorESM, the issues are different components. Make sure you select the right component for your issue.
2. Also add other information to the issue as label (can be e.g. be a project-name). Adding Multiple labels is OK.

1. Blocker: We need to solve this immediately. Some project can not be delivered because of this problem. Problem blocks other people from working.
2. Critical: Should be solved as quickly as possible. Major problem with product functionality.
3. Major: This is the default priority
4. Minor: Nice to do this, but not really necessary
5. Trivial: Fix this when you have the time
6. Not prioritized: We don't need to do this

1. Find out together with your team which issues are most important
2. Try to compose a sprint so that the product (NorESM) is more or less usable at the end of the sprint.
3. If a task requires more than 3 days of work, it should probably be splitted into sub-tasks. Create an story (or epic) and convert the issues into sub-tasks of the story. Go to issue, more actions and “convert to sub-task”.

1. Every other week, we will create a new “sprint”. That means that the scrum board will be refreshed. (see below)
2. When you want to start working on something you should always do something which is in the sprint. Those are the tasks that the team has defined as most important.
3. Go to the task and choose “assign” and “assign to me”.
4. Also in the task go to “more actions” and “start progress”. You can also just drag the task over in the “in progress” column in the scrum board
5. Drag the issue to the “resolved” column when the problem is solved.
6. You the board to see what your collegues are working on. Comment on their issues!

1. Mention the task when you commit the fix. For example git commit -m “metno/noresm#346: I did something clever” will link the changeset to the right issue in github.