Anti-Patterns of a Private Workspace


What is a Private Workspace
A private workspace is an isolated place where software programmers can control the versions of code they are working on. A private workspace usually lives in the context of a code development process. The code development process includes an “active development line” which is a place where the latest baseline of code resides sometimes known as the “project integration” stream or branch. Connected to the project integration stream are the private workspaces. To illustrate this, please review the “Figure 1”. Private workspaces are individual streams of development where each developer can work on his/her own code changes independent of the latest and continually changing baseline of code in the project integration stream.


In order to determine the best development process in which a private workspace lives, one must first understand the nature of the development project and the development methodology, amongst other factors. For example, the rate at which a programmer should bring the latest code from the project integration stream to the programmer’s private workspace may be dependent on the development methodology (iterative vs. incremental vs. waterfall), the size of the team, and the release schedule. In addition, the frequency of the check-in is dependent on these factors. In other words, the development methodology should be understood, the release cycles should be known, the number of programmers of the team, and what they work on (requirements and defects) should be clear (amongst other factors). The rate of merging latest into the private workspace or the rate of check-in can be discussed and determined.


What is an Anti-pattern
When talking about what an anti-pattern is, we must also address what a pattern is. A very simple definition of a pattern is that it is a good solution with the implication that the solution actually works within the context and forces of the organization or group. An anti-pattern is defined as a poor solution. What is meant by that is that an anti-pattern is a

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!