https://www.halvorsen.

blog

Azure DevOps

Hans-Petter Halvorsen
 Azure DevOps
• In the simplest terms, Azure DevOps is the
evolution of VSTS (Visual Studio Team Services).
• It is the result of years of using their own tools
and developing a process for building and
delivering products in an efficient and effective
way.
• Web Site: https://dev.azure.com
https://www.halvorsen.blog

What is “DevOps”?

Hans-Petter Halvorsen
 What is “DevOps”?
• DevOps is a Software Development Methodology
that combines Software Development (Dev) with
Operations /Production (Ops)
• The goal of DevOps is to shorten the systems
development life cycle while delivering features,
fixes, and updates frequently in close alignment
with daily Operations
 What is “DevOps”?
A defining of DevOps is:
• “DevOps is a set of practices intended to
reduce the time between committing a
change to a system and the change being
placed into normal production, while ensuring
high quality”
What is “DevOps”?

https://en.wikipedia.org/wiki/DevOps
 What is “DevOps”?
DevOps typically includes the following Key Topics and Tools:
• Coding – code development and review, source code management tools,
code merging
• Building – continuous integration tools, build status
• Testing – continuous testing tools that provide feedback on business risks
• Packaging – artifact repository, application pre-deployment staging
• Releasing – change management, release approvals, release automation
• Configuring – infrastructure configuration and management, infrastructure
as code tools
• Monitoring – applications performance monitoring, end-user experience
“DevOps” and Agile Software Development
• The need for DevOps arose from the
increasing success of Agile Software
Development
• Organizations wanted to release their
Software faster and more frequently
 Goals with “DevOps”
• Improved deployment frequency
• Faster time to market
• Lower failure rate of new releases
• Shortened lead time between fixes
• Faster mean time to recovery (in the event of a new
release crashing or otherwise disabling the current
system)
https://www.halvorsen.blog

Start using
Azure DevOps
Hans-Petter Halvorsen
 Start using Azure DevOps

• Go to the Azure DevOps Web Site and register

for the Service.

• Web Site: https://dev.azure.com

https://www.halvorsen.blog

Create New Project

Hans-Petter Halvorsen
New Project

Make sure to select

these settings
 Scrum
• Scrum is a Framework for creating
Software
• https://www.scrum.org

Introduction to Scrum: https://youtu.be/gy1c4_YixCo

 Scrum

Taskboard
My Project
Invite Members
Project Settings

These you can turn

off (will not be used
in this Project)
Configure Iterations/Sprints
Configure Areas
Configure Backlog
https://www.halvorsen.blog

Work Items

Hans-Petter Halvorsen
Work Items
 Work Items
Most used Work Item Types:
• Product Backlog Item (PBI)
– List of all things that needs to be done within the project, i.e., list of
requirements
• Task
– Each PBI needs to be broken down into a set of Tasks
– A Task is something that should be done by the developer
• Bug
– Used to report Bugs in your Software
• Feature
– Typically a stakeholder that wants a new feature in the Software that is
not included in the original Requirements
https://www.halvorsen.blog

Product Backlog

Hans-Petter Halvorsen
 Product Backlog
• In the simplest definition 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 artifacts.
• These items can have a technical nature or can
be user-centric e.g. in the form of user stories.
 Product Backlog
• The Product Backlog is an
ordered list of everything that
is known to be needed in the
product.
• It is the single source of
requirements for any changes
to be made to the product.
 Product Backlog
• A Product Backlog is never complete.
• The earliest development of it lays out the initially
known and best-understood requirements.
• The Product Backlog evolves as the product and the
environment in which it will be used evolves.
• The Product Backlog is dynamic; it constantly
changes to identify what the product needs to be
appropriate, competitive, and useful.
• If a product exists, its Product Backlog also exists.
Product Backlog
Create Product Backlog Items
https://www.halvorsen.blog

Tasks

Hans-Petter Halvorsen
 Tasks
• Each PBI needs to be broken
down into a set of Tasks
• A Task is something that should
be done by the developer
Tasks
Product Backlog Items and Tasks
https://www.halvorsen.blog

Task Board

Hans-Petter Halvorsen
 Azure Boards
• Plan, Track, and Discuss your work
within your Team
• Scrum/Kanban Board (Task Board)
 Sprints/Iteration
• In Scrum we divide the work into different
Iterations
• An Iteration is called a Sprint
• When a new Sprint starts we need to
select/create a set of Tasks for that iteration
into the Taskboard
 Scrum Board (Taskboard)
• A physical board to visualize information for
and by the Scrum Team, often used to manage
Sprint Backlog.
• Scrum boards are an optional implementation
within Scrum to make information visible.
 Scrum Board (Taskboard)
To Do In Progress Done
Dropbox Web Create Database GUI
Support
Nils 4h
Service
Hans 4h Login8h Nils
Design4h Design
Trond 6h
Nils

3 Layer Add DB SQL

DB API
Support
Nils 4h Hanne 6h Nils Comm.4h Script6h
Vera

Java Gantt
Create
Support Chart4h
Trond 7h
Per
API8h Nils

Opera Create
Support
Per 4h Arne
SDP8h
Chrome
Support
Nina 4h
This is an Example made
with another Tool
Boards
Taskboard
https://www.halvorsen.blog

File Structure

Hans-Petter Halvorsen
Folders and Files
Folders and Files
https://www.halvorsen.blog

Visual Studio

Hans-Petter Halvorsen
 Visual Studio
• You use Visual Studio to connect
to the Repository/Project
• Possible to Check-in/Check-out
your Code
•…
Connect to Project
Source Control Explorer
Check-in/Check-out
https://www.halvorsen.blog

Bug Reporting and

Monitoring
Hans-Petter Halvorsen
 Bug Reporting and Monitoring
We can use Azure DevOps for Reporting and
Monitoring Bugs, Feature Requests, etc.
• Work Items
• Queries
New Bug
Feature Request
Queries
Hans-Petter Halvorsen
University of South-Eastern Norway
www.usn.no

E-mail: [email protected]
Web: https://www.halvorsen.blog