Skip to main content

Trello Workflow

This document briefly describes the process we follow in Trello and how Trello and AirFocus work together

Epics​

Product team will create and track epics in AirFocus. These epics will be automatically synched to the Next Epics list in the Backlog board in Trello.

We will not sync cards or epic status back to AirFocus for the time being.

Trello Backlog Board

Engineering will be able to view the Backlog board to see which epics are coming next, Epics will be listed in priority order.

When engineering are ready to plan further work we will take the highest priority epics and move them to the In Progress Epics list. We will then plan the epics and create linked cards in the next sprints board. When we add a card we will link to it an epic, epic progress is then tracked automatically within Trello as the linked cards are moved to the Done list.

If backend are working ahead of front end, but the epic requires both FE and BE work, BE should create a placeholder ticket for the FE development so the epic is never marked as complete before it is actually complete.

Sprint Boards​

We will create a new board for each sprint and both FE and BE will work within the same board. Each planning session will be planning epics and cards in the next sprints board so its ready in time for the start of the next sprint. This will allow us to easily see whats coming next.

We will continue to use the same Kanban lists in our sprint boards as below

Trello Sprint Board

When a card is moved to the Done list the linked epic card will have its progress updated. Once all cards linked to an epic are marked as done the epic will show 100% complete, but we will need to manually move it to the Complete Epics list. At this point it will no longer be considered an epic, this is so it no longer shows up in the list when linking cards to an epic.

Story pointing​

We are using the Card Size power up to allow us to track storypoints for cards. During planning sessions we will run the planning poker sessions within Trello and update the card sizes as we work through the cards in the next sprint.

Labels​

All backend tickets should be labelled with the BE label and front end tickets with the FE label. In addition we currently have a Bug label for bugs and a High Priority label.