Backlog vs. AgileBox by DevSamurai vs. Digital.ai TeamForge

ticket management

Well suited:

• Estimation of user stories in agile team.
• Recording the estimations and events directly to JIRA.
• Estimations can be done without leaving JIRA.
• Best suitable in this pandemic situation as most of the people are working remotely.
• Different estimation scales are present to adapt as per the team norms for example Fibonacci, T-shirt sizing and custom estimations as well.

Scenarios where it is less suitable:

• Where only inbuilt chat box from DevSamurai is used. So synchronization is an issue there.
• And apart from that a consistent internet connectivity is required.

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

• Backlog is one of the best management and collaboration tools available in the market for better managing of resources at the workplace.
• I have been using this platform for a very long time and it has been helping me a lot to manage the business processes, manage employees, managing leads on different projects, and coordinating with colleagues.
• It has been helping me a lot to check the issue in the project completion.
• It gives me real-time status on the project/gives right insights of the system.

Incentivized

• Usefull interface.
• Don't need any training for using guide.
• Challenging.

Incentivized

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

Incentivized

• Price is very high for small teams and department of short term contracts.
• GUI can be more intuitive.

Incentivized

• Live chat box feature need to be improvised as it still not robust.
• Integration module should be flexible enough to stick with other workflow tools.

• 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

nice to use in the night as well

I would give 9 but one less because of the high price.

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

Backlog has all of the top-notch features to increase productivity, visibility, and project tracking. Backlog is easy to use. I first just logged in to the platform and it was [ready] to go. I easily started working on it and it started giving me the bugs’ details on our project. Always available for queries. Listen to the queries very attentively and try to give a solution on the go if applicable. Otherwise, take some time and respond with the advanced workable solution in the limited time frame.

Incentivized

The only application we use in planning poker studies in the organization.

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

• SLA should be given by single candle

• Estimation of user stories and updating the JIRA is automated and hence resulted in reduced efforts in poker planning.
• No need to be present under same roof for estimation, and hence a flexibility which is much required in this scenario.
• Clients can have a clear and better picture of estimation at any time with all statistics and hence customer sees more transparency.

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

Incentivized