Executive Summary

Due to the growing and new strategic reorganization, the division is in need of dedicated resource to server its SCM needs for multiple technology delivery teams. Previously, various features of different TFS version were being used between different teams. Some for source code only, some use bug tracking, and some use MS Build directly. Most processes are manual and inconsistent even between teams using the same technology.

The goals are

  • Fully utilize the TFS 2010 features
  • Streamline the Build and deploy processes
  • Dedicated resource around SCM needs

Some symptoms were observered during the initilal encounter

  • Naming convention for branches and environments are ambiguous and inconsistant
  • Branching strategies are inconsistant between teams
  • Manual build and deploy processes
  • No dedicated build environment
  • No standard work item templates
  • No integration between TFS and other technologies
  • In need of MTM to run and track tests for both manual and automatic tests
  • In need of custom work item definition
  • In need of custom reports

Steps taken to build a better SCM practice

  • Setup a TFS 2010 system
  • Migrated code and projects to the new system
  • Standardized the template (Scrum 1.0)
  • Setup a build server for teams
  • Setup build definitions to standardize the build and deploy processes
  • Customized work item definitions to fit different needs
  • Generated reports for various teams
  • Created new work item types for non-technical teams to track works in TFS
  • Implemented Hyper-V based Lab management
  • Setup MTM to for QA teams
  • Setup integrators between TFS and Rally
  • Setup integrators between TFS and Pivtal Tracker
  • Setup Urban Turtle for visualize Scrum planning