the problems team system solves have nothing to do with the size and the scope of the team. hell if you ask me, even 1 guy needs team system. microsoft has really screwed the pooch by trying to bill this thing as an enterprise tool. It's not an enterprise tool, it's a software development tool. period.

 

marketing dictates that this is an enterprise tool, not the reality of software development. i've secretly been pushing to try and deliver a hosted version of team system. it's currently being discussed inside of microsoft, but there are licensing issues. simply put if i want to host it, it has to run under the spla (service providers licensing agreement). currently, this isn't in the mix.

 

i'm going to rant for a second here. when i first suggested hosted team system to a microsoft person, i got a response along the lines of why? who would need that? this answer shocked me. team system helps solve a myriad of problems, facilitating communication amongst a team is simply one aspect of it. issues like bug tracking are issues that teams of 200 or lone codeslingers have. issues like code churn, requirements tracking, associating a requirement with a scenraio, with an implementation, with a bug, with a fix are all software development issues, not team issues.

 

i think everyone needs a team system. it's unfortuntate that microsoft doesn't... wake up redmond, teams of 1 have the same information and project management problems as teams of 1000. software development is no different with 1 or 1000. the issues are all the same. i'll conceed that communication becomes more difficult as the team size grows, but the fundamental problems of managing the information don't.

 

arglefargle....

 

 

Paul