--- url: 'https://metadrop.net/en/methodology/agile-kanban-board' title: 'Agile Kanban Board | Our Project Methodology' author: name: Root url: 'https://metadrop.net/es/sobre/metadrop' date: '2019-05-26T11:49:04+00:00' updated: '2026-06-29T09:39:58+00:00' type: article summary: 'See how Metadrop runs Drupal projects on a Kanban board: columns, WIP limits, QA gate and KO loop for predictable delivery. See how.' image: 'https://metadrop.net/sites/default/files/styles/full/public/2026-06/agile-kanban-board.webp?itok=YzQW-4TP' published: true og: determiner: Automatic site_name: Metadrop street_address: 'Calle Manuel Luna, 12, 3 Dcha' locality: Madrid region: Madrid postal_code: '28020' country_name: España email: hola@metadrop.net phone_number: '910053180' schema: '@context': 'https://schema.org' '@graph': - '@type': Organization '@id': 'https://metadrop.net/#organization' url: 'https://metadrop.net/' name: Metadrop sameAs: - 'https://www.drupal.org/metadrop' - 'https://twitter.com/metadrop' - 'https://asociaciondrupal.es/partner/metadrop' - 'https://www.linkedin.com/company/metadrop' logo: '@type': ImageObject url: 'https://metadrop.net/themes/custom/mdrop_radix/logo-metadrop-500-500.jpg' width: '500' height: '500' - '@type': ItemPage '@id': 'https://metadrop.net/en/methodology/agile-kanban-board' breadcrumb: '@type': BreadcrumbList itemListElement: - '@type': ListItem position: 1 name: Home item: 'https://metadrop.net/en' publisher: '@type': Organization '@id': 'https://metadrop.net/#organization' --- # Agile - Kanban Board Metadrop's Kanban board defines task states, WIP limits, and a QA quality gate across every Drupal project delivery cycle for predictable, transparent results. [Talk to our team](https://metadrop.net/en/contact)[Explore](#scroll-to-content) Metadrop runs every Drupal project on an *agile Kanban board*, a visual workflow that moves each task through defined states with strict work-in-progress limits and a quality gate. Digital and IT leaders get predictable, transparent delivery rather than black-box development. ## What a Kanban board is and why we use it A *Kanban board* is a **visual workflow** that shows every task and its current state, from request to production. Anyone looking at the board can see **what is being worked on right now**. We use it because it makes delivery **predictable and observable**. Stakeholders track real progress without status meetings or chasing updates. For Drupal projects, **columns, WIP limits, and exit criteria** map directly to how code moves from a backlog item to a live, deployed feature. The board is the operating layer beneath our agile delivery: *Scrum ceremonies* set the cadence, and the Kanban board governs the **flow of work** day to day. Talk to our team See how our governed Kanban delivery gives you predictable, transparent Drupal projects. [Talk to our team](#contact) ## The Metadrop board: from Backlog to Done A task crosses six columns in order. Each column has a clear **entry and exit criterion**, so a card never advances until it has earned the next state. The lifecycle below shows how a request becomes a live, deployed feature without skipping a checkpoint. ## The board column lifecycle Each card moves left to right through these six states, earning the next column at every step. 1. ### Backlog Holds documented, prioritized tasks and user stories with **acceptance criteria** set, ready to be estimated and pulled into a cycle. 2. ### To Do Holds cards approved to start. **No work has begun yet**, so they can still be swapped for equally-pointed backlog items if priorities shift. 3. ### In Progress Holds cards in active **development pending delivery**, plus any rejected (*KO*) cards being corrected and resubmitted for re-check. 4. ### QA Holds cards in **validation** that have passed automated tests (*Behat*, *Unit*, *static analysis*) and the team's **internal review** before anything is shown to the client. 5. ### Deploy Holds cards **approved to ship**, queued for release to Production. 6. ### Done Holds cards **finished and deployed** to Production. ## WIP limits: why we cap work in progress ### Caps work in progress A *WIP limit* caps how many cards can sit in a column at once, so the board **stops the team starting more than it can finish**. ### Surfaces bottlenecks If QA is full, no new development starts until cards clear, so problems are **fixed instead of piling up**. ### Steadier throughput Clients get **faster, steadier throughput** and a realistic, observable pace, rather than a flood of half-done work that stalls near a deadline. WIP limits turn "we're busy" into **"we are actually shipping"**. ## What happens when a card fails: the KO/rework loop If a card fails QA or the client rejects it, it is marked *KO* and sent **back to In Progress**. It is never quietly closed or hidden. The same developer **corrects the issue**, and the card re-enters QA to be **re-checked from scratch** against the same automated and internal tests. A card only reaches Deploy once it **passes cleanly**, so defects are caught **inside our team**, not by your users or in Production. This loop is why our delivery is **low-risk by design**: rework is an expected, tracked state, not an emergency. ## The QA gate: how quality is enforced before delivery Every card must clear an **automated test suite**, covering *Behat* (behavioural), *Unit* (logic), and *static analysis* (code standards and typing), before a human even reviews it. It then passes **internal team validation**: a second person confirms the work meets acceptance criteria **before the client ever sees it**. Nothing advances to Deploy on a developer's word alone, because the **board enforces the gate**, making quality a process rather than a promise. For the full testing and CI/CD pipeline behind this gate, see our [quality assurance methodology](https://metadrop.net/en/methodology/quality-assurance). Discuss your project Tell us about your Drupal project and we will show you how this board keeps delivery predictable. [Discuss your project](#contact) ## Predictable delivery vs. ad-hoc development The result is **transparent, low-risk delivery**, the core reason enterprise teams trust a governed partner over an unstructured vendor. ### Visible vs. opaque **Opaque agencies** work in a black box, where you learn about slips at the deadline. With our board, **progress is visible daily** and surprises are caught early. ### Gated vs. ad-hoc **Ad-hoc delivery** ships untested work and fixes it in Production. Our **QA gate and KO loop** keep defects internal and out of your live site. ### Finishable vs. endless **No WIP control** means everything is "in progress" and nothing finishes. Our **WIP limits** force a steady, finishable flow, the difference between motion and progress. ## Why this delivery model matters for your project - **15+ years delivering Drupal** as a *Drupal Silver Certified Partner*. This board is refined across every project, not improvised per client. - We apply the same **states, WIP limits, and QA gate on every delivery cycle**, so behaviour is consistent whether the project is one site or a multi-site platform. - Backed by **ENS certification and a GDPR / WCAG / NIS2 compliance** track record, quality gating is part of how we meet those standards. - Trusted on mission-critical Drupal work by organizations including **Saint-Gobain, Save the Children, Telefónica, and UNICEF**. ## Frequently asked questions - ### What is a Kanban board? A Kanban board is a visual workflow that tracks every task through defined states. At Metadrop, those states are *Backlog → To Do → In Progress → QA → Deploy → Done*, so the **status of all work is visible at a glance** and progress is measurable in real time. - ### How is a Kanban board different from Scrum? Scrum sets the **rhythm** through sprints, planning, reviews, and retrospectives, while Kanban governs the **continuous flow of work** through columns and WIP limits. We use both together. For the ceremonies side, see our [Scrum meetings methodology](https://metadrop.net/en/methodology/agile-scrum-meetings). - ### How do clients track progress on a project? The board is the source of truth. You can see **which cards are in development, in QA, or deployed** at any moment, with no need to request a status update. Visibility is continuous rather than a weekly report. - ### What happens when a task fails quality checks? It is marked *KO* and returns to In Progress for correction, then **re-enters QA to be re-checked** before it can advance. A card only reaches Production once it **passes cleanly**, so defects are caught inside our team. - ### What are WIP limits and why do they matter? WIP (work-in-progress) limits cap how many cards a column can hold, which **stops the team over-committing** and surfaces bottlenecks immediately. The payoff is **steadier throughput and a predictable delivery pace**. ## Get in touch See how our Drupal agency turns this Kanban delivery model into predictable, transparent project delivery for your team. Explore our methodology: [Agile Scrum meetings](https://metadrop.net/en/methodology/agile-scrum-meetings), [Quality Assurance](https://metadrop.net/en/methodology/quality-assurance), [Tools](https://metadrop.net/en/about/methodology/tools), and [Deliverables](https://metadrop.net/en/about/methodology/deliverables). You must have JavaScript enabled to use this form. Name Email Organization Tell us more Escribe tu mensaje aquí... Privacy policy I have read and accepted the [privacy policy](https://metadrop.net/en/privacy-policy) regarding data processing. Leave this field blank ## Our Methodology How Metadrop runs complex Drupal projects: Scrum ceremonies, Kanban boards, quality assurance, and full deliverables at project close. - [**Quality Assurance**](https://metadrop.net/en/methodology/quality-assurance "How Metadrop ensures code quality: CI/CD pipelines, automated testing, static analysis, and peer review on every Drupal project.") How Metadrop ensures code quality: CI/CD pipelines, automated testing, static analysis, and peer review on every Drupal project. - [**Tools**](https://metadrop.net/en/about/methodology/tools "The agile and DevOps tools Metadrop uses: version control, CI/CD, communication, and project management platforms across all projects.") The agile and DevOps tools Metadrop uses: version control, CI/CD, communication, and project management platforms across all projects. - [**Deliverables**](https://metadrop.net/en/about/methodology/deliverables "Full handover of source code, documentation, credentials, and accesses so your team is completely self-sufficient at project completion.") Full handover of source code, documentation, credentials, and accesses so your team is completely self-sufficient at project completion. - [**Agile Scrum meetings**](https://metadrop.net/en/methodology/agile-scrum-meetings "How Metadrop implements Scrum ceremonies — stand-ups, sprint planning, reviews, and retrospectives — within our agile Drupal projects.") How Metadrop implements Scrum ceremonies — stand-ups, sprint planning, reviews, and retrospectives — within our agile Drupal projects.