Discussing anti-patterns is a useful way to evaluate possible solutions. By considering the context of the problem and the forces that are in existence, it provides a way to evaluate the potential solutions and identify which is best for the given situation.
With this in mind, it is important that the private workspace is established in relation to an overall development process. Assess the context of the project and the forces influencing the project and programmer. Design, document, and communicate the development process and the usage of the private workspaces in relation to the expected change rate, release schedule, and other factors. While the concept and working model of a private workspace can be very advantageous, I hope the anti-patterns discussed above will help you avoid common mistakes.
1. “Approaching Continuous Integration” by Mario E. Moreira, article on CM Crossroads, September, 2004
2. “Anti-patterns of Change Control” by Mario E. Moreira, article on CM Crossroads , April 2004
3. "Software Configuration Management Implementation Roadmap" by Mario E. Moreira, 2004, John Wiley & Sons, Ltd
4. Anti-patterns and Patterns in Software Configuration Management by William J. Brown, Hays W. “Skip” McCormick III, and Scott W. Thomas, 1999, John Wiley & Sons, Ltd
5. Software Configuration Management Patterns: Effective Teamwork, Practical Integration by Stephen P. Berczuk with Brad Appleton, 2003, Addison Wesley
6. The Anti-pattern section of theWiki Wiki Web - see http://c2.com/cgi/wiki?Processanti-patterns