Admin Insights
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
Currently, my company implemented TeamForge across all of it's IT, for use in monitoring codebases, as well as integration/tracking changes. We use this implementation for restricting access as native GIT does not supply such limitations. And in small ways, we use this for tracking with Agile projects, tying into Version One.
Pros
- Code security.
- Code migration.
- Agile tie-in.
Cons
- Backing out of changes could be better with their interface.
- Determining what user groups are assigned to what repositories can be challenging with my companies current implementation of TeamForge.
- Sometimes we have to get work around for TeamForge to interface with other Agile tracking options. TeamForge has its own tracking method and is not designed to hook up to third parties. They'd rather you use their product.
Likelihood to Recommend
As long as you are looking for a tool that segregates who can do what with a given repository and branch in GIT, and do not mind strictly using TeamForge's Agile tracking software that comes native to the application, this is the tool for you. The tool is fairly user-friendly, and they have an excellent support staff. You're really buying that support, more than anything else. If however, your company insists on using separated agile tracking software such as Version One, I would not recommend TeamForge. They prefer an all or nothing kind of deal.