Targetprocess Reviews

Pros

Excellent pricing structure, easy to set up, and implementation/training professional services are first rate. The software is powerful and can handle various different approaches to Agile/Agile Scrum, and comes with pre-built solutions for frameworks like SAFe. Our organization was up and running in little time.

Cons

Some of the more powerful features, such as creation of rules could be more straightforwardly implemented. Some features have a "coding" feel to them that could improve in usability, user-friendliness. The software is sensitive to hierarchical structure of Agile entities, and you have to get this right. The ability to move/transform entities into different levels of the hierarchy could be improved, and sometimes can disconnect entities from the hierarchy, forcing the user to reconnect them manually.

Alternatives Considered

Jira, monday.com, Rally and Smartsheet

Reasons for Choosing Targetprocess

Taiga was too limited and didn't support enough of the elements of our Agile Practice and had no true DevOps features. While we liked its simplicity, it did lack many advanced features we thought were important.

Switched From

Taiga

Reasons for Switching to Targetprocess

Customizability, Ease of Use, Quality of the Professional Services Organization, Price, Power of Features

Pros

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.

Cons

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.

Alternatives Considered

Jira

Reasons for Choosing Targetprocess

We migrated from Waterfall to Agile PM Methodology.

Switched From

Basecamp

Reasons for Switching to Targetprocess

Jira was too technical for our non-technical users, such as account managers, creative, copywriters, and media people.

Pros

- Flexibility of the tool, customization options
- Ability to create any kind of process workflow
- Out of the box Kanban metrics
- Representation of data on views and boards in any kind of form, for different stakeholders
- Visual cards and thier options
- Ability to automate process steps with web hooks and metrics

Cons

- Timeline is not useful
- Interdependencies management is poor
- Reporting engine, options are limited
- Customisation of entity view is not possible
- Access management options is limited
- Lack of capacity/resource management functionality
- Lack of Portfolio management (cost management, portfolio roadmaps, strategic dashboard, what if analysis)

Pros

* 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)

Cons

* 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

Alternatives Considered

Kantata, LiquidPlanner, Zoho Desk and GanttProject

Reasons for Choosing Targetprocess

* wanted faster and cleaner UI and larger hierarchy support

Switched From

Jira

Reasons for Switching to Targetprocess

Price, featureset, ease of use

Pros

Tons of good features
Very flexible and powerful

Cons

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.

Alternatives Considered

Jira, Trello and GitLab

Reasons for Choosing Targetprocess

We started working with larger projects that required a better control of the roadmap and we also wanted to have better metrics about our teams and deliveries.

Switched From

Trello

Reasons for Switching to Targetprocess

After watching some videos it seemed we liked a lot the flexibility to create our custom processes. Being able to have cards automatically moving across teams depending on their status was very nice.

Pros

We have found it very clean and simple in the day by day usage, it has powerful reporting functions that helps to keep track of your progression and global performance between multiple projects

Cons

We are missing some functionalities, like the skills matrix tool in order to have a clear view of allocated peoples vs. skills required on a project basis.

Some aspect of the UI can be improved and much polished to be more clean, but we know that its a matter of time.

Pros

At first glance, you can do anything you want with Target Process. It is geared to set up workflows and views the way you want them to perfectly fit your business structure. The more time our team spent in Target Process, the more we realized how it is extremely customizable. Of all of the Project Management tools I have viewed (which is a lot) I have never seen one that would allow you to created as many variations of a project view and related reports as Target Process.

Cons

With all of the customization possible, it is very daunting to get it set up and running. The only reason we did not stick with it long-term is because we had a hard deadline to change project management software, and could not onboard everyone fast enough. Other than that, the only things "missing" are things like bulk edit or moving tasks to a different project. Very minor things.

Pros

That it helps run the business better and faster and they update the software better then the other software programs

Cons

I think it makes the other software programs look bad because they are not as good as the targetprocess

Alternatives Considered

TopNotepad

Reasons for Switching to Targetprocess

Because the other ones are harder to use and do not work well

Pros

The boards are just so intuitive - using a board to estimate user stories, for example, by dragging stories of similar complexity to the same story-point column. Being able to quickly throw together a board to view stories or tasks, on a grid with whatever-you-want as the two axes makes it really easy to understand how your work is partitioned.

