Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Cisco Catalyst SD-WAN
Score 8.8 out of 10
N/A
Cisco Catalyst SD-WAN is a software-defined wide area network solution designed to simplify and optimize enterprise network connectivity in complex digital landscapes. It enables organizations to connect any user to any application, whether on-premises, in data centers, or across multiple clouds, with integrated capabilities for multicloud support, security, predictive automation, and enhanced network visibility—all built on a Secure Access Service Edge (SASE)-enabled…
N/A
Pricing
Azure DevOps
Cisco Catalyst SD-WAN
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
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.
The best case, what I recommend to others and to clients to use is Cisco Catalyst SD-WAN one for is the case when you have a huge number of branches or small offices or remote offices, you name it. Even home offices, you have a large number and you want this whole infrastructure to be extremely easy to set up and also to have everything almost the same, not to have deviations from the standard configuration. This is the sweet spot for introducing Cisco Catalyst SD-WAN.
We are able to use a multiple different circuits to go into the cloud, so we are not relying on just one particular private wireless. We're relying on wine circuits, ethernet, ethernet out. So it provides us that flexibility where we didn't have that before. Provides security that is very robust and flexible and scalable and it provides us with, the biggest thing is redundancy, where we have backup. For example, we have a Starlink for nuclear power plants. If our main circuits go down, we have that. And without Cisco Catalyst SD-WAN it would be very hard to actually achieve, to accomplish true redundancy. So we're happy with Cisco Catalyst SD-WAN in that regard.
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.
I will say the way we use it now, and I think what happened was the way it was deployed, it was fine, but unfortunately over the course of the years we've gotten a little out of hand with our device templates and feature templates. I think if there's any form of feedback that I would give to Cisco is how do we find ways to improve the environment as it stands so we get to a certain point with the environment and then we don't know how to undo it or fix it or optimize the environment. Because right now we're in a position where we're playing a lot of catch up and clean up and if there was a way or some tool or feature that we can take advantage of that would allow us to optimize that environment where we will kind of corner ourselves into a lot of problems in the future. There's some feature or something that we could take advantage of that will allow us to optimize that environment and not let it get out of control pretty easily. That would be my suggestion.
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.
I would rate SD-WAN highly because it has significantly improved network performance, reliability, and cost-efficiency for my organization. Its ability to optimize traffic dynamically, enhance security, and simplify management across multiple locations has been invaluable. With SD-WAN, we’ve reduced dependency on costly MPLS, improved cloud application performance, and gained greater control over our network infrastructure.
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.).
The niche configurations are given equal focus as the standard use cases, which can make onboarding difficult in the beginning (ie why am I not using an entire tab of the portal), but aside from that part, the dashboard is relatively easy to navigate and apply the configuration. The metrics and analytics available are also nice to have in a single pane.
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.
Al ser soluciones integradas del portafolio de soluciones de Cisco, el soporte es transversal a cada uno de los componentes implementados, teniendo el cliente la capacidad de resolver sus inconvenientes bajo una misma infraestructura que está totalmente homologada, satisfacciendo de esta manera, las necesidades del cliente asi como permitiendo, que este se concentre en su negocio. Since the Cisco SD-WAN tools are a part of Cisco’s broader portfolio of solutions, support cross-cuts to each of our deployed components, with our company as the customer having the ability to solve our problems through the same, approved infrastructure. Their support team easily satisfies the customer’s needs so that they continue to focus on business functions.
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.
We've used the old Cisco SD-WAN, which no longer exists. It was a lot more complex to configure what is now called Cisco Catalyst SD-WAN. So they've definitely come a long way in that it is a lot less complicated to set up and template based.
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.
Our branch offices can connect to our enterprise network and the internet quickly and securely, which has helped to increase productivity and reduce downtime.
We have been able to reduce our dependence on expensive MPLS connections, and instead utilize a combination of broadband and LTE connections, which are more cost-effective
The centralized location improves network visibility and troubleshooting process
