Trello Workflow
Trello is an agile-based task management system used for asynchronous team communication and task management. This is where issue tracking, feature suggestions and enhancements are currently kept.
Our Trello workflow consists of multiple boards, explained below
The Doubtfire Backlog Board is the Product Backlog for Doubtfire. It aims to outline all tasks in Doubtfire's backlog horizontally. Each column is described as thus:
- Inbox - New general tasks people think of should be added here. Product owners will then prioritise them.
- Quick and Easy - Quick and easy fixes for anyone to pick up
- Top Priority - Tasks that need to be completed ASAP, such as critical bugs
- High Priority - Tasks that need to be completed which have high importance, such as bugs
- Medium Priority - Tasks that should be completed soon, such as new features or enhancements
- Low Priority - Tasks that would be nice to have done eventually, such as small UI beautifications
- One Day - Ideas that would be great to have one day if we had the time, essentially tasks that are currently too out of scope
- Maybe... - Ideas that are still being considered
- Sprint Backlog - Tasks involved over an upcoming time-fixed sprint moved from the Doubtfire Backlog board - essentially the current sprint backlog
- In Progress - Tasks that are currently in progress. These tasks must be assigned to whoever is working on them
- In Testing - Where relevant, tasks move into this column if unit or integration testing is needed on that task (e.g., a new API endpoint should have unit tests written). These tasks should be assigned to whoever is writing the tests for the task
- In Internal Review - Tasks that are to be reviewed internally by another team member. These tasks should be reassigned to the reviewer
- In Open Pull Request - Tasks that have been put into a Pull Request and assigned to a product owner for external code review. These tasks should be reassigned to the external code reviewer.
-
Done - When the task is merged into the
developbranch (the Pull Request has been closed).
This workflow is used to guide team members on how to use Trello for their day-to-day activities whilst working on Doubtfire.
The workflow also complements the Doubfire Git Workflow, meaning that all changes made will be pushed into the primary develop branch on the Doubtfire product workflow for improved continuous integration.
In this step, team members will go to the Doubtfire Backlog Board and find (or create with the Product Owner's permission) tasks that are relevant for the current sprint.
Once they have found a card, they can move it directly to the Helpdesk Ticketing System Board's Sprint Backlog column. To do this, they can click on a card and them move it:
Once the card is in the backlog on the Helpdesk Ticketing System Board, it will be progressed throughout the board (moved toward to the right hand side of the board) to describe its process by dragging and dropping it between columns:
When the card is ready to start on, progress the card from the Sprint Backlog to the In Progress column.
It needs to be assigned to whoever is working on the card. To do so, click on the card and assign the task to a team member:
If the card requires testing to be done, progress the task from In Progress to In Testing.
When the person working on the card thinks the card is ready, they should run a code walkthrough with someone else in the team.
Progress the task from In Testing or In Progress to In Internal Review and sit down together with the team member. Walk the other team member through both the functionality changes added, as well as the code that has been added. This ensures for optimal product quality and code quality by having a second set of eyes look over the code.
When the code review is over, remove the other team member from the members list of the card.
As through the Doubtfire Git Workflow a Pull Request should be submitted to the Product Owners (i.e., the doubtfire-lms repository) when ready for external review.
Progress the card to In Open Pull Request from In Internal Review when the pull request has been submitted and assign the Product Owner (e.g., Andrew Cain) to the card (if applicable).
Progress the card from In Open Pull Request to Done only once the changes made from the card have been merged and the Pull Request is closed. The assigned task member can be removed from the card at this point.