Digital.ai TeamForge vs. Planview AgilePlace

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

This tool enables the visual management needed in many offshore teams to easily and quickly see the pending work, work in progress and completed work.For teams that work with a waterfall methodology and do not have AGILE internalized, I believe there are other solutions from Planview or other providers.

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

Incentivized

• Visual kanban board that is easy to customize as the team's needs change
• Real time collaboration allowing teams working remotely to stay up to date on current status
• Allows versatility for how a team needs to capture details on the work at hand by utilizing card icons, card types and custom data points
• Card scoring is easy to setup and provides the team the ability to set values to better prioritize their backlog
• Ability to add card automation to take out some of the repetitive manual actions

• 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

• Ability to add more than 1 visual cue to the card. We use custom icons and sometimes more than 1 is appropriate but you have to choose which is most important since only 1 can be applied.
• Better visibility to board access from the user administration screens. Currently have to run 1-2 reports to see this information. Would like to be able to click on a user within Configure Users and see what boards they have access to quickly.

we are happy with the tool and the service and continuos improvement of the tool so there is no need yet to change to another one.

LeanKit isn't the best designed Kanban system I've seen, but overall it's pretty usable. The boards I've used are pretty complex, so it can be difficult to find things. I found that searching and filtering for specific cards was somewhat of a challenge. Dragging a card from one lane to another is kind of a fun way to get things done though.

Incentivized

Not experienced any outage

Incentivized

Larger boards take longer to load

Incentivized

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

Every time I have reached out to the AgilePlace support team I have received a timely response in addition to professional & personal feedback. Their consultants are knowledgeable and the management team is happy to jump in and help when needed.

Very easy.

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

Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration. In the end, we picked Planview LeanKit because of several reasons: Aesthetics: The look was much more clean and professional. Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement. API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it. Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.

Incentivized

Good use cases for small/large teams

Incentivized

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

Incentivized

• LeanKit has made it easier for new employees to understand other employees' roles in the company by seeing their workload.
• It makes it clear who is responsible for what project so that there is more accountability at our company.
• It helps our project manager schedule new projects in a way that we all can see.

Incentivized