Hello,
I'm part of a small development team (10 members including business analyst, team leader and infrastructure guy). We're considering moving to Team System. We currently have a very loose, informal development process. I've been trying to catch up on Agile and methodologies in general, but there is very much information and much of it requires prior knowledge of or experience developing by methodologies. What I really need is concise introductory material explaining what Agile re-organization or restructuring is required to maximize usage of VSTS. So, what one or two concise introductory VSTS+Agile migration resources do you most highly recommend

Top VSTS+Agile intro resources
JohnK1
Hi Michael,
The trick here is to recognise that you have several battles to fight:
First, you have little existing methodology or experience with one, so you need to get that in place first. You could look at an agile methodology to start with, and implement the concepts without a tool. That way you get the discipline in first.
Then look at the PM aspect, and where you guys touch on any project management processes. They need to be aligned, or created as well if needed. That will really take time.
Then look at the tool - if the guys arn't doing this without a tool, they may abandon the tool. VSTS is cool since it really sucks you in so you can't ignore it, else you can't work, but just realise that the tool alone won't instill the discipline the guys will need.
You have to have upper management support for this. Just doing it on your team is really a short lived solution, you need this to be mandated from above.
You need to create a context in which everyone expects the methodology to be followed, so it takes on a life of it's own, you can't have one person drivng it alone all the time.
You need to look at change management a bit, and make sure the guys understand that they can still be developers and do their jobs, this won't take that away, but will make things easier and clearer for them. Show them how the mess ups will be reduced if they embrace this.
I don't have any VCTS info but there are a couple of books out there, such as Professional Visual Studio 2005 Team System as found on Amazon. Our guys are using it.
For an agile methodology, the MSF process guidance, or even MSF3 white papers, are pretty good. You can also look at books like Rob Thomsett's Radical Project Management.
Good luck with it, it's a great journy and VSTS will get you through it.
Ryan Darby
SDM
HughFraserLarne
Does anyone else have any pointers, recommendations or experience to share Have any other teams transitioned from a haphazard process to a more structured, prescribed one
Ken Alexander
Hi Michael,
There are two ways to adopt a process. The first adoption method is the "grass roots" method where one practice is added at a time. This method tends to be more successful with teams that have worked together for a while with no apparent process (usually there is a process though). The second is the "all at once" approach that works with new teams.
Randy
MSF