Project : Azure DevOps

 Microsoft Azure DevOps currently has three types of processes:

  • Agile
  • Scrum
  • CMMI

But the problem with these processes is that they are very process or methodology-heavy. Suppose you are a new engineer, and you are working with Github and you want to use Azure DevOps, then you will need to deal with product backlog items, user storage, and all the technical mambo-jumbo. These make adopting Azure DevOps very complicated.

So to remove these complexities the Azure DevOps introduced the Basic process. With this users could just literally add project issues and start working on them immediately. Basic Process is the most lightweight. You should choose Basic when your team wants to develop or create the simplest model that uses Issues, Tasks, and Epics to track work.  


There are 3 work items in Azure Boards with the Basic process:

  1. Epic: Under epic, we can create multiple types of issues.
  2. Issue: Issue may be a bug, user story, or an improvement.
  3. Task: Task is the smallest unit of work, for each issue we can create multiple tasks.


In this article, we will look into the process of creating a project on Azure DevOps using Basic Process. To do so follow the below steps:


Step 1: Sign-in or Sign up to Azure DevOps  


  • Add your email address, phone number, or Skype ID to your Microsoft account.

  • If you don’t have Microsoft Account create one.


Step 2: Create Project with Basic Process in Azure DevOps

  • Click on the New Project button on the top right corner.

  • Enter information into the Panel that opens:
    • Enter the name of your project.
    • Project name can’t contain special characters such as / : \ ~ & % ; @ ‘ ” ? < > | # $ * } { , + = [ ], can’t begin with an underscore and must be 64 or fewer characters.
    • Enter the description this field is optional.
    • Choose the visibility of either public or private.
      • Public: With public visibility, anyone on the internet has the right to view your project.
      • Private: With private visibility, only people to whom you give access can view your project.
    • Choose the right version control for detail refer Git and TFVC version control – Azure Repos | Microsoft Docs.
    • Choose the Work Item Process.

Step 3: Click Create button. Navigated to Welcome page.

Step 4: You can choose the options display on the welcome screen to continue.

  • Invite: Using this option you can add others to your project. You can only invite users who are already part of your organization.

  •  Boards: Using this Option you can add work items.

  • Repos: Using this option we can clone or import a repository also initialize a README file for project summary page.

  • Pipelines: Using this option we can connect to any git provider and deploy continuously in any language and platform to the cloud.

  • Test Plans: Using this option we can perform testing solutions using the explanatory testing toolkit.

  • Artifacts: Using this option we can create, discover, host, install, and publish NuGet, npm, and Maven packages.

  • Manage your services: Using this option we can disable the visibility of services.

At this stage, you have successfully created a project on Azure DevOps using the Basic Process.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more