Azure DevOps Services vs. Microsoft Project Server

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

You will be able to do the project management (scheduling, tasks assignment, resources allocation, cost tracking) for all your projects in one place, where the team members can contribute and keep the plans up to date. The web version does the main job right but if you find it more difficult to use you just use the standalone Microsoft Project and upload the changes back to the server.

Incentivized

• 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.

Incentivized

• Ability to update project plans on the move in any location. Plans can even be updated offline and saved back to the server when the connection is reestablished.
• Visibility of resource assignments across the company allows us to plan project start dates easily and effectively.
• Being a Microsoft product, it is intuitive to administer and easy to configure to our individual requirements.

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• Resource loading and leveling extremely complicated within the tool
• Software makes incorrect assumptions and changes without user knowledge
• Inconsistencies within the tool make it hard to predict & troubleshoot

Incentivized

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.

Incentivized

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.

Incentivized

We don't have to worry about maintenance, upgrades, or compatibility issues. All the capabilities we need are there, and are easily customizable.

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.

Incentivized

Was not part of the process.

Incentivized

Per Microsoft, Project Online provides more value long-term by reducing infrastructure cost and increase feature release cycle time

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

I have used Basecamp which I recommend for all! This is one of my top tools for not only company projects however for projects, meetings, communication outside of work. We use Basecamp for our membership organization's dental meetings in other states to communicate events, chat with participants, send donation requests and organize events on the platform. There really is no learning curve, it's super user friendly, you don't need any experience prior and it's cost effective.

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• Better project management and schedule tracking which in turn improved employee's efficiency.
• Licensing aspect is complex. Issues with onboarding new users to system from licensing perspective.
• Positively, financial review process can be tailor-made which may not require further customization of the tool.

Incentivized