Anti-Patterns of a Private Workspace


Anti-Pattern Name: Lazy Merge


·         Where do I merge my code with the latest code in the project integration stream (active development line)?


·         The programmer has made changes in the private workspace and is ready to move it to the project integration stream (aka, active development line).


·         The programmer has a list of new work changes they must start.

·         The release date is getting closer and the pressure is building to get the changes in.

·         The merge process is not well defined and understood.

(Poor) solution

·         Merge the changes to the project integration stream (aka, active development line).


·         When merging to the project integration stream, any changes to code in this baseline are not tested (or rebuilt) to validate that the changes still integrate well with the full baseline of code.

Better solution

·         Merge the changes (e.g., take the latest code) from the project integration stream (aka, active development line) into the programmer’s private workspace first. Then reconcile (e.g., rebuild, retest). This will ensure that the programmer’s latest changes do not break the latest baseline of code which everyone depend.

·         Establish clear guidance in the SCM checkout/check-in process including merge steps. Educate programmers on this process.  

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!