Manage your project

Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

With most Azure DevOps services, you can start using the service and configure resources as you go. No up-front work is required. Most settings define defaults.

That said, as an organization owner or a project administrator, there are a few tasks you might want to do once your created your project to ensure a smooth operational experience. If you own a large organization, you'll want to consider additional tasks to structure your projects to support multiple teams or software development apps.

Add users to your project

The first task is to ensure that all members of your organization or group are added to your organization and projects. For small groups, using Microsoft Accounts to add users to your organization and projects works fine.

Larger enterprises may want to consider using Azure Active Directory to manage permissions and user access. To learn more, see the following articles:

The first task is to ensure that all members of your organization or group are added to your organization and project. Larger organizations may want to consider using Azure Active Directory to keep the maintenance of managing permissions and user access. Typically, you should install Azure Active Directory prior to installing TFS. To learn more, see these articles:

You can delegate the task to add users to an organization by adding a user with Stakeholder or higher access to the Project Collection Administrators group.

Grant or restrict permissions

Access to features and functions is controlled by access-level assignments, permissions, and security groups. To quickly understand the defaults configured for your project, see Default permissions and access.

If you decide that you want to delegate specific tasks to others, then you'll want to add them to a built-in or custom security group or add them to a specific role. To learn more, see these articles:

To learn more about permissions and security, review the following articles:

Share your project vision and support collaboration

Each project has a summary page where you can share information through README files or by pointing to a project Wiki. To orient users who are new to your project and share established processes and procedures, we recommend that you set up your project summary page or provision a Wiki.

Each project has a summary page where you can share information through README files. To orient users who are new to your project and share established processes and procedures, we recommend that you set up your project summary page.

Remove unused services from the user interface

To simplify the web portal user interface, you can disable select services. For example, if you use a project only to log bugs, then you can remove all services except for Boards.

This example shows that Test Plans has been disabled:

Disable a service

Set code, test, and other policies

There are several policies you can set to support collaboration across your teams, secure your projects, and automatically remove files that are no longer needed. To set policies, review the following articles:

Define area and iteration paths for work tracking

If you support several products or feature areas, you can assign work items by feature area by setting up area paths. To assign work items to specific time intervals, also known as sprints, you'll want to configure iteration paths. To use the Scrum tools—sprint backlogs, taskboards, and team capacity—you need to configure several sprints. For an overview, see About areas and iteration paths.

Iterations Areas
Default iterations, Scrum process A set of sample area paths

Customize work-tracking processes

You and your teams can start using all work-tracking tools immediately after you create a project. But often, one or more users want to customize the experience to meet one or more business needs. Although you can customize the process easily through the user interface, you can establish a methodology for who manages the updates and evaluates requests.

Note

By default, users granted Stakeholder and higher access are granted permission to create, edit, and manage processes used to customize the work-tracking experience. If you want to lock down who can perform these tasks, set permissions at the organization level to Deny.

To learn more, see the following articles:

Customize work-tracking processes

You and your teams can start using all work-tracking tools immediately after you create a project. But often, one or more users want to customize the experience to meet one or more business needs. You can establish a methodology for who manages the updates and evaluates requests.

To learn more, see On-premises XML process model.

Review and update notifications

A number of notifications are predefined for each project you add. Notifications are based on subscription rules. Subscriptions arise from the following areas:

If users believe they're getting too many notifications, they can opt out of a subscription.

Personal notifications

Configure an SMTP server

In order for team members to receive notifications, you must configure an SMTP server.

Add teams to scale your organization

We recommend that you add teams as your organization grows. Each team gets access to their own set of Agile tools that they can customize.

Agile tools and team assets

To learn more, see the following articles:

Install and manage extensions

An extension is an installable unit that adds new capabilities to your projects. You can find extensions in Azure DevOps to support the following functions:

  • Planning and tracking of work items, sprints, scrums, etc.
  • Build and release flows.
  • Code testing and tracking.
  • Collaboration among team members.

For example, to support code search, install the Code Search extension.

You want to tell your users about extensions and that they can request an extension. To install and manage extensions, you must be an organization owner, a member of the Project Collection Administrators group, or added to the Manager role for extensions.

Set up billing

All organizations can add up to five users with Basic access and unlimited users with Stakeholder access. If you need to add more users or pay for additional services or extensions, set up billing.

Next steps