IBM Targetprocess
IBM SoftwareExternal reviews
200 reviews
from
External reviews are not included in the AWS star rating for the product.
Super flexible product and project management
What do you like best about the product?
A lot of product management tools force you into their process to use the tool. TargetProcess is super flexible and can be customized to whatever process you want to use with your team/company/group.
What do you dislike about the product?
The pricing is a flat rate regardless of role-type. For me as a PO that is using the tool on a daily basis, the price is more than fair. But, for our developers who are only using the tool to read the details and update the state of a ticket, it's too pricey.
What problems is the product solving and how is that benefiting you?
We needed a backlog management tool. We had been using a whiteboard with sticky notes and that was obviously unscalable. TargetProcess allowed us to get everyone aligned.
Best tool for agile teams and organisations
What do you like best about the product?
It is possible to modify all processes in a way that it feeds the needs of an agile team. Not the tool defines your process - the team does, We have expierenced different tools, mainly Targetprocess and Jira. Targetprocess comes with the better UX, easier to learn and modify, scalable for bigger teams etc.
What do you dislike about the product?
Working together with clients is not well supportet. They started a help desk recently - need to have a look at it. And I am missing a comprehensive role concept for clients.
What problems is the product solving and how is that benefiting you?
We are managing our software development projects with Targetprocess. That includes agile methods such as Kanban and Scrum. Other teams (non-software development) are using the tool to organise and visualize their tasks.
Great tool for project and team management
What do you like best about the product?
The custom view creation tool is exceptionally well thought out.
What do you dislike about the product?
The object structure is sometimes a little restrictive (eg: no way to have 2 tasks from the same user story in 2 different sprints)
What problems is the product solving and how is that benefiting you?
All our project management and bug logging is done through Target Process.
Creating bug reports and attributing them to different developers and QA engineers is fast and easy.
Once you setup up your views the way you want them, finding the information you want is quick and painless, allowing you to get back right back to work.
Creating bug reports and attributing them to different developers and QA engineers is fast and easy.
Once you setup up your views the way you want them, finding the information you want is quick and painless, allowing you to get back right back to work.
Recommendations to others considering the product:
If you've adopted the agile methodology, I see no reason to at least try out Target Process for a sprint or 2.
Target Process nails the Kanban Process.
What do you like best about the product?
We have been using Target Process for 3 years. Over those three years our development as gone from just a handful of developers to multiple teams in several departments. As a result our development process has changed significantly since the first day we started using Target Process. We haven't run into a situation where Target Process as failed to met our changing needs.
What do you dislike about the product?
One area I wish Target Process was stronger is in the handling of new requests from our stakeholders. Target Process does offer a secondary product called help desk that is designed to help with these types of requests, but it hasn't been updated in some time so it doesn't have near the level of polish the main product does.
What problems is the product solving and how is that benefiting you?
I don't think there isn't a part of the development process that we aren't using Target Process for.
We used the API Target Process offers to create our own request system.
We use it for time estimation and for sprint planning.
The developers use it on a daily basis. The user story holds all of the details needed for development and we use the comments system to document any communications between all the parties involved with a given user story.
The developers also track their development time in target process.
We also use the reporting to generate various reports for the stakeholders.
I can't emphasize enough how nice it has been to be able to do all of this out of a single system.
We used the API Target Process offers to create our own request system.
We use it for time estimation and for sprint planning.
The developers use it on a daily basis. The user story holds all of the details needed for development and we use the comments system to document any communications between all the parties involved with a given user story.
The developers also track their development time in target process.
We also use the reporting to generate various reports for the stakeholders.
I can't emphasize enough how nice it has been to be able to do all of this out of a single system.
Recommendations to others considering the product:
Have an idea of what your process is, or should be before you move into Target Process. While Target Process is more than capable of adapting to just about any situation. If you have good idea of what you want your process to be the process of getting Target Process will be pretty straight forward.
We moved from a whiteboard with index cards to Target Process in a little over two days.
We moved from a whiteboard with index cards to Target Process in a little over two days.
Almost a great product
What do you like best about the product?
I like the ability to tie test cases to specific user stories.
What do you dislike about the product?
There are several things that almost work the way I want except for one key thing. For instance, splitting a set of stories across two teams is kind of painful. Also, I liked the old TP2 interface and I miss having access to it. Searching by tags isn't intuitive.
What problems is the product solving and how is that benefiting you?
We use TP to track our work. We are an Agile/Scrum organization, so TP is the primary way we track user stories, test cases, epics, etc.
Recommendations to others considering the product:
I think Targetprocess is probably more effective for teams that use Kanban or other "card oriented" development methodologies. It is better if you have a single team working on each project. When there are multiple teams trying to access the same stories, things can get complicated and a little clunky.
Use of TP as a project management and capacity planning tool for our team
What do you like best about the product?
Visual management capacity
Release / Sprint / Backlog / Impediment management
Release / Sprint / Backlog / Impediment management
What do you dislike about the product?
Capacity planning function with Team
What problems is the product solving and how is that benefiting you?
Multiple projects and teams in parallel mode with sometimes several work locations
Awesome Product ! Great Engineering
What do you like best about the product?
Very Intuitive User Interface.
Ease of Use
Feels like the TP team has spent time in analyzing how to reduce the how to reduce the number of operations (clicks/scrolls) for the user to get the work done.
The best feature that i like is User Story Addition / and Addition of Test cases. You can add a user story in less than 5 seconds and describe when you wish to.
Ease of Use
Feels like the TP team has spent time in analyzing how to reduce the how to reduce the number of operations (clicks/scrolls) for the user to get the work done.
The best feature that i like is User Story Addition / and Addition of Test cases. You can add a user story in less than 5 seconds and describe when you wish to.
What do you dislike about the product?
View Customization is still a little complex. sometimes after customizing your view you don't see the rows generated. Its only after some experience you would understand how to generate a view. But i am sure these people will come up with the most simpler way of handing views.
What problems is the product solving and how is that benefiting you?
Earlier i used to spend a lot of time creating business requirement document no I do not spend time creating any business requirement document.
1. Add Project
2. Define Features
3. Add User Story
4. Describe User Story
5. Estimation.
Its all so simple and quick. Since Business requirement documents keep changing i put all my ideas as comments and share with the team. Once a month we review all the comments and modify the story description.
1. Add Project
2. Define Features
3. Add User Story
4. Describe User Story
5. Estimation.
Its all so simple and quick. Since Business requirement documents keep changing i put all my ideas as comments and share with the team. Once a month we review all the comments and modify the story description.
Recommendations to others considering the product:
My Recommendation would be
a. Please simplify the views
b. In earlier versions of target process iteration planning was simpler now i see its a little difficult.
c. We are interesting in people specific / feature specific / user specific performance reports. I have already mentioned this in previous survey.
d. Security : Sometimes we work with part time developers we wish them to just view a certain part of the project say only a couple of stories. we can do that as of now.
a. Please simplify the views
b. In earlier versions of target process iteration planning was simpler now i see its a little difficult.
c. We are interesting in people specific / feature specific / user specific performance reports. I have already mentioned this in previous survey.
d. Security : Sometimes we work with part time developers we wish them to just view a certain part of the project say only a couple of stories. we can do that as of now.
Visibility and customization
What do you like best about the product?
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. There is an API, so you can perform regular remote backup.
Besides that, the UI is very intuitive. Tickets can be written with Markdown. There is an API, so you can perform regular remote backup.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
We have one team with scarce number of developers but we have a lot of projects and tickets. Our main problem was filtering and prioritizing the tickets so that we don't have to go through the list of not important tickets too often. TargetProcess enables that and also provides the views to see all the tickets of many projects on one board but also enables filtering out or inactivating a project.
Secondly, Kanban boards are of great importance for us. Thanks to them we can easily change a property of a ticket or relocate a user story between features. That is an irreplaceable help when you have a lot of tickets.
Thirdly, we know it too well that tickets times estimates are prone to mistakes and thus team sprints time boundaries change. In TargetProcess it is very easy to edit a team sprint start and end time, no need to tediously go through all the tickets of a team sprint.
Secondly, Kanban boards are of great importance for us. Thanks to them we can easily change a property of a ticket or relocate a user story between features. That is an irreplaceable help when you have a lot of tickets.
Thirdly, we know it too well that tickets times estimates are prone to mistakes and thus team sprints time boundaries change. In TargetProcess it is very easy to edit a team sprint start and end time, no need to tediously go through all the tickets of a team sprint.
Recommendations to others considering the product:
It's really worth a try and can be of much help, once you set and customize some tickets views.
Good product with a great roadmap to complete
What do you like best about the product?
Intuitive visual interface, speed and easy to user / setup. Great improvement since last major version (2).
What do you dislike about the product?
The reporting seems to me to be the major leak. Must find a better solution for reporting, also easy to setup.
The capacity planning and days off is also a must have to allow teams / projects / companies to plan properlly the work.
The capacity planning and days off is also a must have to allow teams / projects / companies to plan properlly the work.
What problems is the product solving and how is that benefiting you?
Reporting and daylly work visibility / planning.
Target Process & Ease of Use
What do you like best about the product?
That is seems to capture all the elements needed to have multiple teams and business areas review the details, criteria, action plan and that we can all experience this communication in one place via requests, stories, tasks, etc.
What do you dislike about the product?
The search feature in TP3 is hidden, unlike in TP2.
What problems is the product solving and how is that benefiting you?
Having one collective place to work a user story so communication does not get lost, or in the case of email folks get dropped from an email conversation but as long as that user is in TP they are in the loop. Less running around the office to visit others to discuss user stories and criteria, which equates to more productivity.
Recommendations to others considering the product:
If a company is looking to cut down on disturbing others during their work day and will use TP as the source of all information, they will find their productivity is increased.
showing 161 - 170