Microsoft team foundation project lead (1)

Microsoft team foundation project lead (1)

 

The team foundation project leader has some responsibilities and permissions that common project members and administrators do not have to deal with team projects.
1. create and manage team projects
As a team project manager, the project manager is responsible for creating team projects and ensuring that the team meets the originally set goals.
To achieve the predefined goals, we recommend that you start with the following aspects of the project.
(1) Planning Team Project
Before creating a team project, the project leader should carefully plan the scope of the project and consider future modification, growth, and maintenance approaches for the Team Project.
For this reason, Microsoft provides a list of issues to help the project lead determine whether to "Create a new team project" or "Expand existing projects ". The purpose of this list is to provide a project leader with a starting point for thinking about Project issues, rather than providing detailed or deterministic information for all software development projects.
Microsoft provides the following "Decision Tree" to help the project director decide whether to create a new team project for the project. If most of the answers to this "Decision Tree" are "yes", it indicates that a new team project should be created in the team Foundation server. (This figure is an overall flowchart of decision-making. Each substep will be decomposed in detail later)

 

(Figure 1)

The "team project-related Issues" substeps in u can be divided into the following subproblems:

 

(Subgraph 1)

The meanings of each subproblem in this figure are explained in detail on Microsoft's official website. From
Http://msdn.microsoft.com/zh-cn/library/ms242894.aspx#CurrentTeamProject

.
The "TFs-related questions" substeps in U (General Figure 1) can be divided into the following subproblems:

 

(Subgraph 2)

The meanings of each subproblem in this figure are explained in detail on Microsoft's official website. From
Http://msdn.microsoft.com/zh-cn/library/ms242894.aspx#CurrentTeamProject

.

The "structure-related problems" substeps in U (General Figure 1) can be divided into the following subproblems:

 

(Subgraph 3)

The meanings of each subproblem in this figure are explained in detail on Microsoft's official website. From
Http://msdn.microsoft.com/zh-cn/library/ms242894.aspx#CurrentTeamProject

.
 

In U (General Figure 1), the process-related substeps can be divided into the following subproblems:

 

(Subgraph 4)

The meanings of each subproblem in this figure are explained in detail on Microsoft's official website. From
Http://msdn.microsoft.com/zh-cn/library/ms242894.aspx#CurrentTeamProject

.
It should be noted that the above question is not a summary of all aspects of the plan content of all projects, but only a starting point for thinking. However, this does not affect the value of the preceding "Decision Tree". This "Decision Tree" provides a good guiding role in using the team Foundation server to plan the team's projects.
(2) create a team project
Because most of the work done by the team is carried out in the boundaries and design of the "Team Project", creating a "Team Project" is a key aspect of using the team Foundation server.
The procedure for creating a new team project using the new Team Project Wizard is simple, but you must carefully plan the "Team Project" to ensure it has the required capacity, flexibility, and long-term.
(3) share team project resources
In team Foundation server, you cannot directly share the settings, objects, and process templates of team projects across "team projects. Process templates, version control settings, check-in policies, generation types, and work item definitions are isolated between different team projects, therefore, they cannot be shared across different teams.
U sharing Process Template
To share the same process template among team projects, you can store the Process Template in team Foundation server and use it each time you create a new team project.
U sharing process Guide
To share the same procedure guide between team projects, you can store the procedure guide document in a public location outside each team project.
U shared team "project items"
There are two ways to share the "project item" content (such as source code) in the "Source code management Tree:
(1) copy the "Source code management Tree" branch to create the same directory structure and content in the target Team Project.
(2) manually copy the "project item" from the source Team Project to the target Team Project.
To share work items, documents, reports, versions, tests, or source code that are not stored in the source code management tree, you can copy these items from the source Team Project to the target Team Project ". In this way, although there is no dynamic relationship between the source information and the target information (that is, changing one of them will not change the other at the same time ), however, the information contained in items in a team project can be used in other team projects.
(4) Split team projects
When you use team Foundation server to manage multiple team projects, you may encounter the need to split a "Team Project" into two (or more) independent team projects.
There are two ways to split a team project:
U continues to use the original team project and creates a new branch for the second new team project.
U creates two (or more) New team projects instead of the original team project.
The specific steps for "splitting a project" involve only the specific operations of the team Foundation server:
Http://msdn.microsoft.com/zh-cn/library/ms242901.aspx

