Jira is typically regarded as a technical tool. In some companies, this reputation is so widespread that the IT and software teams use the Jira intensively, while other teams avoid it completely. In this two-part article, I’m arguing why it’s worth freeing Jira from this unfair constraint and expanding its use into the company as a whole.
Easy Agile Roadmaps for Jira addresses the needs of product managers, their teams and stakeholders by providing a clear shared product vision & direction, keeping everyone updated at all times, allowing distributed teams to collaborate more effectively and clearly visualizing the goals the teams and managers need to meet.
Confluence and JIRA are definitely great products in their own right. However, there are several great reasons to use them together. Software development teams already using JIRA will benefit from using Confluence as well.
There are times when even agile teams can’t get around a certain level of planning. But, it can be quite challenging to balance daily tasks within a sprint along with the added pressure of a plan.
Since development teams organize their day-to-day operations in JIRA, Atlassian developed Portfolio for JIRA, which takes planning to a new level. The new plugin helps align product roadmaps with sprint planning, keep track of dependencies, manage team skills, and pose what-if questions.
A story map describes the journey a customer undertakes with …
With JIRA 7, Atlassian gives individual teams in a company the exact products they need for their use. The license structure was broken up, three new products were created at the same time, and the use cases were changed. This applies to the tools JIRA, JIRA Agile and JIRA Service Desk. In this article, we explain how changes to JIRA licensing affect you and answer the most important questions.