airfocus offers a modular product management platform. It provides a solution for product teams to manage and communicate their strategy, prioritize their work, build roadmaps, and connect feedback to solve the right problems. airfocus allows users to customize the platform to fit the various ways that teams work. airfocus offers a 14-day trial.
$15
user/month
Jira Align
Score 8.0 out of 10
N/A
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.
airfocus is a scalable platform, very useful for any organization, especially for our IT department since it facilitates decision making, helps to establish different priorities, and helps to execute your sprints easily in a simple and visual way.
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.
Product prioritization was made simple by compiling stakeholder input on projects to determine the proper order to execute differing projects. Priority poker-like features are a huge timesaver.
Creating roadmaps could not be easier in airfocus. Creating new projects is intuitive and you can customize settings that allow you to automatically add projects to the overall roadmap. There are a number of choices for the roadmap templates also which is nice depending on individual product managers' needs and expertise.
Perhaps the most useful feature(s) of airfocus are the collaboration tools. The ability to build out product roadmaps with the entire team's input saves countless hours of in-person prioritization meetings and has made refinement meetings with engineering team go much more smoothly.
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.
As I have mentioned, some older, less tech savvy, team members have not found it as intuitive. I found it the same when I started using it although it quickly made sense. I think this is because there are lots of features we do not use so this can get in the way of what we do use
They answered every single question we had in a timely fashion and furthermore, they went out of their way to make sure we had all the time we needed to fully evaluate the product. I think the fact that they truly valued customer feedback to improve the product made them feel more like a partner then just an off-the-shelf solution
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.
It's easy to use, it's customizable. It is ideal for managing multiple product lists, it is transparent and helps keep any work team centralized. It has an intuitive interface, special to track the time to our established goals.
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.
We know exactly what the impact/effort is of our projects, so we don't waste time on projects or features that won't drive meaningful revenue or increased brand affinity.
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.
