Azure DevOps vs. Microsoft Visio

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

Incentivized

Visio is by far and away the best tool that I have used to do Value Stream Mapping sessions with the warehouse I support. It has all of the shapes needed built in to be able to represent all areas of the processes. I also like how you are able to make the drawing as big as needed and when printing it out of Visio you have the ability to use the necessary paper size. The biggest complaint that I have with the software if how it can be cumbersome for non-Visio users (that is, people without a license in the orgnaization) to interact with the Visio Map. We normally have to dedicate one Visio SME to be able to make the changes that Process SME's find since they do not have access to the software.

Incentivized

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

Incentivized

• Microsoft Visio is excellent for organizing thought processes related to our more complex research.
• The diagrams created with Microsoft Visio are ideal for graphically displaying the internal organization of work and research groups through flow diagrams.
• Microsoft Visio is a great tool for managing our students' activities by creating flowcharts that help us graphically visualize the steps of their group work.

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

• When navigating through swim lanes, the user must be careful between switching from the point to the connection features as it can be difficult to remember which mode you’re in.
• When drawing “decision points,” it can be difficult to type words like “yes” or “no” between the connection lines.
• The exporting options aren’t ideal. They are hard to create in PDF format.

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

We use Microsoft Visio to keep our diagrams updated and to that end we will need the subscription to keep using the software. Otherwise we will be left with PDF versions of the diagrams.

Incentivized

It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).

Incentivized

I have always struggled with some basics, such as connection points, object alignment, font consistency, arranging layers and their order (bring forward, send backward), and managing overlap. I usually need to create an initial rough draft and then do a separate cleanup pass to bring the diagram up to my quality standards. If I skip that step, the result generally does not look very good. And once a diagram becomes busy or the file gets large, Visio has been unstable for me in the past, including occasional crashes that caused non-recoverable edits.

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

Overall, I feel that Microsoft's support is weak. They are now such a behemoth that their model of putting documentation online for their users to sift through is totally outgrown. Given the amount of money you pay for these licenses, Microsoft should provide easy one-on-one support for their products via email or chat. The idea of paying their rates for support incidents is ridiculous. If you have an enormous amount of time on your hands, use their support websites and you will eventually find a solution most of the time.

Incentivized

Was not part of the process.

Incentivized

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.

Incentivized

Even though it’s a more expensive solution, Vizio is built for the enterprise. Therefore, it integrates perfectly with our existing Microsoft stack, and quite frankly, because it’s such a more mature product, it provides exactly the functionality we need and expect.

Incentivized

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

Incentivized

• Reduces the amount of time I need to create process flow diagrams. In the past I would use Powerpoint or Word which required a lot more effort and time and never looked as good. Visio just takes that headache away.
• Only negative is that I personally believe it should always have been part and parcel of the Office suite, thus giving more users the opportunity to use it rather than specifically having to justify its separate purchase within our organisation. Different now with Office 365 of course!

Incentivized