IBM Targetprocess

Organize our software backlog and track all the work items done by the various teams. We also track our issues, bugs, dependencies, releases, and more for all of the projects and teams that work within our IT and technology development departments. Dashboards are then used to track progress across these and to see how they influence each other.

It's pretty decent at what it does and can adjust to many ways of working. So there's a high chance that even if they are outside of software, they could do their work in IBM Targetprocess. Why the score isn't higher is the maintainability of the customizations and how hard it gets with the many portfolios.

We use TP for creating work instructions, capturing decomposition of features and planning.
TP helps developers from knowing what work has priority.

It does the job for creating and using boards visualizing decomposition of features in work items and planning.

The problem is to benchmark the figures and forward to the right target model

it could be more information included

In our organization, we use IBM Targetprocess for Strategic portfolio management, demand management, investment management

Scenario planning needs to be more mature

First time installation and build is easy and oob offerings are good

We're an IT services provider company. We manage all technical operations from the Service Desk to project management in TP.

It is highly recommended for agile teams and less so for hierarchical teams. It is very convenient for executing the work, but for analyzing information and tracking progress, it is very powerful but slightly more difficult to use.

In our organization, specifically in the technology and information department, we use IBM Targetprocess to monitor all devices and ensure the proper performance and functionality of our infrastructure.

Perfect for multiple services that cover a large volume of transactions.

Project, product, portfolio, and resource management.

Tool has ability to do a lot, but in our experience, the UI gets in way of adoptability and user experience. I think we Would have better buy -in and adoption with better UI overall. Too clunky, Can get overwhelming with number of folders. In my opinion, Not intuitive

In my organization, we use IBM Targetprocess to manage portfolio demand, resource allocations and costs.

I think I am likely to tell a colleague that, in my experience, IBM Targetprocess is Highly customizable and easy to use

In our organization, we use IBM Targetprocess for:
Architecture Solution Governance
Workforce Strategy
Work Management/Planning

I think I am likely to recommend IBM Targetprocess to a colleague for the Workforce strategy and planning

I use Targetprocess for my own organization and advocate its use to my customers for overall project planning and better awareness for resources, programs, investments and portfolios available for a particular initiative that is being managed or deployed by a BU. The scope ranges from a large scale global initiative to a smaller project

Targetprocess is best used when there is program or initiative that is being kicked off. Its less appropriate when when its inflight or towards the end of its implementation. the earlier you can take advantage of Targetprocess's features and functionality in program the better and more effective it is for the initiative