Aaron, A team project is designed to contain all artefacts related to a product or team's work. Therefore, in your case I would suggest one team project with areas inside that team project. >From http://blogs.vertigosoftware.com/teamsystem/archive/2006/10/04/3867.aspx
First off, Team Projects are team oriented, not individual oriented.
Think of them as a container for resources for all the roles within a project
(developer, tester, project manager, builder, change management, etc.). This
includes development methodology, process guidance, a team sharepoint portal, a
source control repository, a workitem repository, checkin policies, and
reports. So if you find yourself wishing you could create a Team Project
without all the extra "goo" (e.g. sharepoint portal, reports, etc.) that goes
along with them, you might not be thinking about them in quite the right way...
Another point is that a Team Project is not the same entity as a
solution or a source code project (e.g. a C# console application). A Team
Project can contain multiple solutions and source code projects as well as much
more (work items, reports, builds, etc.).
If your organization has only 1 application under development, the
answer is easy; create a Team Project for your app and stick with it until you
decide to follow a new development methodology. As you issue new releases, use
iterations to track your milestones.
If your organization has multiple applications in development, it might
be suitable to create 1 or many Team Projects depending on several factors.
* Do the products ship on the same schedule?
* Does each project follow the same development methodology?
* Can all the projects use the same work item types, check-in
policies, or check-in notes?
* Are the applications logically related?
* How many source control versions and work items do you estimate
the projects to contain?
Cheers
Chris
<http://blogs.vertigosoftware.com/teamsystem/archive/2006/10/04/3867.aspx>
________________________________
From: [EMAIL PROTECTED] on behalf of Aaron Bull
Sent: Thu 19/10/2006 4:53 PM
To: [email protected]
Subject: Setting Up TSF
This may be a simple question;
What defines a Team Project ?
If we have a big website application, which talks to a webservice which talks
to a windows service, would these be individual team projects or areas within
the one project ?
Similar to above, if we have 10 different and seperate windows services that
just do there own thing, would these all be seperate projects ?
Is there any documented best practises that discusses this sort of thing ?
Cheers,
Aaron
OzTFS.com - to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net
<<winmail.dat>>