Find.
(5) merge two team projects
When you use team Foundation server to manage multiple team projects, you may encounter the need to merge two (or more) team projects into a single team project.
There are two ways to merge two team projects:
U combines one team project into another team project
U combines two (or more) team projects into the third new Team Project
The specific steps to "merge two team projects" involve only the specific operations of the team Foundation server:
Http://msdn.microsoft.com/zh-cn/library/ms242893.aspx

Find.
(6) custom team projects
When creating a new team project, the Team Project Settings, tools, and content are determined by the Process Template selected in the new Team Project Wizard.
When using a "Team Project", you may find that the initial settings cannot meet the actual needs of the project. Therefore, you need to customize the Team Project. For example, if you use the MSF for Agile Software Development Process Template when creating a team project, you may find that some groups created by this template are too general and need to be further refined, therefore, you can customize the group ".
You can customize the following content in team Foundation Server:
L groups and permissions: if the default group is inadequate or inappropriate, you can update these groups or create new groups. You can also add or remove individual users in a group, or grant or revoke group permissions.
L work item type and query: You can customize the work item type to suit your own workflow, or create your own public query or private query. We can make the following changes to the work item:
(1) Add a field
(2) rename a field
(3) allowed Value List of restricted Fields
(4) change status and supported State Conversion
(5) make the field a required field or a read-only Field
(6) make one field dependent on another field
(7) automatically fill in Field Values
(8) rearrange the display form of information in the form
(9) modify the Microsoft Project column mapped to a field
(10) generate the work item type
L source code management check-in instructions and policies: if the default check-in instructions are inadequate or inappropriate, you can add or remove the check-in instructions field or make some fields mandatory, other fields are optional. If the default check-in policy is inappropriate or inappropriate, you can add, update, or delete individual check-in policies.
L region and iteration: when a new team project is created using a process template, the team project does not contain the classification structure of the region or iteration. The team project structure can be updated by classifying the functions/components of the Team Project by region or iteration.
L Team Portal: if a team project uses a team portal, this portal is most likely a central point for communicating information to team members. You can change the appearance and behavior of the portal or its content.
L Process Guide: The Process Guide explains all roles, forms, reports, and workflows used in a team project. You can edit the Process Guide that is attached to the team Foundation server to customize the process that the Team should follow.
L Team report: you can create your own custom report by using the SQL Server 2005 report service designer or by extracting the report and manually editing its XML.
L generation type: Each team project can have its own generation type.

(7) use team resource manager to configure team projects
"Team Resource Manager" provides users with an orderly view of team projects.
"Team Resource Manager" only displays team projects in one team Foundation server at a time. When "team resource manager" is opened for the first time, it is empty. You must connect to the team Foundation server. Then you can select the team project to be displayed in "team resource manager.
"Team Resource Manager" is the main tool for managing team Foundation server. It can be used to manage the following resources:
U favorites
U team project
U Version Control
U work item
U documentation
U Report
U team Foundation build

The specific information involves the operation steps, from:
Http://msdn.microsoft.com/zh-cn/library/ms181472.aspx

Find.
(8) Cross-team project work as a project supervisor
As a team project manager or supervisor, you may need to manage multiple team projects at the same time. The team Foundation Server comes with multiple tools that can help project owners manage and execute work across "team projects.
You can work across teams in the following three aspects:
L tracking assigned work items: if the project supervisor is working on multiple team projects, it is easy for him to view all work items assigned to you across all team projects.
L organize your favorites: when the project leader is engaged in multiple team projects, he may want to create a central location, this allows you to find the most frequently used work item queries, documents, reports, and generation types.
L create a custom Report: if the project leader wants to know about code coverage, test results, and status across teams, you will want to create a specific custom report for the project supervisor.
The above three aspects involve specific operations. From:
Http://msdn.microsoft.com/zh-cn/library/ms242898.aspx

Find.
(9) Move the Team Project from one version to the next version
If the project owner is managing a team project that has completed a major iteration or milestone, or the Team Project changes too much and is not compatible with the existing workflow being promoted, the project supervisor can upgrade the team project from the current version to the next version to solve this problem.
The specific method is to create a new team project based on the existing team project. Moving a team project from one version to the next involves branch source code, copying items, and re-creating a combination of existing items in a new team project, which can be roughly divided into the following steps:
(1) create a new Team Project
(2) Move the work items in the old team project to the new team project
(3) set user permissions for new team projects
(4) copy documents from the old team project to the new team project
(5) Create regions and iterations for new team projects
(6) create a check-in Policy
(7) Create an alarm
(8) determine whether it is suitable for creating a backup

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/xuwedo2003/archive/2009/07/21/4365491.aspx