http://blogs.msdn.com/b/robcaron/archive/2004/08/06/210298.aspxAfter being somewhat static since it came on the scene a few months ago, we're starting to hammer the Team System Developer Center into shape. In this iteration, we've cleared out some of the static content and added some areas that will be more dynamicen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/robcaron/archive/2004/08/06/210298.aspx#210763Sun, 08 Aug 2004 06:30:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:210763Saurabh NanduA1&amp;2) This whole concept of working with Team System is new. To get it implemented in an development center, it will require some material on how one benefits from the process, how does one go ahead and implement this process in an company etc. Get the managements thinking and buying on this system. <br>Since unless there is stuff that can be used to feed to the management, its not going to be an easy job to get them hooked to using thsi system. <br> <br>A3) If possible BOTH. The reason is that one would come to this site in 2 different frames of mind. <br>When I come to this site to learn, then I look for information related to my role, and how it will help me perform my job better. <br>But also when I have specific product issues I am facing, or want to learn more about a feature I have in the product, I'll always like things grouped by the product I am using. It will be almost impossible for me to figure out the information I seek, if its grouped by roles. <br> <br>About once a week would be a good starter. Gives me enough time to catch up with things slowly, rather than be bombarded and overwhelmed with stuff I can read.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=210763" width="1" height="1">