Apache OpenOffice vs. Azure DevOps

In my opinion, Apache OpenOffice is best suited for writing, editing and proofreading texts in any language. You can also download additional language packages that really take up little space in your PC's storage. Of course, Apache OpenOffice is comprehensive of spreadsheet-/drawing-/database-related softwares and so on, but I primarily use it for writing and editing my own texts. I don't see any scenarios where it is less appropriate, at least so far.

Incentivized

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

• The number one strength of OpenOffice is the flexibility it gives. We can open any file type, save any file type - it's pretty much invincible. Even if we're going to work on this in a different program, just being able to open some of these ancient files that we get from local city governments is a huge win for us.
• It's also administrator friendly - I'll use it a lot on the road because the licensing is so much easier to deal with than trying to check out a license from a server or make sure that everybody has internet connectivity.
• It just looks pretty! It's legitimately a quality product, the layout looks good, it's not nearly as pushy as "other suites," and for the money it's the best!

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

• Some people used to Microsoft products can feel it's a little bit old in its style
• I saves documents in its native format, which is incompatible with MS Word or Excel, unless you change that in the preferences tab
• The UI is not very pretty

Incentivized

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

It is a cheap alternative; however, with Microsoft 365 licenses also dropping significantly, we might opt to go in that direction to maintain uniformity.

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

It's good overall, just the UI it's not the prettiest, feels like an older version of MS office, but gets the job done. Once get the hang of it it's easy to use, besides it has great documentation on how to use it and there are many forums that discuss many related topics.

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

Is there really support? There is a user forum but I do not see much developer input. Support options are limited. The most recent (Sept 2019) version of the product seems to have issues operating under Windows 10, yet there are few recent comments in the community forum, most comments are regarding older versions.

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

We found that it is possible to use Open Office to accomplish everything we need. Some tasks required searching for steps on Google.

Incentivized

Was not part of the process.

Incentivized

Apache OpenOffice is less intense on our computer systems and saves us a ton of financial resources. Since our document creation and editing needs are typical of a small business and not very complex, Apache OpenOffice is sufficient for us. We think that almost any smaller to medium sized business would feel the same way if they don't have a need to make or edit complex documents.

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

• Moving to OpenOffice will save the company the cost of 500+ of Microsoft Office licenses in our company.
• Because it is cross-platform, we could also save 500+ of Microsoft Windows licenses if we move everyone to Linux.
• On the negative side, the lack of online collaboration and browser support may be an issue when you use clouds like Box, Workboard etc.

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