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)
BMC Track-It!
Score 6.4 out of 10
N/A
BMC's Track-It! (formerly Numara Track-It!) is an IT asset management, IT help desk, and license management solution.
N/A
Pricing
Azure DevOps
BMC Track-It!
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
Offerings
Pricing Offerings
Azure DevOps
BMC Track-It!
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure DevOps
BMC Track-It!
Features
Azure DevOps
BMC Track-It!
IT Asset Management
Comparison of IT Asset Management features of Product A and Product B
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.
Track-It! is great for a small-to-medium sized enterprise that has a fairly small IT department but needs far more control of tickets than just email and spreadsheets. It scales well enough as IT departments grow, adding techs is simple enough, as is changing the workflow. A large company would probably be better off with a different solution. The lack of easy customization, and the shortcomings it has in workflow templates (which would be a nightmare for project management) means it won't scale up that far.
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.
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.).
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.
We have rarely needed to use Support for BMC Track-It!, but in the times that we did need to use it, they were excellent. The biggest issue is that after not paying for support for about three years, now that we NEED support, it is too expensive for us to receive. This is due to the way their support is billed. So long as you never drop support, then you should be fine.
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.
BMC Track-It! is much more bare bones compared to ServiceNow products, and if your department has the money, ServiceNow is a much better option. Not only is the Knowledge Base much easier to create and publish articles, but the asset management in BMC Track-It! is practically useless. BMC Track-It! is more cost effective, and with a small amount of technicians there's likely no reason to need a bigger solution, but it leaves a lot wanting.
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.
The biggest positive impact it had on ROI was that the software itself didn't require any expensive ongoing maintenance contracts since it was installed and managed by our organization.
The negative aspect of this is if there was a major problem with the software, then it would require contacting the vendor, at which point it could become expensive for a service call.
