Rob van der Meijden

After the PDC I’m starting with a new project. At this project we’re going to use all new tools Microsoft has available (VS 2005 TS, SQL 2005, Biztalk 2006 and maybe Indigo). For this reason my first day is going to be all about Team systems (dawn, Team system is without the S) this time not the into’s but a real case scenario. Session was given from 3 point of view, namely Project manager, Architect and Developer (occasionally the tester was mentioned J)

Team system gives the project manager finally the control he was searching last years. No longer: my work is finished for about 80% which was the same last week and the week before that, but accurate productivity numbers from the project. Using his own tools (Excel, Powerpoint) to manage work items and some very nice report: such as:

• Feature creep report a.k.a. planned and unplanned features. In a timeline you can when the unplanned features take overhead on you’re projects.
• Code churn, based on (MS) statistics it risks you’re work-items and predicting code failure (see this blog. As somebody in the audience mentioned, what does this mean if it’s based on MS statistics … :-)

The architect is namely drawing his diagrams for the logical data center and application diagram. Adding constraints to this diagrams which will be checked when you are creating the deployment diagram.

The developer only may implement the application diagram created by the architect. However when the developer changes the code by adding a new public method, the synchronization of code and diagrams adjusts the application diagram without the notice of the architect ... Ouch … I don't like that. 

Some must have links/reads:

Rob Caron’s blog

VSTS OPML file containing dozens of RSS feeds

VSTS System Definition Model (SDM) SDK