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
Jira Align
Score 7.9 out of 10
N/A
Jira Align (formerly AgileCraft) is an enterprise-ready project management solution, now from Atlassian (acquired May 2019).
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
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.
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.
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.
Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
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.
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
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.
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. The productivity increase we realized with DevOps is worth real money!
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.
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.
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.
