{"id":37593,"date":"2015-07-27T12:07:00","date_gmt":"2021-02-10T11:00:13","guid":{"rendered":"https:\/\/www.globallogic.com\/latam\/insights\/blogs\/5-herramientas-esenciales-de-soporte-al-ciclo-de-vida-en-agile\/"},"modified":"2025-01-30T10:59:58","modified_gmt":"2025-01-30T10:59:58","slug":"5-herramientas-esenciales-de-soporte-al-ciclo-de-vida-en-agile","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/latam\/insights\/blogs\/5-herramientas-esenciales-de-soporte-al-ciclo-de-vida-en-agile\/","title":{"rendered":"5 herramientas esenciales de soporte al ciclo de vida en Agile"},"content":{"rendered":"
Every development process is, in its execution and among other characteristics, closely linked to the way in which a set of different tools interact to help bring the product forward.<\/span><\/span><\/p>\n

In particular, within the universe of agile methods there are numerous tools that help the development team to create, build, plan, manage and monitor the progress of User Stories (US) and support the organization and management of backlogs, sprints, burndown charts, retrospectives and most of the artifacts that are specific to agile management.<\/span><\/span><\/p>\n

However, there is no \u201csilver bullet\u201d among tools. There is no one that has everything at the same time and with each function at the expected level. Some place greater emphasis on the creation and monitoring of US, leaving aside the generation of statistics or metrics. Some tools seek simplicity at the cost of marginalizing functionality. Others incorporate more advanced services, but are more complex to use, extending the training period and learning curve. As always, it is important to take into account the advantages and disadvantages of each when choosing the tool to use. Below are described some of the main tools, detailing their strengths and weaknesses [2].<\/span><\/span><\/p>\n

Tool #1 – JIRA<\/span><\/span><\/strong><\/p>\n

JIRA<\/span><\/span><\/a><\/span> is a project management application based on the J2EE standard, offering flexibility and adaptability to meet the specific needs of different project management models. This allows it to easily adapt to agile methods such as<\/span><\/span> Scrum<\/span><\/span><\/a><\/span> or<\/span><\/span> Kanban<\/span><\/span><\/a><\/span> .<\/span><\/span><\/p>\n

JIRA has customizable and comprehensive filters, which provide excellent possibilities for management, metrics generation and reporting, add-ons, JIRA extras (some paid, others not) that help with specific needs. For example, JIRA Agile provides Scrum boards (for iterative and incremental processes) or Kanban boards (to manage flow in demand-driven processes) and allows building and managing the backlog (epics, US, swimlines, etc.), having collaborative work between team members and keeping agile metrics such as Burndown charts, velocity, CFDs, among others.<\/span><\/span><\/p>\n

Another notable aspect is the integration with other tools that facilitate workflows and allow, for example, to achieve complete traceability of requirements, US, Test cases, technical documentation and other artifacts. Among many other integrations, we could mention:<\/span><\/span><\/p>\n