Create a Project in Azure DevOps-Basic Process

Introduction

Azure DevOps is a comprehensive toolset that supports the full software development lifecycle (SDLC), offering services for project management, version control, CI/CD pipelines, testing, and more. However, traditional processes in Azure DevOps, like Agile, Scrum, or CMMI, can be overwhelming for new teams due to their complex methodologies. To address this, Azure DevOps introduced the Basic Process, a lightweight process ideal for teams that need a simpler framework to start managing their projects effectively.

In this article, we will explore how to create a project in Azure DevOps using the Basic Process. We’ll also cover its key features, advantages, disadvantages, best practices, and troubleshooting tips to optimize your project setup.

What is the Basic Process in Azure DevOps?

The Basic Process in Azure DevOps is designed to simplify project management. It eliminates the complexities of methodologies like Scrum and Agile, allowing teams to focus on their work without having to navigate product backlog items, user stories, or excessive technical jargon. The Basic Process uses a simplified model to track work through Issues, Tasks, and Epics.

Key Work Items in the Basic Process:

1. Epic: Represents large units of work, broken into multiple issues.
2. Issue: Represents a bug, user story, or improvement. Each issue can have multiple tasks.
3. Task: The smallest unit of work assigned to team members.

The Basic Process is ideal for teams starting with Azure DevOps or those who prefer a straightforward approach to project management.

Create a Project in Azure DevOps-Basic Process

Step 1: Sign In or Sign Up for Azure DevOps

1. Visit the Azure DevOps Portal.
2. Log in with your Microsoft account. If you don’t have one, click Create Account and complete the sign-up process.

Step 2: Create a New Project

1. Once logged in, click on the New Project button in the top-right corner.
2. In the panel that appears, fill in the following details:
   • Project Name: Enter a unique name. Ensure it does not contain special characters (e.g., / : \ ~ & % ; @).
   • Description: (Optional) Provide a brief summary of the project.
   • Visibility:
     • Public: Anyone on the internet can view your project.
     • Private: Only users with access can view the project.
   • Version Control: Choose between:
     • Git: Recommended for modern version control.
     • TFVC: A centralized version control system.
   • Work Item Process: Select Basic Process from the dropdown.
3. Click the Create button. You will be redirected to the project’s Welcome Page.

Step 3: Navigate the Welcome Page

After creating the project, the welcome page offers several options to set up and manage your project:

1. Invite Team Members:
   Add users who are part of your Azure DevOps organization to collaborate on the project.
2. Boards:
   Use this option to create and manage work items like Epics, Issues, and Tasks.
3. Repos:
   Initialize a Git repository, clone an existing repository, or import a repository to manage your source code.
4. Pipelines:
   Configure Continuous Integration (CI) and Continuous Deployment (CD) pipelines to automate build and deployment processes.
5. Test Plans:
   Set up manual or automated testing for your application using the exploratory testing toolkit.
6. Artifacts:
   Create, host, and share packages like NuGet, npm, or Maven for dependency management.
7. Manage Services:
   Customize the visibility and availability of services like Boards, Repos, and Pipelines.

Key Features of the Basic Process

1. Simplicity:
   The Basic Process removes complexities associated with Agile or Scrum processes, making it easier for new users.
2. Work Item Hierarchy:
   Tracks work using a straightforward structure: Epics → Issues → Tasks.
3. Quick Adoption:
   Teams can start working on issues immediately without requiring extensive setup or training.
4. Integration with Azure DevOps Services:
   The Basic Process seamlessly integrates with other Azure DevOps tools like Boards, Pipelines, and Repos.
5. Customization:
   Allows you to customize work item fields and workflows to suit your team’s requirements.

Advantages of the Basic Process

1. Ease of Use:
   Ideal for teams new to Azure DevOps or project management tools.
2. Flexibility:
   Supports a variety of project types without enforcing rigid methodologies.
3. Rapid Onboarding:
   Simplified structure reduces the learning curve for team members.
4. Seamless Collaboration:
   Tools like Boards and Repos facilitate team collaboration and task tracking.
5. Scalability:
   Suitable for small to medium-sized projects, with the option to switch to Agile or Scrum as the project grows.

Disadvantages of the Basic Process

1. Limited Advanced Features:
   The Basic Process lacks some advanced workflow and reporting features available in Agile or Scrum processes.
2. Not Ideal for Complex Projects:
   For large projects requiring detailed sprints, story points, or backlog prioritization, Agile or Scrum may be better suited.
3. Minimal Customization:
   Compared to other processes, customization options are more limited.

Best Practices for Using the Basic Process

1. Define Work Items Clearly:
   Clearly differentiate between Epics, Issues, and Tasks to maintain organized workflows.
2. Use Boards Effectively:
   Create customized Kanban boards to visualize and track progress.
3. Automate Pipelines Early:
   Set up CI/CD pipelines from the beginning to streamline deployment processes.
4. Invite Team Members Proactively:
   Ensure all relevant stakeholders are part of the project for seamless collaboration.
5. Monitor Progress:
   Regularly review work items and update their status to reflect accurate progress.

Troubleshooting Steps

If you encounter issues while creating or managing a project in Azure DevOps, try the following:

1. Error While Creating Project:
   • Ensure the project name adheres to character and length restrictions.
   • Verify that your organization has sufficient permissions to create projects.
2. Cannot Add Team Members:
   • Check that the users are part of your Azure DevOps organization.
   • Ensure you have administrative permissions.
3. Pipelines Not Triggering:
   • Verify pipeline configurations and repository connections.
   • Ensure your pipeline YAML file is correctly formatted.
4. Issues Not Appearing in Boards:
   • Confirm that work items are assigned to the correct Iteration or Area.
   • Refresh the board or check filters applied.
5. Repositories Not Accessible:
   • Verify repository permissions for team members.
   • Check for any connectivity issues between your Git client and Azure Repos.

Conclusion

The Basic Process in Azure DevOps is an excellent starting point for teams looking for a lightweight, easy-to-use project management solution. With its simplified work item hierarchy and seamless integration with Azure DevOps services, teams can quickly set up projects and start collaborating. While it may not offer the advanced features of Agile or Scrum, its flexibility and simplicity make it a great choice for small to medium-sized projects.

Whether you’re managing a personal project or onboarding a new team, the Basic Process ensures a hassle-free experience. To learn more about Azure DevOps, visit the official Azure DevOps documentation.