Team Development with Visual Studio Team Foundation Server

• Accurate progress reporting
Creating and Managing Projects with Team Foundation Server
The following steps summarize the general approach for creating team projects in Team
Foundation Server:
1. Choose a process template. You can either use a default template out of the box or
you can customize your own.
2. Create a team project. Your team project will be based on your process template.
3. Add appropriate groups and members to your team project.
4. Decide on your iteration cycle duration for the project. This includes creating
iterations in your team project.
5. Capture your scenarios as work items in TFS.
6. Determine which scenarios need to be completed for each iteration.
7. Define the quality of service (QoS) requirements. Link the quality of service
requirements to your scenarios.
8. Break your scenarios down into stories to provide manageable work items for
developers. Obtain estimates from the developers for each work item.
9. Create a project schedule. Create a project schedule (by using Microsoft Project)
and adds it to the Team Project.
10. Define acceptance criteria. Define acceptance criteria for the work items (correlated
to the QoS requirements).
11. Define reporting requirements. Define your project’s key performance indicators
and identify reporting requirements.
For more information on creating and managing a team project see, “How To: Manage
Projects in Visual Studio Team Foundation Server”
Strategies for Team Projects
You need at least one team project to start working with TFS. When a project manager
creates a new team project, an associated team project Web site is created containing
document libraries with document templates and stock reports. A work item database is
created for tracking all effort on the project, and a methodology template is installed that
determines rules, policies, security groups, and queries for all work efforts. Additionally,
a source code branch is created for source control.
The structure you choose for your team project should be guided by your requirements
and might change as your software development process evolves. There are three
common strategies for creating new team projects. You might use one of these strategies
or a combination of several. The three common strategies are:
• Team Project per application
• Team Project per release
• Team Project per team