Summary -

In this topic we are going to discuss in brief about tools that are used in Agile both for Agile Management and Agile Development.


Below are some of the popular tools among the total available -

Agile Manager

HP's Agile Manager was developed to organize and guide teams from the starting as they plan and deploy the working code through the agile model. At the starting stages of the cycle, during the release plan, managers would gather the user stories and would decide how the teams would attack them. These would set the stage for sprints and deployment. During each Code sprint, the scrum masters and the developers would record their progress on the user stories and issues. Progress of the project would be projected on the dashboards so that the entire team would be aware of the project's progress.

Active Collab

Active Collab tool helps in tracking time and generating bills. It is Organized in order to help the software shops to deliver the code and account for their time. The heart of the system is a list of tasks that would be assigned and tracked from starting to completion. System-wide calendar would help the team understand and follow everyone's roles. System would check the amount of time that has been devoted to all the tasks so that the team can determine how accurate their estimates are. The system would support a collaborative writing tool so that everyone can work together on the documentation, an essential operation that would set the stage for more agile collaboration later.

JIRA Agile

The JIRA Agile tool would add a layer for agile project management that interacts with the major tools from Atlassian. The team would create a list of project tasks with a tool known as confluence and then tracks them on an interactive Kanban board that developers would update as they work. The Kanban boards would become the center of everyone is focused to plan how to attack the code. The Agile tool would be integrated with other Atlassian tools. Dashboard would be updated the moment the code is committed to stash or Bitbucket, Atlassian's Git hosting products.

Agile Bench

Agile Bench is a tool that has been hosted in order to highlight the tracking of the work assigned to each individual. The release schedule would start as a backlog of user stories and other additions. As they are assigned, the team should measure both the business impact and the cost of development by assigning an estimate of the complexity of every task in points. Dashboard is used to track both these values so that members would tell who overloaded and which tasks is are important. The tool is integrated with Git hosting sites like GitHub or Bitbucket which allows it to make committed code with tasks.

Pivotal Tracker

Pivotal Tracker is a group of tools from pivotal Labs that has been created to support Agile development. The core of the project is a page that would list the tasks that are often expressed as stories. Team members would rack the complexity with points and the tool would track the number of tasks finished each day. The group would include Whiteboard for team-wide discussions, Project Monitor for displaying the status of the build, and Sprout, a configuration tool.

Telerik TeamPulse

Telerik is a tool that has many frameworks for creating apps in the mobile market. This has been utilized to create their own code into Teampulse, a tool they use in order to track projects. The main screen would display a full page of tasks which need to be completed and which would follow the team as it would progress. The menus would contain configuration options and a wide range of reports which show how the project is progressing towards completion. It would also work with Telerik's other tools for building and testing the code.

Version One

Version One is designed in order to organize all the groups involved in development across an enterprise by providing a stable communication platform where everyone would plan the initiatives and create continuous documentation. This tool would accept Kanban boards for following the ideas and stories through the process until they are turned into working code. The system would track all sprints and organizes the retrospective analysis so the team can start the cycle again.


Planbox would have four levels of Organizational power in order to keep multiple teams working together to achieve a common goal. Initiatives would be on top priority which are huge abstractions. They would contain projects that are built on items which in turn are filled with tasks. As the tasks are finished, Planbox would track the progress on all these levels and produces reports for all the stakeholders. Time tracking feature would let everyone compare the time that each one spends on an item with the estimate of how long it was thought to take.

The tool integrates with GitHub (see number six above) for code storage, Zendesk for tracking customer satisfaction, UserVoice for bug tracking, and many more.


Leankit would replicate the whiteboards of a conference room where most projects start. It would allow the team members to post virtual notes or cards that would represent all the tasks, user stories, or bugs that should be addressed. As the team finishes them, the board updates faster than any whiteboard. The software also allows multiple teams to work together in separate spaces while still coordinating their interactions.


Axosoft project tools would track the project in the three different ways. The Release planner would present a tabular view of the different tasks, bugs, and user stories. Developers drag and drop the different entries in order to assign them and mark them as finished. The burndown charts would show graphically how quickly the team is intersecting on its goal. The projected ship date is displayed prominently to keep everyone on track. The planning is also done Kanban-style using the card view, where each card represents one task.