My team is currently using the code review functionality in Visual Studio. Why would we need Collaborator for reviews?
For some teams, basic code review functionality in Visual Studio is enough. If the project you are working on is low stakes, it can be a convenient approach. Still, it does dramatically limit your team's code review process. Through its Visual Studio integration, Collaborator enables teams to customize their review process with custom fields, workflows, checklists, and participant rules. You don't need to leave your IDE to conduct high quality reviews. Mark defects and capture metrics on your process, like defect type and severity, inspection rate, and lines of code reviewed. Since Collaborator also supports document review, your team can review requirements, design docs, and documentation alongside your code reviews. If you need to review multiple artifact types and drive process improvement, it is easy to integrate Collaborator with Visual Studio and ensure that quality is prioritized early.
My developers don't like leaving Visual Studio; will they have to leave Visual Studio to use Collaborator?
Not at all! Your developers can stay in Visual Studio the entire time. The Visual Studio plugin brings the full functionality of Collaborator right into the IDE, from uploading code, to commenting on reviews.
Does the Visual Studio plugin consume a license?
A license will only be consumed when you open a review. Just listing reviews will not consume a license.