Cons

The licensing model makes it hard to share info with non-users. You can generate (and export) lots of reports, but I'd really like to see a read-only licence that lets occasional visitors look around.

Pros

The system is very easy to use and is quite intuitive. Many of our users can easily adopt its methodologies and workflows.

Cons

Connecting to third party tools such as SalesForce and Azure Dev Ops is extremely difficult. There are only 1 or 2 tools and both are terrible.

Pros

Besides the flexibility and robustness of the features and functionalities found in the product, Targetprocess has a great support group found when using their "Live Chat". Their Live Chat personnel who respond to our inquiries and issues are extremely responsive and knowledgeable. And the same can be said for their Targetprocess Support team. Many times when we have discovered an issue or had a technical question, their Support team have provide abridged videos and write-ups that demonstrate the how-to's for resolving or leveraging the functionality of the tool.

Cons

What is Targetprocess' strengths is also its' weakness -- its' extensive flexibility / functionality . . . which is overcome over time by using the tool. Sometimes, you are not certain which approach to use when creating a board / view / list, or wanting to use a report, or creating a dashboard, or exporting the content out as a CSV file for Excel manipulation. But as we have worked with the tool, our various departments have developed SME's (aka Subject Matter Experts) to work with their end-users of the product. This has helped significantly for us, and we have monthly TP user community session to discuss-and-share how various groups are using the tool, and providing each other with tips-n-tricks.

Pros

The best things in TargetProcess are visibility and customization. TargetProcess provides many examples of tickets views for planning, being up to date with daily tasks or for retrospective purposes. There are different levels to look at tickets: you can easily prioritize all the tickets on a backlog and you can plan each ticket separately. We needed customization, because our workflow is always a work in progress. TargetProcess enables customization of both: views and tickets.

Besides that, the UI is very intuitive. Tickets can be written with Markdown.

Cons

At first I missed retrospection views, but then reports were introduced and now you can e.g. make a chart of how many tickets were closed each month.

The only thing that bothers me now is the time needed to first open the TargetProcess in a new tab in a web browser. Apart from that, I see nothing to dislike.

Pros

Their visual flexible boards allow our team to easily see views of our development progress in whatever way we need. This is one of the few products that gets prioritized backlog views right. TargetProcess has become a critical piece of our software development lifecycle.

Cons

It would be nice to see entry-level pricing for small companies. For Start-ups, every little bit helps!

Alternatives Considered

GitHub and Jira

Reasons for Choosing Targetprocess

Needed software that could provide the agile views needed to properly prioritize our workflow and quickly manage work assignments. TargetProcess is so much more efficient than other online options we've evaluated.

Reasons for Switching to Targetprocess

Easy of use and better online reporting.

Pros

For me personally the best thing about TargetProcess is the people behind it. The support is second to none, they respond promptly via email, but usually I use the live chat which is just perfect. Using live chat we have often used the screen sharing facilities and the support person has taken control of our server virtual machine, which I'm more than happy for them to do, I trust them 100%. We've never had a show stopping issue from their system by the way, its very robust and smooth to run, even on a vm.

I also really like the user interface, it looks professional and is easy to use. As a developer myself, I understand how hard it is create something like that, so I am really impressed.

They also have great commenting / following system in place which allows people to be notified of updates on stories that are specific to them.

It's generally a great, stable platform which runs very efficiently on minimal hardware.

Cons

Generally the only thing I have disliked is the learning curve switching from the TP2 interface to TP3. If you are a new user of course, you wont have this issue as you will just be using TP3 interface. The TP3 interface is very good, very flexible and looks awesome, it's just very different from the TP2 interface that I was used to.

Pros

1. Features & Stories list view
2. Consistency
a. Done is always visible in Grey
b. Green + button to add stories, tasks etc
3. Customization of boards and views
4. Reports
5. Clean UI
6. Information found in the burn down chart details
7. Timesheet view for our teams

Cons

