Microsoft Azure DevOps – Projects

Hi All,

LIFE IS BEAUTIFUL 🙂   I hope we all are safe 🙂  STAY SAFE, STAY HEALTHY  STAY HOME 🙂

Background: We have started discussing Azure DevOps. In last three articles of Azure DevOps we discussed

• Introductory part of Azure DevOps
• Organizations in Azure DevOps
• Microsoft Azure DevOps – Deleting and Recovering Organization

In this article we will move ahead and will discuss Microsoft Azure DevOps Projects.

Take away from this article: At the end of this article we will got to know about

• What are Microsoft Azure DevOps projects
• Types of Azure DevOps projects
• Permissions require to create DevOps project
• How to create DevOps projects
• Clients / Tools that support connection to a project

Prerequisites :

• We need Azure DevOps organization for creating Azure DevOps project
• User must be a member of the Project Collection Administrators group or have the Create new projects permission set to Allow.

What are Microsoft Azure DevOps projects :

• A project is container for our source code or code repository
• Project is a place for team to manage, track progress of our application, to collaborate
• Every Azure DevOps organization have at least minimum one project
• We can have one more multiple projects in Azure DevOps organization
• When we create an organization, there is we get option to create project as

• By default “Private project” is selected as shown in above fig

Types of Azure DevOps projects :

• There are two types of Projects we can create
  • Public Project –
    • Public project doesn’t require user sign in to access Azure DevOps services
    • Without user sign in, user gets read only access to the Azure DevOps services
  • Private Project –
    • For private projects we need to add users and give access to the project
    • User need to sign in to the Azure DevOps to access the project and respective services
• In next upcoming article we will discuss in more depth about types of projects and scenarios 🙂

Permissions require to create DevOps project : User must be a member of the Project Collection Administrators group or have the Create new projects permission set to Allow.

How to create DevOps projects :

• To create new project go on Azure DevOps home page – https://dev.azure.com/<organization name>, here we have https://dev.azure.com/prashamsabadra
• From Azure DevOps home we have an option at right top corner – blue button – “+ New project” as shown in below Fig

• Under “Projects” tab we get an existing created projects
• Once we click on “+ New project“, “Create new project” dialog opens as shown in below fig

• Please fill the respective values and click on “Create” button at the right bottom corner of “Create new project” dialog as shown in above fig
• Once we clicked on “Create” button, progress bar comes as shown in below fig

• Once our new Azure DevOps project created successfully, we will redirected to the summary page – https://dev.azure.com/<organization name>/<project name>, here we have https://dev.azure.com/prashamsabadra/Knowledge%20Junction%20Intranet of new project (project name – Knowledge Junction Intranet) as shown in below fig

• On new Azure DevOps summary / overview page we have project details and options like
  • Project name – Here, Knowledge Junction Intranet
  • Project statistics
  • Project members
  • We could invite the users for the accessing services
  • Azure DevOps services as in left column –
    • Boards
    • Repos
    • Pipelines
    • Test Plans
    • Artifacts

Clients / Tools that support connection to a project :

• Visual Studio (Professional, Enterprise, Test Professional)
• Visual Studio Code
• Visual Studio Community
• Eclipse: Team Explorer Everywhere
• Office Excel
• Azure Test Plans (formerly Test Manager)
• Microsoft Feedback Client

Recommendation for number of projects in Azure DevOps organization :

• It is recommended that single project should be created for an organization
• Single project reduces maintenance tasks
• Single project supports most optimized / full-flexibility cross-link object experience. (cross-link object => Linking of work items, linking of work items to test cases, linking of tasks / bugs while committing the code etc. )

We will stop here. In next upcoming article we will discuss more about Organizations and Project settings.

We have very good series going on Azure DevOps. Please have a look once – https://knowledge-junction.in/?s=Azure+DevOps

References :

• About projects and scaling your organization
• Create a project in Azure DevOps

Thanks for reading 🙂 Feel free to discuss / comment / questions. SHARING IS CARING 🙂 

Share In Teams:

Enjoy the beautiful life 🙂  Have a FUN 🙂 HAVE A SAFE LIFE 🙂 TAKE CARE 🙂