Versions Compared

Version Old Version 1 New Version Current
Changes made by

Khai Huynh

Khai Huynh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The workflow being used for Frontend team when working on CMS is "Main Workflow for FE Development Team". Diagram and Kanban board are below.

Image RemovedImage Added Image RemovedImage Added

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.

...

  • 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.

Image Added

IN REVIEW

  • 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.

Image Removed

  • 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.

Image Added


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

Image Added


READY FOR TESTING

  • The ticket has been pushed to Test Environmentreviewed and push published.
  • Ticket It is now assigned to a QC Lead to deploy to Test Environment for testing.
  • After having the ticket deployed, QC Lead select Once deployed to Test Environment, click on "Deployed to Test" to change ticket to "Testing" status and assign to a QC tester to start testingexecute.

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.


...


  • Ticket has passed QC and waiting for approval for Go Live.
  • Once done testing, QC selects "Tested" under Workflow option to move to this 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.


DONE


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

...