1. Sometime performance is slow
2. Wish I could add points, tasks, hours to Bugs.
Workaround - we make everything a user story and put the word "BUG:" at the beginning of the story/task and set it up to automatically turn red.
3. Sometimes can get lost trying to create a report/board etc and it does not feel intuitive

Alternatives Considered

Jira

Reasons for Switching to Targetprocess

Boards, views, clean UI.

Pros

Works very well for the actual creation and collaboration work around users stories in an agile project environment. The cloud/SAAS prodcut

Cons

Tracking and reporting at a project level is still very weak. The ability to easily roll things up to a project level is still very difficult and the internal reporting abilities is still lacking. Even the most basic information has to be extracted to Excel or another reporting tool. Would help to have some basic end-user reporting functionality.

Alternatives Considered

Jira

Reasons for Switching to Targetprocess

Cost.

Pros

Highly customizable - you can set up everything as you want it.
There's almost nothing you can't do.

Cons

It takes a while to get to learn all the capabilities of TP. I'm the company's expert and each new person who needs to learn it still takes time to learn it.

Alternatives Considered

Jira, Wrike and Asana

Reasons for Switching to Targetprocess

Price, customizability, UI, capability

Pros

Target Process offers a lot of functionality to make it very useful for most organizations, large and small. I particularly like that it combines all normal ALM functions with basic PM functionality to track progress. I also like that it isn't just focused on software and Agile, but allows you to adapt it to your needs. We use it for both hardware and software with equal effectiveness. Customer support is excellent and they will even perform supported customization for you.

Cons

Learning to use the views isn't intuitive and lacks the ease of use of an advanced search to find the items you're looking for. The test functionality is a bit of an after thought and doesn't allow some needed features, like reuse of test steps and test parameters. We use this to manage all requirements and there is no easy way to get those into a nice printable format. I know they are working on more item customization, but I'm use to TFS and having complete control over the fields, layout, and rules.

Pros

Ease of use and constant improvements.

Cons

For me, there seems to be some obvious functionality that is not included such as duplicating user stories, tasks, test cases and such.

Pros

Easy to use - 2D drag-and-drop for cards in Iteration Plan mode is intuitive and straightforward. Quick to create new cards, assign them to features & releases & sprints, etc. Plenty of ability to customize for smaller organizations, no need to slog through lots of mandatory fields, steps, etc.

Cons

UI is sometimes touchy, especially on a small screen. Dragging a card to a new state, paging forward & back through iterations.
I wish you could define defaults for things like the Project field when creating a new card - right now it defaults to alphabetical order.

Pros

Very reliable. Fully customizable. Easy to use. Full of features. Very modern.

Pros

My team and I were able to get started on this product right away and our user did not take long to onboard.

Cons

Overall my experience with this product was great. The only thing that was maybe lacking was some other features that competitors offered.

Pros

Ease of use when you want to create a new board, also the boards configuration is very powerful, with lots of possibilites of filtering and visualization tips. Despite this, if you have any doubt or question you can contact with their support team by on-line chat, every time I contacted they have solved my doubts.

Cons

Lack of information and/or manuals about DSL language to edit or build new reports.
In our case the notification system don't work properly and seems to send messages to people who do not have to receive them.

Pros

We utilize TP daily for all of our project tracking and testing purposes. We have multiple product software suites that we continually maintain/update, and using TP allows us to easily coordinate and plan the hierarchy of those enhancements. We use this for testing new enhancements, as well as production issues and additional feature request enhancements.

Cons

When pulling reporting and exporting to CVS, there are limitations to the number of records that can be exported. We have learned to filter down our reporting and pull in multiple requests.

Pros

The best thing is that I can develop my own processes in the tool. I can translate the needs and requirements of my clients exactly. Thus, I can build a IT supporting project management adapted to the company. Sometimes I do not get ahead when programming my user-specific requirements. But the customer support is really fantastic. There is a contact person of TargetProcess has contacted me. This person has processed my problems always directly. Either he can solve the problem directly or he has informed the competent developers about it and the challenge was eliminated in the shortest possible time.

Cons

I find it a pity that the tool is not yet available in German. I personally have no problem with it, but many executive employees who do not speak English are working with this tool. This has already cost some nerves among employees. But it is positive that the employees also learn a bit of English.