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)
Azure DevOps Server
Score 8.4 out of 10
N/A
Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. 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
LibreOffice
Score 8.8 out of 10
N/A
LibreOffice is a free and open-source Office Suite from The Document Foundation, presented as the successor to OpenOffice.org. The suite includes Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing).
$0
free and open source under the Mozilla Public License v2.0
Pricing
Azure DevOps
Azure DevOps Server
LibreOffice
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)
Basic + Test Plan
$52
per user per month
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps
Azure DevOps Server
LibreOffice
Free Trial
No
No
No
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Azure DevOps
Azure DevOps Server
LibreOffice
Considered Multiple Products
Azure DevOps
Verified User
Manager
Chose Azure DevOps
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software. On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
Compared to other tools we have used, Microsoft STS has been a much more complete tool. Communication, collaboration, tracking, management, automation, testing, speed to production—all these areas have been improved since we started using Microsoft STS. We have been looking for …
Our TFS was dated and in some ways was quite crude. VSTS is thoroughly modern and I don't have to worry about updating it since MS is always updating VSTS. Also, VSTS has better integration with other products such as JIRA than our older TFS would. I am sure you could integrate …
With more functionality added, JIRA has become slow, whereas VSTS is a pleasure to use. Trac and JIRA do not show the entire health status of the pipeline like VSTS. Hygieia is open source and trying to achieve what VSTS does but it is not as mature yet.
Being its predecessor, VSS has a very limited team-sharing view, providing little to no multiple-user, multiple-project support. Considering the fact that Microsoft has purged its support in favor of TFS and VSTS, it's only reasonable to believe they have something extra. Git …
Haven't used a lot of similar products that have the full feature set as Visual Studio. It's highly effective development platform especially when used with SVN and TFS makes large Agile project easy to manage and collaborate.
I haven't used any other products, so I can't say how VSTS/TFS would stack against any competitors, but I know that for an SDLC management tool, VSTS/TFS has everything you need to help an organization meet the requirements needed to adhere to the specific/general practices …
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.
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.
If you're working with numbers, LibreOffice doesn't get in your way and try to make changes as it sees fit, forcing you to repeatedly go back and undo processes you didn't want, didn't ask for, and that have no place in the document you are trying to produce. All I want to do is assemble the data, process it for the task at hand, and then print it for distribution. LibreOffice allows me to do that.
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 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.
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.
We use it consistently and have a lot of documents in the OpenDocument format so it will be necessary to use LibreOffice or a compatible product such as Openoffice in the future to be able to open these files. Because the license fee for Libreoffice is zero it is not very costly to keep using it - the costs are mostly for keeping it installed on the office PCs and regularly updated, and solving employee issues with the user support.
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.).
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
For all of the reasons in the foregoing evaluation. Its menus are clean, intuitive and straightforward. Any function I need to use can be accessed via keystrokes, without having to stop, move my hand to the mouse, deal with it, and then get back to the keyboard to proceed. It helps me keep my mind on my work and not worry about dealing with the mouse all the time.
Libreoffice is a desktop app not requiring any server part so it is always available when the PC is working normally. Installing it on another machine if one PC fails is very quick and easy. This is a non-issue.
For big/imported tables or text documents with images loaded from the internet it is sometimes getting very slow, RAM and CPU intensive, and sometimes even hangs due to some memory leaks or other bugs. This is a long-term problem and is still not resolved perfectly.
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.
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
Support is not officially offered. However, you can find answers to any usage questions or trouble-shooting online easily, typically starting with a Google search. (I believe that all forums / tips for OpenOffice apply equally to LibreOffice, and vice versa.) While Microsoft Office, for example, officially includes support, I find that typically you end up going to a Google search in any case. So, this is not really a downside. However, in all these cases, you end up doing a lot of figuring things out for yourself.
Generally easy to perform, issues are how to ensure regular automatic updates on Mac OS X. Fortunatly we have only a few machines with OS X run by management and we can do these updates manually occasionally. Windows updates are quite easy with the support of third party software such as Ninite or Chocolatey, and Linux updates are super-easy thanks to the package manager (apt-get).
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.
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!
If you are looking for a well-rounded, GNU-licensed product that will encompass word processing, spreadsheets, presentations, and database then LibreOffice is probably all you need.
For online collaboration, links with cloud storage, and more robust support, Microsoft Office 365 and Google Docs are probably what you or your organization needs.
LibreOffice is at its best for regular document creation and spreadsheet management. It is more cumbersome when it comes to fonts but also when it comes to linkages with cloud-based services. It is there, but you need some more computer knowledge to make it work.
There are other free alternatives, most notably Apache Open Office, which is also a very good alternative if you do not like LibreOffice.
Having said that, I honestly think off-line computers or laptops used off-site can certainly benefit from having LibreOffice installed.
With more users using it in the company there are more cases when a simultaneous editing of the same document is needed and this feature is lacking in Libreoffice even though the files concerned are shared and synced by some solution (we use ownCloud). Google Docs or MS Office365 via Sharepoint/Onedrive offer a better function for this.
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.
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.
I am able to quickly create and edit word processing documents and spreadsheets which are for all intents and purposes equivalent to documents I could create and edit in other tools such as Microsoft Office and Google Docs/Sheets.
Lack of an online portal for sharing documents necessitates the use of Google Sheets for automation/integration. Ideal would be an all-in-one solution.
Having open-source software that provides common functionality eliminates the need for expensive licenses.
Lack of dedicated support is negligible. Most issues can be resolved using online search.