Just like to echo Tegan's sentiments on getting the last version...The first two version were could be incredibly hard to install! -I am convinced SQL Reporting services (used to be a dependency of TFS) hated me.
You can now easily install TFS now in about 5 minutes. If you run into any issues on the install drop me a line. My mobile is 425-495-4564. If there are areas you are interested in let me know and I will pull together a user group session on that topic. Chuck From: [email protected] [mailto:[email protected]] On Behalf Of Tegan Mulholland Sent: Wednesday, January 26, 2011 10:31 AM To: [email protected] Subject: Re: My company just decided to implement Team Foundation Server, should I be concerned? First off, if you are mandated to use TFS, I highly recommend making sure you're on the most recent version possible. The project management features especially have improved quite a bit between 2008 and 2010. We had a company-wide shift from Rally, svn, and CruiseControl.NET to a phase of anarchy to TFS for source control and task tracking due to an acquisition. The reason we lost Rally early on was that it's expensive, and at Microsoft we prefer never to buy software from another company when we can make a half-assed version ourselves (I am kidding. Kind of.). As source control, TFS has some cool features. Use the shelve sets! Also, make sure to get Team Foundation Power Tools. This is a command line tool set that will help you do things like "scorch" your local copy to make sure you have exactly what's on the server, or revert a particular revision. In my experience, the weakest aspect of TFS is how difficult it is to revert a checkin, which used to be something I took for granted. I've had no problem running builds locally that are also configured in TFS, but that depends on your own setup. Our TFS build doesn't do much other than build our .sln. I've seen other teams with a ~90 minute build time for their code base, though, and they aren't even running unit tests in the build. We don't run our tests in the TFS build, we still use CruiseControl.NET since it's something we can actually control. I agree with everyone else who says that a centralized tool like TFS task tracking can give the business a dangerous illusion of control. If you can't get devs to update Rally, they're never going to update TFS. Unlike Rally, TFS supports a deep hierarchy of "things" (deliverables, features, tasks), but even in 2010 the UI doesn't actually show those relationships very well. If you have any input into the way people higher up are looking at your task tracking tools, I'd do whatever I could to make sure that task tracking is understood AS A TOOL FOR DEV TEAMS to self-correct and not as a tool for management to punish or reward people or even track how well things are doing. If you can't trust your devs or dev manager to give a good status report, how can you trust them to enter honest information into a tool? - Tegan On Wed, Jan 26, 2011 at 8:11 AM, Brandon Molina <[email protected]<mailto:[email protected]>> wrote: In the past I actually championed an effort to get a different company to switch from VSS to TFS. This effort was ditched when I ran into so many troubles just trying to install TFS. At my current company I was very please with their tool set consisting of; Team City, SVN, HC Quality Center, Rally and a few other tools. I'm still looking for the main driver for the switch, my gut tells me its around reporting and tracking projects better (because some teams have issues getting their devs to input tasks in Rally [entirely different problem] ). Can anyone share good/bad stories about similar migrations or even experiences going from one company to the next. Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]<mailto:[email protected]>. To unsubscribe from this group, send email to [email protected]<mailto:altnetseattle%[email protected]>. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]<mailto:[email protected]>. To unsubscribe from this group, send email to [email protected]<mailto:[email protected]>. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
