One of the more fun but challenging aspects of my job is that I sit on the .Net PAC (Microsoft Partner Advisory Council)and this gives me an insight into new products, the workings and politics of the product teams and a chance to represent the partner community in feeding back to MS our views and feelings.
An example of this was when the .Net PAc were presented too by the Visual Studio/Team Services product team. Whilst we liked what we saw we were very concerned about the lack of support for the business analyst and the whole process of requirements gathering.
MS had already realised this but , my thought here, due to the purchase of Rational by IBM they had lost a key piece of their picture and were having to play catch-up! The party line was that we had all we need Team Services. We have covered off Architect, PM, Developer and Tester ~(note logistics gets its own toys) but you analysts must make do with Office.
So this takes me to RASK – Requirements Authoring Starter Kit just released by MS at : http://www.microsoft.com/downloads/details.aspx?familyid=e96ccc54-8759-452f-bf68-3a261c663b66&displaylang=en
My gut feeling is this is too late, too little and a bit half arsed. Decided to give it a whirl as I’ve just kicked off a project using TFS/Teams services and all.
I’ll report back with my findings, and those of others I come across….