Kanban
Last updated
Last updated
Kanban is a visual system used to manage and keep track of work as it moves through a process. The word kanban is Japanese and roughly it means “card you can see.”
Key Take Aways
Repositories dedicated to Business Projects (Business) should have Staging (Sales) and Launch stages.
The QA engineer should notify the Ops team when a new feature is ready for testing in Staging (Sales).
The Ops team should be highly involved in coordinating the launch of a feature. They have the power to decide when to launch.
In gitlab we have 10 different columns/lists that make up the Kanban process for MAT Enterprises.
Open - Ideas that are not clearly structured as a ticket.
Planning - Ideas that are being structured into a ticket SPRINT.
Sprint - Tickets assigned for the weekly or bi-weekly sprint.
In Progress - Tickets that the developer is working through the sprint.
Coded NOT Ready for MR - Tickets finished by developers but not ready for merging.
Merge Request - Tickets on merge request are pending for code review from an assigned engineer or CTO.
QA - Tickets going though Quality Assurance.
Staging (Sales) - Only for repositories dedicated for Business Projects, eg. Android User, iOS User, Flutter Driver, Verifik Client Panel, Verifik Admin Panel. Ticket tested for UX and quality assurance by ops team. At this stage the engineer involved in QA must provide a staging app to the sales team so they can test the new features, so then they (sales and devs) can coordinate when to launch the feature on the upcoming release.
Launch - Only for repositories dedicated for Business Projects. eg. Android User, iOS User, Flutter Driver, Verifik Client Panel, Verifik Admin Panel. Number of tickets previously accepted by Sales team and ready for version update. The Sales team must coordinate with the DevOps team to launch on a specific date. The Sales team is responsible for the launch of the new feature.
Done - Final stage where tickets are officially sent to production.
