I agree with point a), it is extremely helpful to have someone spending time to get you started. You cannot implement TFS on the side road, you have to have someone dedicated on that for a few weeks.

To point b) I must say it was much more easy to learn and to maintain than we initially thought. We don't need to hire someone for that, it's not as difficult as it might look at first.

So I would hire somebody for the implementation a some training, but not for running TFS.

>Assuming that a) someone has the time (and inclination) to learn how to do it properly; or, b) the company hires someone who's competent (hopefully) in running TFS.
>
>
>>TFS is more than version control. It will run your continuous integration, tracks bugs, work items, story points, etc. It's useful for team collaboration. If you aren't doing much team collaboration, then some of these other pieces aren't useful for you. However, even in small shops you can see big wins from bug tracking and continuous integration.
>>
>>
>>>I'm perfectly capable of checking in/checking out source code without having to have it integrated into my IDE. I really haven't found anything else that TFS is good for.