Team Development with Visual Studio Team Foundation Server

• Regressions. This report shows a list of all the tests that previously passed but are
now failing.
• Reactivations. How many work items are being reactivated? This report shows work
items that have been resolved or closed prematurely.
• Related Work Items. What work items are dependent on other work items? This
report shows a list of work items that are linked to other work items so you can trace
dependencies.
• Remaining Work. How much work is left to be done and when will it be
completed? This report shows the amount of work that is remaining, resolved and
closed over time. Projecting remaining work trends forward can enable you to predict
the point at which you will be code complete.
• Unplanned Work. How much unplanned work is there? This report charts total work
versus remaining work and distinguishes planned from unplanned activities.
• Triage. What work items need to be triaged? This report shows every work item that
is still in the proposed state.
• Work Items. What are the active work items? This report lists every active work
item.
• Work Items by Owner. How much work is assigned to each member of the team?
This report shows work items per team member.
• Work Items by State. How many active, resolved and closed work items are there?
This report shows lists every active, resolved, and closed work item.
Groups and Permissions
The following groups are available by default in the MSF Agile process template:
• Readers. Members of this group have read-only access to the team project.
• Contributors. Members of this group can add, modify, and delete items within the
team project.
• Build Services. Members of this group have build service permissions for the team
project. This group is used for service accounts only.
• Project Administrators. Members of this group can perform all operations in the
team project.
Source Control
MSF Agile uses the following default source control settings:
• Multiple Checkout. By default MSF Agile allows multiple checkouts to enable
multiple team members to work on the same file at the same time. Any resulting
conflicts must be resolved at check-in time.
• Permissions. The default permissions on the source control are as follows:
o Project Administrators. Have all available rights.
o Build Services. Have rights to read, pend changes, check-in, label, start build,
and edit build.
o Contributors. Have rights to read, pend changes, check-in, check-out, label,
and start build.