Digital.ai TeamForge vs. SAP Process Control

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

In my opinion, SAP Process Control is well suited for bigger companies with an already mature Internal Control System as well as for bigger companies who want to completely new/redesign the internal control system. The size of the company, as well as the budget, is quite important when thinking about the implementation of SAP Process Control. A smaller company with e.g., 150 people should think more about implementing SAP FCM.

Incentivized

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

Incentivized

• Native connection to SAP applications
• Automated monitoring process of SAP applications
• Workflow capabilities for control testing

Incentivized

• 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

• Default delivery of controls could be done by SAP on some basic controls like client openings, password controls, etc
• The messaging or customization of messages in different workflows is limited, which could be introduced to enhance the product
• SAP Process control does not have the capability for cloud product monitoring which is required with more SAP cloud products available right now

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

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

The connectivity with other SAP products out of the SAP GRC suite, like Access Control and so on, was key for the decision. Also we had an already mature SAP System landscape as well as having internal processes that were similar to the SAP Process Control standard processes helped us with the decision to implement SAP Process Control.

Incentivized

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

Incentivized

• Automated alerts for controls issues
• Workflow capabilities; however, there's natively only 2 levels of review. More layers would be beneficial.

Incentivized