Visual Studio Team System (VSTS)
"Before you start some work, always ask yourself three questions - Why am I doing it, What the results might be and Will I be successful. Only when you think deeply and find satisfactory answers to these questions, go ahead.”
Chanakya (Indian Politician, strategist and Writer, 350 BC-275 BC)
Chanakya (Indian Politician, strategist and Writer, 350 BC-275 BC)
Well, this is precisely what I do before I take up any new work either official or pesonal. When I started with VSTS, I felt as if I had taken the less travelled road ("Road Not Taken" by RobertFrost) as we at Infosys had already got sophisticated tools and process in place for managing the SDLC of any type of Project.......
As I started studying the product deep, I saw a big value addition in terms of personalized tools provided for all the roles of SDLC and TFS tools/features. VSTS is very strong in the Engineering tools and ofcourse this being their first tool into the project management space, there is scope for improvement. I felt support for project management was not really very strong (through reporting is excellent) and started looking at how well this can integrate with other project management tools using the customization and extensibility options of VSTS.
It has been quite some time now since I started looking at this . Well in my future postings I will put some of the good stuff I saw in VSTS, limitations and the work arounds we came up with wrt this exercise ,... So do keep a watch on this blog site..Have a nice day...
PrashanthG
Comments
I have found some limitations in VSTS, while working with Team Edition for Testers. Web test is automatically getting aborted after 180 request. I would like to know whether i am assuming wrong or is this a limitation.
Posted by: Kaustubh | September 5, 2007 04:36 PM