The workflow being used for Frontend team when working on CMS is "Main Workflow for FE Development Team". Diagram and Kanban board are below.
BACKLOG
Any new ticket is created in Backlog.
These tickets stays there for grooming until all required information is added.
- Any ticket at any stage can be move back to Backlog if its development is decided to put on hold.
SELECTED FOR DEVELOPMENT
- Base on team capacity, tickets which are ready will be moved to SELECTED FOR DEVELOPMENT column.
- These tickets will then be assigned to developers accordingly.
IN PROGRESS
- The ticket is under development.
- Developers need to select "Start work" to update ticket status when they actually work on.
READY FOR TESTING
- The development for the ticket has been completed.
- Ticket is assigned to QC Leader to be pushed to Test environment.
- Developers need to select "Complete Development" to change to this status.
TESTING
- The ticket has been pushed to Test Environment.
- Ticket is assigned to a QC for testing.
- After having the ticket deployed, QC Lead select "Deployed to Test" and assign to a QC to start testing.
- If the ticket is failed, QC can select "Reopen" under Workflow option to put it back to "Selected for Development" status and assign to Developer.
READY FOR GOLIVE
- Ticket has passed QC and waiting for approval for Go Live.
- Once done testing, QC selects "Tested" under Workflow option to move to this status and assign back to Reporter for approval.
- If the ticket is not approved, reporter (CM) can select "Reopen" to put it back to "Selected for Development" status and assign to Developer.
DONE
- Ticket is completed and pushed to Live environment.
- Once it is deployed to Live environment, QC Lead can close it by selecting "Deployed to Live" under Workflow option.
- For some reason, if the ticket needs to be re-worked, reporter (CM) can select "Reopen" to put it back to "Selected for Development" status and assign to Developer.
Add Comment