version control - TFS process guidance template lock-in? -


My team is trying to migrate many of our tools (SCM, bug-tracking, build, testing) to TFS . We are considering moving each system into phases. For example, take source control first, go to bug / feature tracking, etc ...

Because we have to choose a process template to use source control (or anything in TFS) How are we locked in with the decision? I'm looking to avoid making another project later (or is it not as bad as I think it will be?).

I know that in principle can customize everything, whose process configures the template after the fact (right?), But how is it possible in a practical way?

Here I see how I am doing:

  1. We migrate our source code. We select Microsoft's CMMI template.
  2. We create a new work item (or check-in note) which is a simple link to our legacy bug tracking system.
  3. We work for a while.
  4. We wait for that powers (we are a sophisticated software company) to work with a new TFS development workflow, a simple collection of new work items or a complete There may be a new template in the way that configures all types of goods.
  5. We try to transfer our new TFS project to our new system without losing our history.
  6. Is it unheard that till all these decisions have been finalized before using TFS, we just do not wait

    Therefore, you are right to think about the template of your process because there are certain "lock-in" "But it is not very serious. It seems that you have your process template with honey instead of super glue. Switch to get caught.

    Personally, I will start with MSF playful template. It's a very light weight and includes less working items - so you want to add more things to it (rather easy, very well supported in TFS) instead of removing them (more complex and completely satisfying) ).

    However, if a uber process definition process of power is decided to go down and comes out magically with a new process template in 12 months, then they want to use it If you think that you want to create a new team project, then unless it is on that server (or Project Collection in TFS 2010), then you either have your code added to the new team Project (Which means that the history is somewhat hidden in the current versions of the TFS client), or you can create a new team project with a blank folder for source control, and then the old folders are used for the old team project You can take it from new to new ones. It will completely preserve history because TFS maintains history for the trick on the same TFS example. Prior to this step, your working things will be eliminated in the old process template, and you will need to decide if you want to copy them or just leave them to stop naturally.

    Obviously, while actually using TFS for 12 months on actual projects, when you are getting the strength, you will be in a better position to know how you would like to have your shiny new process template - And I have often found that this is an exercise that never happens, and most people are tinkering around the edges of MSF or some more reminder Choose them.

    Hope that helps,

    Martin.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -