Azure DevOps Services vs. Microsoft Planner

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.

Microsoft Planner is a user-friendly visual tool for organizing tasks and workflows. It’s great for team collaboration, integrates seamlessly with Microsoft 365 tools like Teams and Outlook, and offers flexibility for projects of all sizes. Additionally, it provides mobile and web access for seamless productivity on the go. That’s a big plus right there.

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

• I love the ability to tag and untag others as needed
• I love the ability to customize the tag labels and that there are so many options
• I love the ability to add comments and it notifies the others tagged in the task
• I love that the task description can be changed as needed without notification to others assigned to the task

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

• Does not allow you to view all tasks and sub-tasks (checklist) in a nested view.
• Comments have character limits that can make it harder for teams to communicate exactly what they want to share.
• There is no way to mention a teammate in a comment and share files and documents in the conversation (collaborative tool???).

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

It is a very useful tool that brings teams in sync with one another. The integration with other Microsoft products makes it an obvious choice because you don't have to purchase a license for a completely different tool that doesn't have cross-functional capabilities with the software you already use on a daily basis.

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

The tool is easy to use, but it is just as easy to set up. No specific skills are required, but its usefulness in our work is immediately apparent. Colors are very helpful in creating a clear interface and providing a very precise overview of the tasks to be performed.

Incentivized

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

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

Our organization chose MS Planner because it is an included tool in the MS Suite, and since we are unfortunately replacing our current and much better project management tool due to a consolidation of the tech stack. However, it doesn't appear that any of the teams using the current program intend to use MS Planner due to its poor functionality. We will likely be pivoting to Jira instead.

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

• Saved over $1000 each year by not having to purchase a third party tool for our content planning
• Not sure that I can provide a hard number to this, but having the oversight to see when something is coming due and making sure everything gets executed in time

Incentivized