I am considering buying SmartBear Code Collaborator for mydev-team to help us coordinate and do code reviews. Cost is not the option/issue here, instead we want to get the right tool for the job.
What is your opinion on using it in a team? What do you like about it? What do you not like about it? Hate? annoyances? Good? bad? Worth getting?
I mean, it's an argumentative question, but I liked the user experience, it's really easy to setup, learn and use.
Just, in my experience, the most important part of peer code reviews is to start doing them and the tool itself is of second importance, you can use basically any diff tool. So, for small teams and project the Code Collaborator might be an overkill, there would be too much formalism.
I'm a big fan of the smartbear. I've used it to great success with remote teams. The above post hits it pretty dead on, easy setup and easy to use. We didn't use any of the workflow functionality, so I can't comment on that. We just tried to be disciplined enough to use it whenever we were touching code other people would be concerned with.
SmartBear's Code Collaborator takes all the chores associated with a code review and automates them. Packaging the code up for a review, providing feedback exactly on the line that you want to comment on, sending the feedback, responding to the feedback, arguing over a line or issue, and so on. Developers actually start to enjoy doing reviews. The defects that the reviews prevent are one of the most hairy ones. I had one of the best software engineers tell me that there was no way that the team would've found a given defect without the review, because it was obscured by other behaviors. But in the review they were staring at the code and the code didn't make sense, so they fixed it.
We also coined the term "reverse code review." This is when an experienced software engineer sends a review to multiple less experienced software engineers with the intent of sharing a solution or teaching a pattern. It works well to improve the strength of the team.
Two of my teams have used it so far, and both consider it a useful tool. The first team told me to figure out how to pay for it, because they don't want to give this tool up after the eval period was over... Disclaimer: I wrote a chapter for the Best Kept Secrets of Peer Code Review book. But that came only after we used the tool, and absolutely loved it.
This tool is critical and not just for remote teams. Ever want to check something in but the "right" code reviewer is on vacation so you get the absolutely wrong guy to do it? We've found literally > 100 bugs in our software this year through code reviews. As you know, when you find it that early, it's much cheaper to fix than if a tester finds it 3 weeks (or more) later.