CMS Development Process

Owned by Khai Huynh
Last updated: Jun 05, 2018

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.


  • Once done, developers click on "Complete Development" to change the ticket to "In Review" status.

IN REVIEW

  • The development for the ticket has been completed.
  • Ticket is assigned to Team Leader to review and push publish required files.
  • If the ticket needs to be reworked, click on "Reopen" under Workflow to move it back to previous status.


  • If the ticket is developed correctly, select "Reviewed" under Workflow after having it push published to change to "Ready for Testing"


READY FOR TESTING

  • The ticket has been reviewed and push published.
  • It is now assigned to QC Lead to deploy to Test Environment for testing.
  • Once deployed to Test Environment, click on "Deployed to Test" to change ticket to "Testing" status and assign to a tester to execute.

TESTING

  • The ticket has been pushed to Test Environment.
  • Ticket is assigned to a QC for 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.



  • Once done testing, QC selects "Tested" under Workflow option to change ticket to "Ready for Golive" status and assign back to Reporter for approval.

READY FOR GOLIVE

  • Ticket has passed QC and waiting for approval for Go Live.
  • If the ticket is not approved, reporter (CM) can select "Reopen" to put it back to "Selected for Development" status and assign to Developer.



  • Once it is confirmed by CM, ticket is deployed to Live environment, QC Lead can close it by selecting "Deployed to Live" under Workflow option.

DONE

  • Ticket is completed and pushed to Live environment.
  • 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.