Agile Hive - SAFe in Jira vs. Azure DevOps Services

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Agile Hive - SAFe in Jira
Score 7.6 out of 10
N/A
The world of work is constantly changing. Agile work processes in particular are becoming increasingly popular. Even large companies are trying to introduce agile working methods. For many, the Scaled Agile Framework (SAFe) is the right solution for their agile teams. However, implementing SAFe with all its features such as providing reports, visualizing dependencies and automated documentation is not always easy in reality. Many companies spend a lot of time and money searching for the right…N/A
Azure DevOps Services
Score 8.2 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Agile Hive - SAFe in JiraAzure DevOps Services
Editions & Modules
No answers on this topic
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Agile Hive - SAFe in JiraAzure DevOps Services
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Agile Hive - SAFe in JiraAzure DevOps Services
Features
Agile Hive - SAFe in JiraAzure DevOps Services
Project Management
Comparison of Project Management features of Product A and Product B
Agile Hive - SAFe in Jira
7.8
1 Ratings
3% above category average
Azure DevOps Services
-
Ratings
Task Management7.01 Ratings00 Ratings
Resource Management8.01 Ratings00 Ratings
Gantt Charts7.01 Ratings00 Ratings
Support for Agile Methodology9.01 Ratings00 Ratings
Visual planning tools8.01 Ratings00 Ratings
Agile Development
Comparison of Agile Development features of Product A and Product B
Agile Hive - SAFe in Jira
10.0
1 Ratings
20% above category average
Azure DevOps Services
-
Ratings
Velocity Calculation10.01 Ratings00 Ratings
Dependencies and Blockers10.01 Ratings00 Ratings
Best Alternatives
Agile Hive - SAFe in JiraAzure DevOps Services
Small Businesses
GitLab
GitLab
Score 8.6 out of 10
GitHub
GitHub
Score 9.0 out of 10
Medium-sized Companies
Planview AgilePlace
Planview AgilePlace
Score 9.6 out of 10
GitHub
GitHub
Score 9.0 out of 10
Enterprises
Planview AgilePlace
Planview AgilePlace
Score 9.6 out of 10
GitHub
GitHub
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Agile Hive - SAFe in JiraAzure DevOps Services
Likelihood to Recommend
7.0
(4 ratings)
8.5
(70 ratings)
Likelihood to Renew
-
(0 ratings)
10.0
(3 ratings)
Usability
7.0
(1 ratings)
7.5
(9 ratings)
Support Rating
-
(0 ratings)
8.1
(11 ratings)
Implementation Rating
-
(0 ratings)
10.0
(1 ratings)
User Testimonials
Agile Hive - SAFe in JiraAzure DevOps Services
Likelihood to Recommend
//SEIBERT/MEDIA
Agile Hive is used for our value train
within a SAFe setup. Every quarter we organize a so-called Product Increment
(PI) Planning, where we plan all Features and Enablers in Agile Hive.
Based on the priority of the Product Manager all teams plan their Features and
Enablers accordingly to the sprints that are determined by the Release Train
Engineer and set up in Agile Hive. The teams then create User Stories and
estimate them and based on their sprint velocity (defined in Agile Hive)
Product Owners can see how many Features and Enablers are realistic in one
quarter (Product Increment). Further, dependencies across teams can be defined
and made visible in Agile Hive, so that the plan is feasible. Without Agile
Hive it would be hard or impossible to plan across several teams within a value
train and to manage all dependencies. Additionally, with Agile Hive the plan is
more realistic, so what can be achieved within one quarter in product
development.
Read full review
Microsoft
DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.
Read full review
Pros
//SEIBERT/MEDIA
  • Roadmapping in terms of defining epics and planning them across a timeline and across teams.
  • Showing dependencies within teams and across teams and over time horizon.
  • Create transparency throughout the product organization and teams about what is planned.
Read full review
Microsoft
  • Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
  • Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
  • Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Read full review
Cons
//SEIBERT/MEDIA
  • I believe the training and support could be more hands on and easier.
  • The Agile Hive - SAFe in Jira product can be a bit robust to understand.
  • Having Knowledge transfer videos can help more than documentations.
Read full review
Microsoft
  • I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
  • The wiki is not the prettiest thing to look at, so it could have refinements there.
  • It could improve the search slightly better.
Read full review
Likelihood to Renew
//SEIBERT/MEDIA
No answers on this topic
Microsoft
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Read full review
Usability
//SEIBERT/MEDIA
It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).
Read full review
Microsoft
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Read full review
Support Rating
//SEIBERT/MEDIA
No answers on this topic
Microsoft
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Read full review
Implementation Rating
//SEIBERT/MEDIA
No answers on this topic
Microsoft
Was not part of the process.
Read full review
Alternatives Considered
//SEIBERT/MEDIA
With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.
Read full review
Microsoft
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
Read full review
Return on Investment
//SEIBERT/MEDIA
  • More transparency.
  • Better product decisions.
  • Saving time and resources.
  • Less critical dependencies.
Read full review
Microsoft
  • We have saved a ton of time not calculating metrics by hand.
  • We no longer spend time writing out cards during planning, it goes straight to the board.
  • We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
Read full review
ScreenShots