Custom Software Apps & SharePoint Consulting

When it comes to good software consulting, Entrance spends a lot of time on maintaining good best practices so that we can produce awesome custom software for our clients. To that end, I’d like to cover a few things that I’ve learned recently about code branching and merging. It should be helpful not only to technical leads on projects, but to all developers on teams as they seek to work together efficiently and seamlessly. The terminology used in this article is defined at the bottom.

Pros and Cons of Branching

As we consider branching and merging of code, we should note that these solutions are context-dependent. As noted in the TFS Branching and Merging guide, “there is ‘no one size fits all’ branching strategy.” Thus, it is helpful before creating branches to consider the inevitable costs, such as:

  1. Increased complexity.
  2. Possible loss of work and introduction of bugs through failed merges.
  3. Increased maintenance costs as:
    -Someone needs to continuously Forward Integrate (FI) and Reverse Integrate (RI) change sets between the branches.
    -Permissions need to be set properly for each branch.
    -Merges between child branches become difficult.

For these reasons, one should carefully consider the possibility of a single code stream approach before creating branches within any given project. As noted in Professional Team Foundation Server 2012, “This should always be your default position. Do not branch unless you need to.” For small projects where there are only a few people working in any given area, a single code stream can reduce complexity and unintentional loss of work through merges.

Additionally, the use of shelve-sets can give developers a way to share/save changes without the creation of an additional branch. The ALM Rangers note in the below image (click to expand):

Of course, there are benefits to branching:

  1. Branching isolates code and creates stability within that branch. This is especially helpful for Release branches, as you can go back to the Release branch and make emergency fixes without being affected or affecting current development work.
  2. Branching allows multiple teams to develop in parallel. Although individual developers can use shelve-sets and local work-spaces to develop in parallel, if you plan to have multiple teams working on different work items in similar sections of code, giving each team a branch will speed the process and give that team more focus. This is helpful for major enhancements/feature adds.

Next week I will cover some of our standard approaches to branching. For more from Entrance’s software consultants, check out our series on SQL server tuning.


  1. Reverse Integration (RI) – Pushing a change-set from a child to a parent branch. This occurs in order to update the Main branch with changes from Dev or Release branches.
  2. Forward Integration (FI) – Pushing a change-set from a parent to a child branch. This occurs most often in Dev branches, which should be continually receiving changes from the Main branch.
  3. Baseless merge – A merge between two branches which do not have a parent/child relationship.
  4. Merge debt – A metric for understanding the amount of changes which have not been RI/FI between branches. The higher the amount, the more difficult it is to do the merge in the future. TFS has tools to calculate and report on this.


  1. More information about branching and merging best practices can be found in the Visual Studio Team Foundation Server Branching and Merging Guide.
  2. Professional Team Foundation Server 2012

Benjamin Smith
Consulting Manager @ Entrance
Ben has been helping clients solve their data and document problems for the past three years. He is a University of Houston Bauer MBA, and has led numerous successful SharePoint rollouts.
Carol Entrance Software Consulting making software better