ISOQualitas.PLM vs. Jira Work Management

Jira Work Management suits projects involving multiple teams, such as product development. In our case, the design, development, and QA teams use Jira to track tasks from ideation to deployment. Custom workflows and real-time updates ensure that all teams are on the same page, and the ability to link related tasks helps manage dependencies effectively.

Incentivized

• Provide a roadmap of all epics
• Provide a backlog in which you can see all the possible work to be done to create your sprint plan
• Have all our projects within reach
• Have a dashboard with editable columns to manage your work
• Be able to filter by person
• Be able to see past sprints

• More clarification on where to find useful tools and resources for new users.
• Breakdown of Projects, Tasks, Sub-tasks, bugs is hard to follow and cannot be changed once created.
• The ability to customize the dashboard/home page to fit the needs of individuals could use some work.

Incentivized

As we are Atlassian users overall, this entire ecosystem is truly built from a 360 perspective. It becomes the one source of truth, and we can easily see where we are in our projects and where to emphasize focus in the upcoming period. There are some areas for minor improvements, but they are more a matter of preference rather than business necessity

Incentivized

Personally I would not choose Jira Work Management for a marketing team. However, the marketing team was enveloped into the Jira Work Management instance due to use by more technical teams.

Incentivized

• The impact has been positive to have a roadmap available of all the work and to be more aware of the time, effort, and people that will be involved, in order to make a better decision about how our investment will look based on our benefits.