Swimlanes

Swimlanes show in which stage a ticket is. They allow us to track how each ticket is progressing, and also give us a sense of the overall progression of the Sprint and the project.

Swimlanes typically follow the consensus built around Definition of Ready (DOR) and Definition of Done (DOD). The current sequence has been created from the discussions, which took place in Sprint 0 between @sertansenturk and @hedonistrh.

The table below summarizes the swimlanes, and what each ticket has to fulfill to progress to the next lane.

	Summary	Criteria to Move to	Criteria to Keep in	Criteria to Drop From
Epic	All Epics should be in this lane. This lane also gives quick access to filtering tickets by Epic.	Epics should reside in this lane upon creation.	While there are Open tickets linked to the Epic	Move the ticket directly to Closed, if all tickets related to the Epic are Closed. Note that Epics related to a recurring theme (e.g. "Management Tickets") may stay here.
Backlog	Tickets, which are not part within the scope of the current Sprint.	Non-Epic tickets should reside in this lane upon creation.	While the ticket is not within the scope of the current Sprint.	Move the ticket directly to Closed, if the team decided not to work on the ticket (e.g. it is not relevant anymore) in the future.
Sprint Stretch Goals	Tickets, which are to be dealt within the current Sprint after the Spring goals are fulfilled.	When a ticket is added to the scope of the Sprint Goals.	While the ticket is not worked on.	Move the ticket to Backlog, if the team decided to canno make it in the current Sprint.
Sprint Backlog	Tickets, which are to be dealt within the current Sprint.	When a ticket is added to the scope of the Sprint.	While the ticket is not worked on.	Move the ticket to Backlog, if the team decided to drop the ticket from the scope of the Sprint.
In Progress	Tickets, which are being worked on	When a ticket fulfils the DOR and the assignee is starting to work on it.	While the assignee is working on the ticket. Note: Unittests should pass before progressing to Under Review.	Move the ticket to Sprint Backlog, if the assignee temporarily stopped working on the ticket.
Under Review	Tickets, which are being reviewed by the team	When the work on a ticket fulfils the DOD.	While the reviewers request changes, additions etc. from the assignee, within the scope of the ticket.	Move the ticket to In Progress, if the reviewers decide that the work does not meet the DOD.
Integration	Tickets, which are being integrated into the system	When the reviewers approve the ticket.	While the integration tests have not passed yet.	Move the ticket to In Progress, if integration need extra work to be done.
Closed	Tickets, which are completed.	When the integration is complete.	N/A	1) Move the ticket to In Progress, if either an extremely minor addition is needed or a major problem is identified that deems the work as incomplete. 2) Create a Bug Fix ticket, if we have identified some bugs within the scope of the ticket. 3) Create a Feature ticket, if we have identified additional requirements, e.g. the required work exceed the scope of the current ticket.