AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
Rally Software
Score 6.8 out of 10
N/A
Rally Software headquartered in Boulder, Colorado developed the Rally agile software development / ALM platform which was acquired by CA Technologies and rebranded as CA Agile Central. After CA's acquisition by Broadcom the software was once again rebranded as Rally.
Jira has been growing in hardware design teams since is being integrated with CAD software. The best of Azure is that you can manage since level of access control to multiple types of teams. Another bonus is that Jira has more mobile features that let your team stay connected …
Because of the microsoft ecosystem and the product is also build on ms services cloud which uses azure internal services so it is easy to integrate. more reliant support available for the microsoft services because of the well established user community of the product and …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
Managing projects is a breeze using Azure DevOps Server, and the tool also automates testing and checks to see if the project is within its scope. Intuitive, with a low learning curve for novice users; it's also simple to collaborate on projects and keep tabs on their progress …
Honestly speaking, GitHub is better in terms of version control and JIRA has better functionality when it comes to Agile boards, other than that, the UI could have been a bit better for Azure DevOps Server. In all other areas, I feel overall Azure DevOps Server is better.
In my opinion, DevOps covers the development process end to end way better than JIRA or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. …
I was new to the agile methodology when it was first introduced to the Enterprise. Different project teams opted to leverage different project management tools, two of the most common being Jira and DevOps. For someone overcoming a huge learning curve already, I felt that …
My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other …
I was not involved in the purchase decision for this product. Since I have started working at my company, we have always used [Azure DevOps Server]. So I can't comment on how it performs vs its competitors. I have used many project management tools that are not as robust, but I …
I've used and currently use JIRA, which is a similar software to Azure DevOps Server. Azure DevOps Server is more detailed and comprehensive than JIRA. They both offer many of the same features and capabilities but Azure has a better overall interface and is more in-depth. It …
Azure DevOps Server is a fantastic tool and my favorite for organization and management of large application building projects. It was selected for its ease of use with a user-friendly design that allows any team members, particularly outside of developers, to quickly get up to …
At the time we brought Azure DevOps in-house it really was the only game in town. Our company migrated from Visual SourceSafe to TFS to Azure DevOps without any issues or downtime. Git isn't overly intuitive so I never recommend it and shy away from it. I loved it when …
Microsoft Azure DevOps is the one that integrates everything you can possibly use and provides a solution that eases your developing process. It has a strong support community and well-written documentation. No matter what you do, you will always find the right pipeline. It is …
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose …
TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because …
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, …
Overall, Rally Software is a better and more powerful tool than Jira for the same exact purposes. Jira cannot function as a requirements repository so it needs plugins or separate tools to do the same thing. There is no space or option to see all defects or user stories or …
We have used Jira in the past. Jira is easy to use and seems to be an industry standard. Rally is clunky and expensive. The dev side did not pick it, the business did due to its reporting capabilities.
I did not select Rally; it was chosen by the organization. If I were choosing what to use within my own team, I would use Trello. It's free, very simple to use, and has a much nicer user interface. My company previously used VersionOne however, and I prefer Rally over that …
It was a close race between JAMA, JIRA and Rally. We decided to go for JAMA as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
Our evaluation was done many years ago, but at the time Rally provided the best mix of SCRUM-driven features, visibility and economy for our product engineering teams.
Selected because the others seemed worse two years ago when the decision was made. VersionOne seemed ugly and too restricted. Might look better now. Microsoft TFS, now VSO, looked limited but also might look better now. Microsoft is improving it at a remarkably rapid pace. Jira …
The process we used to select a tool was to create a scorecard of IT and Business stakeholder needs. We then reviewed seven tools and graded them against the scorecard requirements. We took the top two products and had a one day hands on demonstration with selected IT and …
We used CA Agile Central (formerly Rally) before but recently switched to Jira. I used jira before Rally too, and I think it was easier to manage defects in Jira. Also, I think Jira is better for teams and companies that want to implement agile/scrum life cycles. It's easier to …
We started exploring new tools, and found better adaptation of our team toward Jira. Jira provided engineers with simpler interfaces and more reliable service, even though less unnecessary features. Also the managers found in Jira better ability to eliminate noise and focus on …
I've also evaluated the following agile solutions: ActiveCollab, Agile Bench, Agilo for Scrum, Atlassian JIRA, Pivotal Tracker, SpringGround, Targetprocess. Telerik Teamprocess, VersionOne, ZebraPlan etc. If it’s time to transition to software that’s specific to your Agile …
Rally has much more features with regards to the the traditional Agile methodology and has more extensive tracking features for the project managers. Pivotal tracker was used for a smaller company and smaller teams but since my current company is larger in scale and has more to …
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate
If your organisation is planning to adopt Scaled Agile Framework Methodology (SAFe) without being worried about cost, CA Agile Central is one of the best tools. Here, you can look at various release trains and how that then flows up to the overall program budget. You can look holistically across all the release trains with minimal effort and have it flow up to the program office’s budget. It also helps by easily maintaining backlogs and integrating more seamlessly into software developers releases, iterations, and features. It has no conformance issue as it supports almost all the browsers like IE from version 8.0, Firefox from 3.6 and the newest versions of Chrome (from 6.0) and Safari (from 4.0).
structuring teams separately in a clean way. You can add as much teams as you want, and guarantee each team's work would stay separate in browsing, graphs and analytics.
detailed menus and drop-downs listing of features - technically it covers all there is of agile aspects and some more
ability to set your email notifications on/off
ability to split user stories into the next iteration if work isn't done in the previous one - no need to duplicate your user story manually
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Assuming we were paying - right now my group gets it for free as the broader engineering organization pays for it. There would be switching costs. There would be pretty minimal data migration, but the biggest cost is getting people to learn a new tool and starting off on the right footing. Evaluation and identification of the right product is a big part of switching too
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available
The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.
It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.
They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.
I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial
Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.