A solution to bridge the gap between strategy and execution for portfolio, product, and program management teams, used to manage idea intake, prioritize your feature backlog, and track progress with live roadmaps.
$27,000
per year
Jira Work Management
Score 8.1 out of 10
N/A
Jira Core is Atlassian's general purpose business and project management tool available to smaller companies or teams and designed to suit a variety of purposes (e.g. marketing planning, product roadmap, etc.). In Jira Core, Workflows define process and enable teams to track tasks. Jira Core Cloud instances also have boards that let users visualize workflows and drag and drop tasks from to-do to done. It is available on the cloud.
The Atlassian Jira Align (formerly AgileCraft) tools help keep our scrum teams moving in the right direction. It gives Sr. Executives visibility into the progress of our digital transformation efforts. It provides information to our program manager to create the necessary artifacts to justify continued funding of our initiatives. It also supports the SAFe framework, along with some others. And the Atlassian Jira Align (formerly AgileCraft) tools provide integration to other tools that we use in our portfolio.
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.
Effective Sprint planning : Sprint planning can be done using Planning Poker in AgileCraft by clicking Team > Manage > Other > Estimation Games very effectively for distributed teams.
Team Capacity Allocation Report: After tasks are created at team or program level, the report from AgileCraft cab be pulled and can be verified that no team member is under or over allocated. A report can be generated by navigating to Team > Manage > Assign Tasks.
Effective Requirement trace-ability: To maintain requirements trace-ability follow the steps below:
Upload test cases against the story/requirement. once uploaded test cases will be visible under that story
Execute Test cases in AgileCraft and mark them as Pass/Fail based on the actual outcome
Based on test results, The acceptance criterion's can be marked as “Pass” or “Fail” & if marked failed corresponding defect can be logged & can be attached with the story
So against each story we can easily see whether all test cases been executed or not & which acceptance criterion's are failed & how many defects are in open or close state.
Daily Scrum: In AgileCraft, the option to run a daily stand-up is available from Team > Manage > Daily Standups. Selecting the sprint number opens the daily stand-up meeting window in which each team member's tasks are visible and hours can be burned against them. Conduct Scrum meetings in AgileCraft, and burn each associate hour against the tasks created during the meeting. The burn-down chart can be generated & viewed during the stand-up to check whether the team is on track.
The initial ticket creation screen lacks some important features, such as assigning "point values" (a measure of effort needed for the ticket).
The browser needs to be manually refreshed to see new tickets, which can make things confusing when several people in a meeting are simultaneously creating tickets.
The interface on some smaller portions of the software are sometimes difficult to understand.
Most of the things are easily manageable except certain things that are hidden and you need to ask teammates who are aware of how they can link attachements in the comment section and so on.
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
Overall support from Jira team is good. It comes at an additional price but it is very efficient. There are no long wait times, you get a dedicated team to look into your issues. The support is available throughout the year and they keep a record of your issues. Overall we are very satisfied with the support they have provided us over the years, it has been very effective for the price that we pay.
Microsoft Azure Devops won't have the major functionality of software management like Jira. The customization provided by Jira is having a cutting edge over any project management tool. Adds-on and Plugins feature in the Jira Tool make it as perfect as desired task management tool for any company. One of the best Agile based Project Management Tools.
The evolution of Jira Service Desk to Jira work management is accompanied by lot of new features like the List View which allows inline editing, easy column management, the Calendar View bases on extensible modal and state categories, the Timeline View supports tasks and subtasks, the Boards which allow the categorization of status and allow the visibility of subtasks on the cards, Forms can be created very easily, Project templates can be used based on the business area.
It has positively impacted our tech teams, allowing them to better organize the tasks and items they are working on and has greatly improved their ability to communicate & review these tasks with other teams.
I believe it negatively impacted other departments as lengthy training was required by many associates to attempt using the tool, only to find out it didn't meet our needs, therefore much time was wasted.
For our marketing team, Jira Work Management caused us to lose valuable work time due to manual updates that could have been automated.
Due to lack of creative review tools within Jira Work Management, our team had to pursue other tools that do not integrate with Jira Work Management, thus creating additional OpEx.
