This document provides an overview of using Azure DevOps for software development. It introduces Azure DevOps and its features for planning, collaboration, source code control, bug tracking. It then provides steps for getting started including creating a new project, configuring source code control and work item tracking. It demonstrates using Agile/Scrum features like product backlog, sprints and taskboards for tracking work. Finally, it covers how to use source code control in Azure DevOps with Visual Studio and how to report and track bugs.
This document provides an overview of using Azure DevOps for software development. It introduces Azure DevOps and its features for planning, collaboration, source code control, bug tracking. It then provides steps for getting started including creating a new project, configuring source code control and work item tracking. It demonstrates using Agile/Scrum features like product backlog, sprints and taskboards for tracking work. Finally, it covers how to use source code control in Azure DevOps with Visual Studio and how to report and track bugs.
This document provides an overview of using Azure DevOps for software development. It introduces Azure DevOps and its features for planning, collaboration, source code control, bug tracking. It then provides steps for getting started including creating a new project, configuring source code control and work item tracking. It demonstrates using Agile/Scrum features like product backlog, sprints and taskboards for tracking work. Finally, it covers how to use source code control in Azure DevOps with Visual Studio and how to report and track bugs.
This document provides an overview of using Azure DevOps for software development. It introduces Azure DevOps and its features for planning, collaboration, source code control, bug tracking. It then provides steps for getting started including creating a new project, configuring source code control and work item tracking. It demonstrates using Agile/Scrum features like product backlog, sprints and taskboards for tracking work. Finally, it covers how to use source code control in Azure DevOps with Visual Studio and how to report and track bugs.
Hans-Petter Halvorsen Contents • Introduction to Azure DevOps • Getting Started with Azure DevOps – Create and Configure a New Development Project • Using Agile/Scrum Features in Azure DevOps • Source Code Control (SCC) with Azure DevOps • Bug Tracking with Azure DevOps https://www.halvorsen.blog
Introduction to Azure DevOps Hans-Petter Halvorsen Table of Contents Azure DevOps • Tool for Software Engineering –Planning, Collaboration, Source Code Control, Bug Tracking, etc. • Developed by Microsoft • https://dev.azure.com • Free for 5 Developers + Stakeholders Features • Integrated with Visual Studio • Agile/Scrum Tools – Product Backlog – Sprint Backlog and Taskboard • Source Code Control (SCC) • Bug Reporting and Tracking • ++ (Not covered in this tutorial) https://www.halvorsen.blog
Getting Started with
Azure DevOps Hans-Petter Halvorsen Table of Contents Create New Project https://dev.azure.com
Enter a meaningful Name for your Project
Enter a meaningful Description for your Project
Note!!! Select “Advanced” Settings Version control = Team Foundation Version Control Work item process = Scrum Invite/Add Members Project Settings
Show/Hide Features • In Scrum we divide the work
into different Iterations • An Iteration is called a Sprint • A Sprint is typically 2-4 weeks long https://www.halvorsen.blog
Agile/Scrum Features in Azure DevOps Hans-Petter Halvorsen Table of Contents Product Backlog Product Backlog
• The Scrum Product Backlog is simply a list of all things that needs to be done within the project. • It replaces the traditional requirements specification. • So basically, The Product Backlog is a List of all the Requirements for a given Software System Work Items
3 important Work Item Types related to Product Backlog
• Product Backlog Item (PBI) • Feature – Can be used to group PBIs that belong together • Task – Divide a PBI into doable Tasks. Each PBI needs to be broken down into a set of Tasks. A Task is something that should be done by the developer Feature → PBI → Task • Feature X Features makes in easier to structure – Product Backlog Item A all the Product Backlog Items ü Task A.1 ü Task A.2 – Product Backlog Item B Each Product Backlog Item is broken ü Task B.1 down in one or more Tasks by the ü Task B.2 Developer • Feature Y – Product Backlog Item C ü Task C.1 ü Task C.2 etc. Example Sprints/Taskboard
Illustrative Example:
A Taskboard in Scrum has 3 columns
• To Do • In Progress • Done Within a Sprint you move the Tasks from left to right as the status changes Sprints/Taskboard https://www.halvorsen.blog
Source Code Control
with Azure DevOps Hans-Petter Halvorsen Table of Contents Repos (Repositories)
• You have limited features using the Web Browser, so you typically want to use Visual Studio to connect to the Repository • Then you can more easily create a proper Folder structure • Then you are ready to use Visual Studio to Check-in/Check-out your Code Visual Studio Open Team Explorer: Connect to your Azure DevOps Project: Map a Local Folder to your Project Source Control Explorer Solution Explorer – Check-in/Check-out https://www.halvorsen.blog
Bug Tracking with
Azure DevOps Hans-Petter Halvorsen Table of Contents Work Items Bug Reporting Queries
Queries are used to get a list of specific Work Items
Hans-Petter Halvorsen University of South-Eastern Norway www.usn.no
