Azure DevOps Services vs. IBM Targetprocess

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

Apptio Targetprocess is well suited to track work and progress of that work. In addition it is easy to tie that work to OKRs. Cost and hours rollup across the work hierarchy works well. Our users like the flexibility of Targetprocess and the ability to develop their own views and reports Scenarios where it is less appropriate is to do executive level reporting and develop reports that can pull in all of our time data since there is a 300k record limit

Incentivized

• Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
• Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
• Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.

Incentivized

• Basic flexibility out of the box is a big advantage for a small company without resources to customize, as is needed for some of the larger competitors.
• The support is second to none. They've even written custom TP queries to get me what I want.
• They have managed to cover all the basics of product development in one product, in particular, the inclusion of customer support (although limited) is a big selling point for a small company.

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• The UI is bit complex for new users who never used it. i think this can be sorted out by providing the steps to access?
• dashboards with large datasets can cause performance lags or timeouts
• Introduce more flexible, template-based RBAC configurations.

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

Targetprocess is the most flexible application for tracking work among teams that we have found. This power comes from near limitless ability to customize your views on the work tracked in the system, and from the myriad reporting options to draw metrics and stats out of the data there. Custom fields, processes, and mashups all add to this flexibility and appeal.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

The UI is intuitive and consistent. The complexity of the app means there is a steep learning curve though, but it is well worth putting in the effort to get the most out of the tool. We have some team members who are learning new ways of doing things after 1-2 years of working in Targetprocess.

Incentivized

Some minor outages are experienced, though these tend to pass within an hour usually and work can continue

Incentivized

Reports are fast loading, considering they can refresh in a second or less and we have 7 years of work tracked in over 40k entities. Pages can load slowly when the views are very busy, but not frustratingly. I am a console user most of my career and generally prefer it over webUI interfaces, but Targetprocess won me over from the beginning and I spend half my day using it now.

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

TargetProcess' support is one of its strengths. The support team is very responsive and helpful when there is a problem but they're also proactive in providing good release notes and engaging with the community through a voting scheme to influence the priority of new features.

The team also releases new versions frequently with new features but with no knock-ons to currently working features.

Incentivized

Was not part of the process.

Incentivized

You should take some time to get everyone to agree how the system should be setup before work starts being tracked in Targetprocess, this avoids difficult and disruptive changes to processes or plugins later when everyone relies on it daily.

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

Targetprocess was all around the better tool. They do not nickel-and-dime you and you don't have to deal with multiple products that do, or do not, integrate well together. Below are some of Targetprocess' biggest strengths:

• Highly customizable; can fit the needs of almost any team
• Robust reporting tool
• Easy to use and administer
• Provides all the functionality an agile org would be looking for
• Support team and user guide are phenomenal.

Incentivized

We use the hosted version of Targetprocess and have never run into limitations or degraded performance due to scalability. Excellent performance over 7 years!

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• TargetProcess is my all-time favorite project management software that enables me to work collaboratively and also enthusiastically with my colleagues.
• Before its invention, emails were difficult to handle in the past but now to make connections better I only trust this application because it’s a good intuitive to work in the form of group.
• It provides me a quite useful view that facilitates my working in a way that I can create a customized view of all my ongoing projects.

Incentivized