---
# System prepended metadata

title: Scrum'n it with GitLab

---

# Scrum'n it with GitLab

## GitLab Artifacts

### Iterations

Define an iteration for each sprint. Iteration 1, Iteration 2, and so on.

### Issue Boards

* **Sprint planning** - Columns are iterations. Over time, you'll need to add and remove iterations.
* **Current sprint** - Scoped to the current iteration. Columns that support your team's workflow: for example, "Doing" and "Needs Review".

### Epic Boards

If you have a lot of epics, consider creating a board or two to help you organize them.

One board might organize them by level of abstraction: with columns E1, E2, and E3 for the highest, midrange, and lowest level of abstraction respectively.

Another board might mimic that of a product backlog.

### Wiki

Use a wiki to store your team's meta data: e.g., working agreements, retrospective summaries, etc.

## Scrum Ceremonies

### Daily Scrum

* Answer the classic questions.
* Update the health status of issues.

### Iteration Review

* On the current iteration board, review and update each issue.
    * Documenting the status of each issue.
    * Move issues to close that are done.
    * Open new issues as necessary.
    * (***Don't*** move unfinished issues to open.)
* On the epic board, review what was completed in the current iteration in the context of epics, and update epics' progress appropriately.

### Retrospecitive

* Select a fun retrospective format.
* Save the result of the retrospective to wiki page for the iteration.

### Storytime/Backlog grooming

* Before the meeting, review and reprioritize epics.
* Before the meeting, review and reprioritize issues.
* Review the new priorities.
* Process high priority issues/epics.
    * Weigh issues to help illuminate assumptions, start discussions, and identify issues/epics that need to be broken down.
    * Break down big issues/epics into smaller issues.
* Prepare 1.5-2.0 times the the team's velocity (in story points).

### Planning

* On the iteration planning board, assign issues to the new current sprint up to the team's velocity (and possibly a streach issue).
* On the current iteration board, review each issue. Nail down the details of what to do. Make to do lists or more issues as needed.

