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.
See how our governed Kanban delivery gives you predictable, transparent Drupal projects.
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.
Backlog
Holds documented, prioritized tasks and user stories with acceptance criteria set, ready to be estimated and pulled into a cycle.
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.
In Progress
Holds cards in active development pending delivery, plus any rejected (KO) cards being corrected and resubmitted for re-check.
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.
Deploy
Holds cards approved to ship, queued for release to Production.
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.
Tell us about your Drupal project and we will show you how this board keeps delivery predictable.
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.
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, Quality Assurance, Tools, and Deliverables.