In many, if not most, SDLC and ALM environments that we have encountered, there is usually very little planning in terms of the team environment and the technology used to support the SDLC and ALM environments. Consequently, decisions are typically based on spontaneous decisions or on a comfort zone, i.e. "we have done it this way for years, why change?"
The results are usually a non-functional SDLC and ALM environment, team frustration and counter productivity. This document is an attempt to simplify, consolidate and encourage the planning of the team structure and the version control environments.
There is a lot more to plan and consider, but we have decided to focus our initial investigation on the topics covered herein as a starting point to promote planning and getting started with a known and valuable SDLC and ALM foundation.
The scope of this document is primarily focused on steps 2 and 4 of the "Version Control" of the "0202 Microsoft Team System Planning" quick reference poster, covering team project, solution, source code, workspace and dependency planning starting with an introduction of options and concluding with the hypothetical company X proposal.