Handbook

# Kanban Board

# The board

We have one single Kanban board (opens new window). The Board contains several parts:

  • Filters. You can leave only your cards on the board. Removing filter, you'll get a full picture on what we all working on.
  • Columns.
    • Column Not Ready shows what tasks we scheduled to do.
    • Column In Progress shows what we're working on right now.
    • Column Ready for things that are ready to deploy or just not confirmed.
    • Column Done shows what we did.

TIP

Jira keeps cards for 2 days in column Done, then the cards moves to status Closed.

# Working on a Story

  • Push a card from Story Map to Jira.
  • If Story is about adding new feature or making significant change, it's recommended to write RFC first.
  • Decompose Story to sub-tasks. If Story is very simple, you can skip that step.
  • Move Story to In Progress state.

TIP

We name our git branches by Story ID. For example, TR-9921.

# Sub-tasks

  • Keep sub-tasks small, but not too small. Try to spend 2-4 hours on each task.
  • You can add sub-tasks at any moment.

# Before moving Story to Ready

  • Create Merge-Request if needed.
  • Perform a demo of a change to CS Team.

# Before moving Story to Done

If it's a dev Story:

  • Make sure the code is merged to upstream and feature deployed.

For other stories:

  • Ask yourself if something else needed. If not, move it Done.

# How we deal with Bugs

If bug blocks customer work, we fix them right away. If not, we postpone them until next Bug Day

# SUPPORT tasks

These tasks are intended to be solved ASAP.

# How to create SUPPORT task

  • Press "Create" on the navigation bar or enter /jira create in any slack channel.
  • Write issue summary. Be precise what happened.
  • Write description. Try to describe how to reproduce the problem.
  • Copy CarrotQuest link.
  • Leave Assignee field free, unless you know who's going to take that task.

TIP

Every morning we publish a digest with all SUPPORT tasks. These tasks have the highest priority.

← RFC →