Jira was
firstly created in 2002 as a bug and an issue-tracking tool for software
development, by Atlassian in Sydney. However, over the years, many other teams
across other industries that are not from IT world have started to use Jira to keep
the track of issues and/or tasks and organize the work. As a result, today,
Jira is “a powerful work management tool for all kinds of use cases, from requirements
and test case management to agile software development”, according to Atlassian,
and “the most highly recommended Agile project management tool in the world”,
as presented in 15th Annual State of Agile Report.
The big
advantage is that using a single platform, the teams can plan, track projects
(this means any issue type, whether a bug, a task, a work item…), release
software, and generate reports, … And it is flexible because it can be customized
to fit business requirements in what respects to define a workflow that meets
what is needed for a certain project.
As an agile project management software, Jira makes possible to create stories and plan sprints, for example. It also provides ready-to-use Scrum and Kanban boards. It enables teams to organize their work, having a clear knowledge of what is “to do”, what is “in progress” and what is “done”. But not only… It also allows more transparency and visibility, as we can easily have access to who is responsible for a certain issue or task, when this person started and finished working on it.
Including
dashboards and reports for tracking progress, performance and productivity in
time, Jira enables a better overview, global and detailed, of what happened and
how it happened, what is happening and what needs to happen to manage the
project in an efficient way. This is very important not only to the Agile team
(as a whole) but also to the project management teams, because it gives more
context to decide better and aligned to the bigger goals.
Although, Jira is strong enough to have a name that comes from Godjira, the Japanese for Godzilla, it has also some weakness, namely the lack of a communication tool – a quick way to directly send messages within it - and a feature to manage costs and assess risks, which is essential in project management.
 |
| 1954 Japanese film Godzilla |
Comentários
Enviar um comentário