MAT-U
  • MAT-University
  • Republica
    • Indice
      • Constitución
      • Acerca de Nosotros
        • Marca - Circulo Dorado
        • Ideología Taffer
        • Misión Corporativa
      • La Cultura MAT
        • Valores & Principios
        • Obligaciones & Enmiendas
        • Un Campo de Misión
      • Guías Corporativas
  • Software
    • Indice
      • Discord
        • Instalación
        • Operación
      • Clickup
        • Configurar Tablero
        • Guía de Tickets
        • Etiquetas
        • Gestión de Tareas
      • Figma
        • Diagrama de Flujos
        • FigJam
      • Gitlab
        • Ticket Guideline
        • Labeling
        • Kanban
      • Workflowy
      • Clear Mechanic
  • Lecturas
    • Departamentos
      • Lectura Trimestral
      • Ops
        • Libros
      • Marketing
        • Libros
      • Comercial
        • Libros
        • Podcasts
      • Ingenieria
        • Libros
        • CheatSheet
      • Management
        • Libros
        • Articulos
        • Online Campus
    • Guías
      • 🟡Circulo Dorado
      • *️Trabajo en Equipo
      • 🛣️Las 3Vías
        • ⚙️Operaciones
        • 🛰️DevOps
      • 🏁OKRs
        • 1.1 Porque los OKRs
        • 1.2 Qué es un OKR?
        • 1.3 Lo que hace un buen OKR
        • 1.4 Superpoderes de los OKRs
        • 2.1 Escribiendo tu primer objetivo
        • 2.2 Conectando propósito y beneficio
        • 2.3 Los OKRs no es trabajo de costumbre
        • 2.4 Refinando tus objetivos
        • 3.1 La ciencia de los resultados clave
        • 3.2 Aportes, Producido y Resultados
        • 3.3 De "Bueno a mejor" 1ra Parte
        • 3.4 De "Bueno a mejor" 2da Parte
        • 3.5 Alineando los OKRs
        • 3.6 Ejemplos de OKRs
        • 3.7 OKRs VS KPIs
        • Tips basicos de Dr. Grove
        • Principios de Gestión
      • ☑️Scrum (Ops)
        • Guía
      • 🤖Gestión
        • Paso Limitante
        • 4 Disciplinas de Ejecución
        • Leyes de Gestión
        • Modelos Mentales
        • Grafica Escalonada
        • Organigrama de Gestión
      • Ⓜ️MBM (Eng)
        • Vision
        • I. Virtue & Talent
        • II. Knowledge Processes
        • III. Decision Rights
        • IV. Incentives
        • Tips for MBM
      • 🥶Revisiones
        • Porque son necesarias
        • Momento de Revisión
Powered by GitBook
On this page
  1. Software
  2. Indice
  3. Gitlab

Kanban

PreviousLabelingNextWorkflowy

Last updated 2 years ago

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.

Kanban Flow

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.

  • Done - Final stage where tickets are officially sent to production.

Staging (Sales) - Only for repositories dedicated for , 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 . 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.

Business Projects
Business Projects
Kanban of MAT