---
url: 'https://metadrop.net/en/about/methodology/tools'
title: 'Agile Tools We Use: Git, Jira, CI/CD'
author:
  name: Root
  url: 'https://metadrop.net/es/sobre/metadrop'
date: '2019-05-26T10:29:52+00:00'
updated: '2026-07-28T10:18:02+00:00'
type: article
summary: 'Discover the agile and DevOps tools Metadrop uses: Git, Jira, Slack, Jenkins, and more for transparent, quality-driven Drupal project delivery.'
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/about/methodology/tools'
      breadcrumb:
        '@type': BreadcrumbList
        itemListElement:
          -
            '@type': ListItem
            position: 1
            name: Home
            item: 'https://metadrop.net/en'
          -
            '@type': ListItem
            position: 2
            name: 'About Metadrop'
            item: 'https://metadrop.net/en/about'
          -
            '@type': ListItem
            position: 3
            name: "Metadrop's Work Methodology"
            item: 'https://metadrop.net/en/about/methodology'
      publisher:
        '@type': Organization
        '@id': 'https://metadrop.net/#organization'
---
 1. [About Metadrop](https://metadrop.net/en/about)
2. [Metadrop's Work Methodology](https://metadrop.net/en/about/methodology)
 
  

# Tools

 



   



 We have experience with various tools for development, communication and project management. Among our favorites are:



 

 

 

 

## Communication



**[Slack](https://slack.com/intl/es-es/)** - Communication tool between team members and the various teams involved in a project. It is used for interpersonal communication, for internal organization at the team level, for requesting assistance or help at the company level and for sharing discoveries and good practices.

**[Google Meet](https://meet.google.com/) / [Jitsi Meet](https://meet.jit.si/)** - Video call tools, we use them constantly for daily and weekly meetings as well as for pair programming or communication between developers working remotely.

**[Chrome Remote Desktop](https://remotedesktop.google.com/)** - Live support tool, allows you to take remote control of the desktop to provide direct assistance both internally (between developers) and externally (with the client).



 

 



 

 

 

 

## Project management



**[Trello](https://trello.com/)** - Project management tool. We use it with some clients who are used to it.

**[Asana](https://app.asana.com/)** - This is the main tool we use for communication between team members or teams working on the same project. It has a very fast interface to manage tasks and communication.

**[Jira](https://es.atlassian.com/software/jira)** - One of the most widespread project and management tools. Besides Jira, Atlassian integrates with other tools like Bitbucket, making a very complete solution for some projects.

**[Taiga](https://taiga.io/)** - Project management tool, it is free and open source.



 

 



 

 

 

 

**Cerebro** - Coordinating and synchronizing so many project management tools is a time-consuming task. To streamline these processes, **we have developed our own internal tool**, Cerebro, at Metadrop.

Cerebro operates as an aggregator, so that tasks coming from Trello, Jira, Asana, Gitlab or others can be centralized in a single board. Developers use Cerebro as the unique reference when it comes to knowing the status of their tasks and assignments, as well as the overall progress of their team and the existence of **bottlenecks or emergencies**. Scrum masters can **plan sprints and easily distribute the workload.**

In addition, Cerebro synchronizes with tracking tools such as Toggl and is able to generate **detailed and customizable reports** to use as accountability and transparency to the client or as internal documents to detect areas for improvement.



 

 



 

 

 

 

## Documentation



**[Nextcloud](https://nextcloud.com/)** - We use it as a file sharing server, especially for those that require an additional security layer or are larger in size.

**[Google drive](https://www.google.com/intl/es_ALL/drive/)** - We use it as a documentation tool. It is fast, can be used by several people at once and is widespread.



 

 



 

 

 

 

## Code repositories



[Bitbucket](https://bitbucket.org) - Many of our projects are hosted on Bitbucket. This Git-style service offers team members a common place to host their code and a set of tools (Pull Requests, diff) to streamline processes.

[Github](https://github.com/) - Internationally known, it is one of the tools most used by developers to host code.

[Gitlab](https://about.gitlab.com/) - Born as an alternative to Github, it has grown to be an application for the entire development pipeline. In addition to hosting the code using Git, it includes project management tools like dashboards or issues that integrate directly with the code.



 

 



 

 

 

 

## Virtualization



[Docker](https://www.docker.com/) - We use this popular container system to develop projects in our local environments quickly and ensure that the whole team works on the same basis.

[Vagrant](https://www.vagrantup.com/) - We have been using Vagrant in our projects for many years. In most cases it has been replaced by Docker, but it is still one of our favourite tools.



 

 



 

 

 

 

## Continuous Integration



[Jenkins](https://jenkins.io/) - La mayoría de las tareas automatizadas se gestionan con Jenkins. Llevamos años trabajando con ella y nos aporta seguridad y automatización de tareas necesarias para asegurar la calidad de código.



 

 



## Our Methodology



How Metadrop runs complex Drupal projects: Scrum ceremonies, Kanban boards, quality assurance, and full deliverables at project close.



 

- [**Kanban board**](https://metadrop.net/en/methodology/agile-kanban-board "How Metadrop structures Kanban workflows for Drupal development: task states, WIP limits, and quality checkpoints.") How Metadrop structures Kanban workflows for Drupal development: task states, WIP limits, and quality checkpoints.
- [**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.
- [**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.