Today I will keep what we stopped last post which is the team Projects, The starting point for working with Visual Studio ALM is to create a team project to track information and to organize source code, builds, tests, and plans for your team. As the following illustration shows, you create a team project by choosing a process template, which defines the artifacts—work items, queries, documents, reports, and more—that support planning and tracking activities. Each team project corresponds to a default team. If you work within a large enterprise, you may want to define a team to support how your team works.
After you create a team project, you create your backlog and define tasks using work items. The types of work items you use will vary depending on the process template used to create your team project. You can learn more about each artifact for the default process templates that Visual Studio ALM provides through the following process guidance topics: Artifacts (Scrum), Artifacts (Agile), and Artifacts (CMMI). If you use a process template that is not listed, you might find associated guidance on another site.
I would like to mention here the work items & queries, project managers can update the status of work using work items. A work item is a database record that Team Foundation uses to track the assignment and progress of work. You can use different types of work items to track different types of work, such as user stories, customer requirements, product bugs, and development tasks. You use work item queries to list work items and to track the status or progress of an iteration or release. By specifying the filter criteria and query type, you can explore relationships among queried items, and modify them individually or in bulk.
- Add new or modify work items
- Attach files to work items
- Create links among work item
- Find or list a filtered set of work items
as clarified in the figure below: