Feature and Review branches are a great idea. It just makes it so easy to work in parallel on different things, and to context-switch when you get blocked. Honestly, I can't remember how we used to solve these problems with SVN. If you're in the middle of developing a feature and need to wait for someone to get back to you, the options for switching to a different feature with SVN are pretty limited.

This is interesting. What I'm curious about though, is how does this workflow scale to thirty developers? 100?

I tend to believe with six people or less, you can really work together with any system and it will work fine. Some will obviously require more work than others, but once you get to a larger team, some systems just won't work, AFAIK.

We also follow feature development workflow with git:

http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-te...