IBM Targetprocess

Vorteile

The scope for customisation is wide open. There's an active developer community and the team at TargetProcess invariably respond quickly with a can-do attitude, no matter how in-depth or niche the request is.

Nachteile

Some non-technical users report difficulty in navigating the interface, there being many different ways to complete the same task and lots of detail shown at once. I do not personally find this an issue, but it's something to bear in mind if you're planning a roll-out.

Vorteile

As our organization continues to grow and have more complex needs, Targetprocess can easily handle whatever our needs are and helps us to grow using standardized methods no matter the project. Also, we have many creative people in the tool and it's user friendly for the non-technical types too.

Nachteile

It's great power can also be a weakness, as getting it setup and configured requires planning offline, team alignment and understanding before moving the workflow to a digital tool like Targetprocess. Having someone who understands Agile and programming is best to get this setup for you as its so customizable it can be intimidating.

In Betracht gezogene Alternativen

Warum IBM Targetprocess gewählt wurde

Zuvor genutzte Software

Gründe für den Wechsel zu IBM Targetprocess

Vorteile

The extreme degree of customization that is supported by this product is excellent. I have created dozens of process queues and pipelines for customized business processes that have nothing to do with software engineering. The ability to replace the software-development terminology with other more pertinent monikers is excellent.

Sales pipeline? Check.
Quote tracker? Check.
Business process tracker? Check.
Service tracker? Check.
Construction project pipeline? Check.
Ordering pipeling? Check.

The web-hosted version of Target Process is outstanding for a small company that wants sophisticated collaboration software without a dedicated IT staff.

Nachteile

Ability to generate local back-ups is not intuitive.

Vorteile

* Responsive UI
* Adding many stories at once is easy so doesn't interrupt your flow
* Incredible customer support responsiveness
* Dashboards are 10x better than anything in JIRA
* Reports are built in and very well designed, things you have to buy from 3rd parties in JIRA (if you even can)

Nachteile

* Roadmapping is harder than it looks, some planning features missing means i can't throw away my gantts just yet but it's getting close
* Search results have way too much white space, can be hard to find exactly what you're looking for - JIRA was better at this
* Difficult to learn the filtering side of things for anything more than basic needs (but their customer support team are amazingly supportive on this, even writing a script for me immediately to address my individual need). Oh, this is meant to be the con section isn't it. ;-)
* Workflows aren't quite as customisable as JIRA, such as setting triggers and custom screens

In Betracht gezogene Alternativen

Warum IBM Targetprocess gewählt wurde

Zuvor genutzte Software

Gründe für den Wechsel zu IBM Targetprocess

Vorteile

Tons of good features
Very flexible and powerful

Nachteile

Expensive for companies in Brazil

As we are a consulting company, there wasn't a good (and cheap) way to add clients to the projects with the ability to add comments to cards without purchasing a license.
In some cases there were more than 10 people involved in the project that would have very small interactions. It would not make sense to purchase licenses for everyone.

In Betracht gezogene Alternativen

Warum IBM Targetprocess gewählt wurde

Zuvor genutzte Software

Gründe für den Wechsel zu IBM Targetprocess