Anti-Patterns of a Private Workspace


Anti-Pattern Name: Workspace Clutter


·         I need to prototype or test several scenarios of changes in my workspace.


·         No SCM Checkout/Check-in or Build process/procedure exists that addresses private files.

·         The private files come in handy.


·         For prototyping and testing, people can easily (and without anyone else knowing) create a private file or copy an existing of a source file within the workspace.

·         Sometimes people forget to clean up the private files.

(Poor) solution

·         Allow people to create private files and keep them in their private workspace as long as they want without any governance process of managing them.


·         When it’s time to submit the changes to the project integration stream (aka, active development line), only the checked out files are checked in and submitted, therefore missing the potentially needed private files. The needed private files cause the project integration stream build to break. The corrective action may be difficult to identify, as the changes work in the programmer’s private workspace.

Better solution

·         Establish a step in the SCM checkout/check-in or build process/procedure to remove or cleanup the private files prior to file builds and unit tests with a private workspace. Educate programmers on these processes.

·         Establish a consequence (e.g., reprimand from product manager) for the programmers who do not cleanup appropriately and cause build and regression problems.  

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!