Anti-Patterns of a Private Workspace


Anti-Pattern Name: Isolationist


·         How often should I populate my private workspace with the latest changes?


·         Project development methodology (waterfall, incremental, iterative) is not identified or understood.

·         No direction or guidance provided on the rate of change to a workspace.

·         Do not really understand the meaning and full implications of continuous integration.


·         Some programmers like to work in isolation. No one bothers them and they do not bother others.

·         Programmers get more work done with they do not have to deal with changes occurring underneath.

·         Because private workspaces come with a separate branch or stream and versioning, a programmer can ensure their code is backed up. However, this can give the perception that they can keep their changes private longer.

·         Changes to the latest baseline often force them to do a lot of rework.

(Poor) solution

·         Infrequently update the private workspace with latest code baseline.


·         When it is time to deliver changes, a potentially large merging and reconciliation (changes, building, unit testing) task may be needed which could take a while, possibly affecting the release schedule. In addition, other programmers have not seen the changes and this can impact past project changes causing regression and breakage in the code.

Better solution

·         Ask for a clear understanding of the project development methodology (waterfall, incremental, iterative) and a general expectation of the frequency of updating the private workspace with the latest baseline.

·         Update the private workspace after reaching a milestone of change (fixed the defect, completed one change request, etc.) that aligns with the change frequency expected and the development methodology used.  

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!