Anti-Patterns of a Private Workspace


solution to a problem that may appear like a good idea, but lacks the necessary input to make it effective and workable.

An anti-pattern will appear when a solution is decided and deployed, but the context and forces are not factored in and consequences of the solution are not considered. The context and forces are critical input prior to defining a good solution (aka, pattern). By context, this refers to the setting or experience level of the organization in which the problem lives and in which the solution must work. By forces, this refers to various influences in play (political, procedural, social, resistance, maturity, etc.) that can affect a solution and therefore the solution’s ability to be adopted. Note: this section adapted from a section in the article “Anti-Patterns of Change Control” by Mario Moreira (October 2004).

How Anti-Patterns Impact Private Workspaces
As mentioned previously, the ability to work in isolation makes a private workspaces very beneficial to programmers. It is important, however, that the private workspace is used in the context of the project and the forces influencing the project and programmer are understood. While private workspaces can be advantageous, it is important for those who own the development process to discuss the usage of the private workspaces in relation to the expected change rate, release schedule, and other factors. Otherwise, programmers can use the private workspaces leading to poor results.


Below are three examples of poor results (aka, anti-patterns) in relation to private workspaces, though more can certainly be identified.  

About the author

Mario  Moreira's picture Mario Moreira

Mario Moreira is a Columnist for the CM Journal, a writer for the Agile Journal, an Author, an Agile and CM expert for CA, and has worked in the CM field since 1986 and in the Agile field since 1998. He has experience with numerous CM technologies and processes and has implemented CM on over 150 applications/products, which include establishing global SCM infrastructures. He is a certified ScrumMaster in the Agile arena having implemented Scrum and XP practices. He holds an MA in Mass Communication with an emphasis on communication technologies. Mario also brings years of Project Management, Software Quality Assurance, Requirement Management, facilitation, and team building skills and experience. Mario is the author of a new book entitled “Adapting Configuration Management for Agile Teams” (via Wiley Publishing). It provides an Agile Primer and a CM Primer, and how to adapt CM practices for Agile Teams. Mario is also the author of the CM book entitled, “Software Configuration Management Implementation Roadmap.” It includes step-by-step guidance for implementing SCM at the organization, application, and project level with numerous examples. Also consider visiting Mario’s blog on CM for Agile and Agile adoption at

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!