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

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Agile Retrospective

Image
  Guide to agile retrospectives for continuous improvement An agile retrospectives is an opportunity for agile development teams to reflect on past work together and identify ways to improve. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). During the agile retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better. Even if you are not on a development team, you can probably relate to the concept of retrospection. Have you ever worked hard on something only to realize later that you should have done it differently? It is not always a good feeling, but the solutions you uncover in hindsight can be valuable input for your next try. The same goes for your successes — acknowledging what went well and is worth repeating can be just as impactful. What is an agile retrospective? In short, an agile retrospective is a meeting...
Read more

Agile product management

Image
  What is agile product management? How do we define agile product management? It is a product development philosophy that emphasizes a flexible and human — rather than a rigid process- or tool-oriented — approach to defining product strategy and carrying out work. Teammates focus heavily on customer feedback to make improvements and adjust roadmaps throughout the product management process. This creates more responsive teams, leads to quicker iterations, and creates a more lovable experience overall. Benefits of agile product management Agile redefines how product managers think about planning and building products. Traditionally, new customer experiences were planned, designed, implemented, and tested in a step-by-step way. This meant that new functionality was delivered sequentially. Once requirements were defined and handed off to the development team, it was difficult to make any changes. The failure rate of large-scale and lengthy software development proj...
Read more