Our Score: 83/100
Jira is a project management software that allows you to plan, track and manage activities and projects. It’s a tracker for teams planning and building great products. The programme works by connecting colleagues, activities and tools thus enabling them to work more efficiently.
In our opinion, Jira is one of the best project management software for agile teams that unlocks the power of Agile Project Management, whether you’re a seasoned agile expert, or just getting started. It offers all essential aspects of agile planning such as creating and estimating stories, building a sprint backlog, identifying team commitment and velocity, visualizing team activity, and reporting on team progress.
Jira Overview by Atlassian
Designed specifically for software teams, JIRA Software combines powerful developer tool integrations with the most important elements of agile development, like flexible Scrum and Kanban boards, and real-time reporting. It offers custom forms and fields to collect and map relevant information, from features to bugs to general tasks of any kind.
It includes JIRA Query Language, which offers search functionality to search and sort for tickets and creates custom filters. JIRA is pre-configured with a range of workflows, which teams can modify to match precisely how they work. JIRA connects people and teams and provides users one place to share and discuss work, mention one another using mentions, subscribe to specific notifications and watch activity streams of any changes. It offers reporting features for the project owners and team members to visualize the team progress and track performance.
|1.||Project Planning & Scheduling|
|1.1.||Setting priorities and deadlines||√|
|1.2.||Resources & Workload Management*||√|
|1.3.||Support Agile Methodologies||√|
|2.1.||Assigning tasks to team members||√|
|2.2.||Attach files to the task||√|
|2.3.||Comments on task||√|
|2.8.||Progress Tracking / Status||√|
|4.||Project Financial Management|
|4.2.||Payments / Billing*||√|
|4.4.||Integration with Accounting Systems*||√|
* Available on Atlassian Marketplace
The Scrum framework enables software teams to manage complex projects by creating a culture of collaboration. Scrum encourages team collaboration by focusing on a single goal at a time and delivering incrementally.
A standard Scrum process begins with the creation of a product backlog, which in simple terms, is really the team’s to-do list. Each team member plans how much of the backlog he or she can complete in a given timeframe (the “Sprint,” typically two weeks). The Sprint begins and the team builds the product. At the end of each Sprint, the team determines what work to tackle next based on the outcome of the previous Sprint. And the process repeats.
Unlike Scrum, Kanban focuses on status rather than due dates. Each item of work progresses through pre-defined project stages so teams can easily see what work is in-progress and identify roadblocks.
A basic kanban board is a three-step workflow: To Do, In Progress, and Done. But depending on the unique requirements and composition of your team, additional workflow stages can be mapped in. With this Flexible kanban boards, your team is full visibility into what’s next so you can continuously deliver maximum output in minimal cycle time.
Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues. It helps you track and analyze your team’s work throughout a project.
Reports for Scrum projects
- Burndown Chart – Tracks the total work remaining, and projects the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly.
- Burnup Chart – Provides a visual representation of a sprint’s scope, as well as its remaining work. This helps your team stay on track.
- Sprint Report – Shows the work completed or pushed back to the backlog in each sprint. This helps you determine if your team is overcommitting or if there is scope creep.
- Control Chart – Shows the cycle time for your product, version, or sprint. This helps you identify whether data from the current process can be used to determine future performance.
- Cumulative Flow Diagram – Shows the statuses of issues over time. This helps you identify potential bottlenecks that need to be investigated.
- Epic Report – Shows the progress towards completing an epic over time. This helps you manage your team’s progress by tracking the remaining incomplete and unestimated work.
- Epic Burndown – Similar to the Epic Report, but optimized for Scrum teams that work in sprints. Tracks the projected number of sprints required to complete the epic. This helps you monitor whether the epic will release on time, so you can take action if work is falling behind.
- Version Report – Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.
- Release Burndown – Similar to the Version Report, but optimized for Scrum teams that work in sprints. Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.
- Velocity Chart – Tracks the amount of work completed from sprint to sprint. This helps you determine your team’s velocity, and estimate the work your team can realistically achieve in future sprints.
Reports for Kanban projects
- Average Age Report – Shows the average age of unresolved issues for a project or filter. This helps you see whether your backlog is being kept up to date.
- Created vs Resolved Issues Report – Maps created issues versus resolved issues over a period of time. This helps you understand whether your overall backlog is growing or shrinking.
- Pie Chart Report – Shows a pie chart of issues for a project or filter grouped by a specified field. This helps you see the breakdown of a set of issues, at a glance. For example, you could create a chart to show issues grouped by Assignee for a particular version in a project (using a filter).
- Recently Created Issues Report – Shows the number of issues created over a period of time for a project or filter, and how many were resolved. This helps you understand if your team is keeping up with incoming work.
- Resolution Time Report – Shows the length of time taken to resolve a set of issues for a project or filter. This helps you identify trends and incidents that you can investigate further.
- Single Level Group By Report – Shows issues grouped by a particular field for a filter. This helps your group search results by a field, and see the overall status of each group. For example, you could view the issues in a version of a project, grouped by Assignee.
- Time Since Issues Report – For a date field and projects or filter, maps the issues against the date that the field was set. This can help you track how many issues were created, updated, etc over a period of time.
- Time Tracking Report – Shows information of time spent on issues for a particular version of a project.
- User Workload Report – Shows how much work a user has been allocated, and how long it should take. For a specified user, you’ll be able to see the number of unresolved issues assigned to the specified user, and the remaining workload, on a per-project basis.
- Version Workload Report – Shows how much outstanding work there is (per user and per issue) before a given version is complete. For the specified version, you’ll be able to see a list of unresolved issues assigned to each user, each user’s workload, and a summary of the total remaining workload for the version.
- Workload Pie Chart Report – Shows the relative workload for assignees of all issues for a project or filter.
A product roadmap is a plan of action for how a product or solution will evolve over time. Product owners use roadmaps to outline future product functionality and when new features will be released. When used in agile development, a roadmap provides a crucial context for the team’s everyday work and should be responsive to shifts in the competitive landscape. Multiple agile teams may share a single product roadmap.
The Roadmap is where you can create, manage and visualize your team’s epics. Roadmaps are useful for planning large pieces of work several months in advance and planning large groups of stories across different sprints. Roadmaps are only available in next-gen Jira Software projects and aren’t available in classic projects.
- Custom filters – Create customer filters using Jira Query Language (JQL)
- Developer tool integrations – Integrate with developer tools for end-to-end traceability such as Bitbucket Cloud, Github, Atlassian Cloud Applications, and more.
- Customizable workflows – Create customizable workflows that map to any style of work.
- Rich APIs – Automate processes with Jira’s robust set of APIs
The Jira Cloud app lets teams who use Jira Software, Jira Service Desk, and Jira Core collaborate and give updates from anywhere.
- Quickly respond to project updates and important conversations
- Create and edit tasks, tickets, and bugs
- Track kanban boards and agile projects on the go
- Manage projects from your fingertips
- Check your Jira Service Desk queues, and reply to customers
Atlassian lets users try their product for 7 days with access to all features that they have to offer. In my opinion, Jira Software gives users a simple way to manage the Scrum or Kanban Board. With drag and drop features, you can easily move the task from product backlog to “To Do” list or vice versa.
I think It’s a bit hard to use without exploring the tool and education on it. It takes time to understand it. For example, reporting features are tricky: Either you become very crafty at JQL, or you pay extra bucks to get extra plug-ins either from Atlassian or from a 3rd party.
What I like about Jira is the features and scalability to be the correct solution for companies/teams of any size. What makes Jira great, is the flexibility it gives you on how you want ticket tracking implemented. External users, internal users, public-facing, etc.
Jira really shines in its management structure and advanced capabilities. It can keep even large teams organized and on track. And what it may lack in intuitive usability, the tool makes up for in powerful features. Time tracking, workflow, reporting, and document management are just a few examples.
Customer Service & Support
Support requests must be submitted through their website. If you think you’ve found a bug, you can visit their system status and bug reports for the latest updates on known issues. In addition, you can access their support page to learn more about Jira Software.
Jira Software has two pricing options for their cloud-hosted services. Prices depend on the maximum number of users. There’s a plan that’s a $10 monthly flat fee for teams with up to 10 users, and another that costs $7 per month (per user) for teams with 11 to 100 users. Discounts are available for subscribers who pay annually.
Pros and Cons
Jira is another powerful, agile development tool that gives you everything you need to track projects, squash bugs, and deliver great software. It is very easy to track team tickets as well as display everything on a board that conforms to your team’s workflow (scrum, kanban, etc). Also, from an administrative standpoint setting up project permissions and integrating it with other systems was simple.
The bad thing that I found in JIRA is that the software is not really easy to use and take much time to explore all features.
When it comes to project management software, you have a lot of options. There are advanced online solutions, like Wrike. There are simpler methods, like Trello. But when you’re looking for powerful, self-hosted project management—especially for software development—JIRA is hard to beat.
With its ancestry in development, JIRA is ideal for software developers. But any department can use its project management capabilities effectively. It’s great for any team that needs to collaborate and work through issues in an orderly manner. Here are a couple examples of other groups that could benefit from using JIRA for project management:
- Marketing – The company needs a new brochure created. JIRA can be used to communicate copy direction to the writer, graphics needs to the designer, and flag the finished project to be approved by the Chief Marketing Officer.
- Compliance – Trading and banking firms, as well as nearly all small businesses, need accurate workflow tracking. Whether your compliance department is asking for documentation or you’re being audited, JIRA can help.
- Remote companies and teams – If you have an entirely remote company or often employ freelancers, JIRA’s team organization abilities will come in handy. It provides a central system for employees and freelancers to check on tasks they’ve been assigned. And managers appreciate the detailed reporting tools.
Atlassian Corporation Plc is an Australian enterprise software company that develops products for software developers, project managers, and content management. It is best known for its issue tracking application, Jira, and its team collaboration and wiki product, Confluence.
Mike Cannon-Brookes and Scott Farquhar founded Atlassian in 2002. The name derives from the Titan Atlas from Greek mythology who had been punished to hold up the Heavens after the Greek gods had overthrown the Titans. This was reflected in the company’s logo used from 2011 through to the 2017 re-branding through a blue X-shaped figure holding up what is shown to be the bottom of the sky.
Atlassian released its flagship product, Jira – a project and issue tracker, in 2002. In 2004, it released Confluence, a team collaboration platform that lets users work together on projects, co-create content, and share documents and other media assets.
In a 2014 restructuring, the parent company became Atlassian Corporation plc of the UK, with a registered address in London—though the actual headquarters remained in Sydney. Atlassian has offices in five countries: Amsterdam in the Netherlands; Austin, San Francisco, and Mountain View, California, in the United States; Manila in the Philippines; Yokohama in Japan, and Sydney in Australia. The group has over 2,200 employees serving more than 60,000 customers and millions of users.
In November 2015, Atlassian announced sales of $320 million, and Shona Brown was added to its board. On 10 December 2015 Atlassian made its initial public offering (IPO) on the NASDAQ stock exchange, under the symbol TEAM, putting the market capitalization of Atlassian at $4.37 billion.