Digital.ai TeamForge vs. Planview PPM Pro vs. Rally Software

CollabNet TeamForge is more well-suited for technically knowledgeable users such as developers, systems analysts, QA but not for non-technical users due to the technical data used throughout the tool. CollabNet TeamForge is appropriate for most applications development. In any industry especially suited for high demand software delivery environments.

Incentivized

PPMPro is well suited for tracking new product introduction projects, as well as process changes. It serves to reliably track ongoing action items, issues, resource allocations for projects. Areas where PPMPro is less appropriate for use: Project to project dependencies, automating action item notifications on multiple platforms, integrations of PPMPro into other platforms PMO typically uses (like MS Projects, Teams, ppt, etc)

Rally Software is well suited for large Agile or scrum teams who do sprints and it helps managing sprints and backlogs. It is well suited for organizations who want visibility into work being done and progress. Suitable for tracking is user stories, defects and release planning. Works well with CI CD too. It would not be suitable for small teams or startups. For teams that don't use agile. Teams who want lightweight tools like Jira. Companies with a limited budget.

Incentivized

• Code security.
• Code migration.
• Agile tie-in.

Incentivized

• New request workflow/kanban board helps visualize where new requests are in the process of the quote to cash/request to completion
• The time tracking tool is tied directly to project tasks for seamless integration of time tracking, estimates, and actuals
• The reporting capabilities and ease of use has allowed us visibility to data that we never had before
• The tool is easily configurable by Administrators. We can add fields, change reports, add new dashboards within hours vs. days of trying to track things manually

Incentivized

• There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
• Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
• Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
• Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
• Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
• It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
• CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
• The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
• CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
• Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.

• I would like to see personalization for managing artifacts, that is, allowing the user to customize pages and save personalized settings and then save them as bookmarks.
• I would like an improved subversion browser such as a graphical user interface rather than a basic file explorer.
• I would like built in features for CollabNet TeamForge integrated with subversion so that i can associate my private code branches and code changes.

Incentivized

• The base API is not a REST based interface and is difficult to use for integration with other systems in the enterprise.
• The UI for the maintenance of the task schedule for projects can be a bit cumbersome , although the spreadsheet style editor helps somewhat. The Gantt view is not interactive.
• The workflow engine is designed only for initial project intake, and does not allow for an integration of the work flow with the project from start to end, so it can't be used for routing artifacts like change requests, ancillary project approvals, etc.

Incentivized

• User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
• The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.

Incentivized

Because I never evaluated other tools, I would be open to considering others. Given our establishment with Innotas and the value it has provided us, separating from it would cause some organizational discomfort. However, if a tool existed with a more intuitive interface for manipulating the data and factors of projects and resources, I would be very interested.

Incentivized

• To keep connecting my people, platform, and process for faster, smarter, better results.
• Making the right contribution to the community. Use Agile and Lean processes to manage the work of your team.
• Once you have tasted the positive result with Rally Software, you don't want to give up and come back to the old school of development pain any more.

Incentivized

PPM Pro has very effective process capabilities around Project, Demand, and Resource Management as well as Reporting/Dashboards. Very stable platform, never any downtime. We now also have PPM Pro Sandbox which we have leveraged for any new major developments such as Request Management.

Incentivized

Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available

Innotas is very rarely down if at all.

Don’t recall ever being unavailable.

No issues with overall response time and performance. There have been some occasions where a Report could take few minutes to render but this is vary rare. No integration issues...

Incentivized

The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.

They always answer the phone when we put a call in, any time. They have consistently sent out contractors when needed and were there every step of the way when we switched over from ClearCase to TeamForge years ago. The support is what you really pay for when you buy into TeamForge.

Incentivized

Their ability to assist and answer questions when needed is incredible. They create innovative ways to share information and help customers trouble shoot. I didn't give it a ten because I believe they could do a better job of personally reaching out to customers and providing improvement guidance based on where the customer is at and their needs at the time

I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.

Incentivized

Tim Srjezter was an excellent trainer.

It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.

They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.

I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial

It's been since 2009. A lot has changed. We have not grown as much as we could have because of executive backing.

Incentivized

Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page

Incentivized

CollabNet TeamForge is superior to Mercury mainly because it has a subversion change management tool integrated with the product. CollabNet TeamForge offers more complexity but with more flexibility for managing and tracking projects. I think
CollabNet TeamForge is more comprehensive than either Mercury and JIRA. They're all user friendly tools with short learning curves but CollabNet TeamForge is most efficient in my experience.
JIRA was recently adopted for particular applications and is currently being evaluated by various technology teams.

Incentivized

Microsoft Project does not integrate the data or provide meaningful dashboards. We needed a tool that could manage a portfolio of projects versus just a single project view. In addition we needed a tool to track financials and internal effort all integrated into one product. Planview PPM Pro addressed all of our needs

Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.

Incentivized

I have no issues with current licensing and renewal terms...

Incentivized

We have always used PPM Pro across multiple Business Units and Business Functions and have never encountered any scalability issues. PPM Pro offers flexibility in how the various Entities are configured across the Enterprise

Incentivized

Very effective and flexible - we obtained a pool of consulting hours that we can use at any time over 12 month period. Consulting topics can vary as we explore new functionalities in PPM Pro. Very easy to schedule ad-hoc time with PPM Pro consultant

Incentivized

• Unfortunately, I do not have access to ROI information.

Incentivized

• Planview PPM directs all the resources in the right channel, hence, credible performance.
• Planview PPM initiates proper time, and resource tracking and hence is friendly for company functions.
• Planview PPM is competent in managing diverse projects, and this offers highly sustainable business continuity.

Incentivized

• it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
• with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
• too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise
• Kanban board support is lacking

Incentivized