Session I held at MK.NET, where I introduced the services of Azure DevOps starting from real-world stories of usage or uncommon scenarios where it proved massively beneficial

1. Aselectionofshort
storieswhereAzure
DevOpssavedthebacon
Matteo Emili – Microsoft MVP

2. MatteoEmili
Microsoft MVP – Developer Technologies
matteo.emili@live.com
https://twitter.com/MattVSTS
https://mattvsts.github.io
2

3. Doweallknowwhat
AzureDevOpsis?
It actually goes back a long time…
3

4. Introducing Azure DevOps
Deliver value to your users faster
using proven agile tools to plan,
track, and discuss work across
your teams.
Build, test, and deploy with CI/CD that
works with any language, platform,
and cloud. Connect to GitHub or any
other Git provider and deploy
continuously.
Get unlimited, cloud-hosted
private Git repos and collaborate
to build better code with pull
requests and advanced file
management.
Test and ship with confidence
using manual and exploratory
testing tools.
Create, host, and share packages with
your team, and add artifacts to your
CI/CD pipelines with a single click.
Azure Boards Azure ReposAzure Pipelines
Azure Test Plans Azure Artifacts
https://azure.com/devops


5. 5
Some talking points about Azure DevOps
In short…
• Server and Service - different upgrade
cadence, close to no feature drift
• Technology agnostic
• Integrated yet fully modular
• Highly flexible
• Huge marketplace for extensions
I could go on for hours, talking about how Azure DevOps
evolved over the past fifteen years becoming what it is
today, but as we only have a finite amount of time I will
limit myself to these:

6. Story#1
We cannot track our own code!
6

7. What happened?
If you leave control of a product to a technological team,
the first thing it focuses on is code.
While this is good in the short term, it is almost impossible
to track back with certainty what happened at a certain
point in time (releases!)
How Azure DevOps helps here…
• Linking commits to Work Items and associating them to
builds made the tracking job an easy exercise
• Taking advantage of Work Item Tracking also means
bringing a collaboration dynamic to the Product
Ownership, where collaboration is not limited to a fixed
number of opportunities
• Eventually, the team moving to a wider landscape of
work brought benefits to the overall deliverables.
Imagine fixing a bug now!
7

8. Demo
8

9. Story#2
Automate all the things!
9

10. What happened?
You need to automate stuff, and you start looking at all
sorts of tools and products to achieve your goal, while
sometimes the easiest solution is just in front of you.
If you change your point of view, Azure Pipelines is simply
an orchestration engine for automations.
How Azure DevOps helps here…
• Azure Pipelines only need an agent to be fully functional
• A host can become a Pipeline runner or a target
• Once you have the agent running, the number of
automation opportunities is almost endless
• Extremely valuable in controlled environments or
regulated industries
10

11. Demo
11

12. Story#3
It’s time to migrate!
12

13. What happened?
It is inevitable that at some point a team will face a code
migration process – the industry evolves, but everyone has
its own pace and they will go through this on their own.
Usually, it is about two scenarios: centralised to distributed
(TFVC to Git) or hoster to hosted
How Azure DevOps helps here…
• Moving TFVC to Git is a breeze thanks to the Import
Repository feature
• The same feature can be used for moving from a third
party hoster (GitHub, Bitbucket, etc.) to Azure DevOps
• For more complex moves, there are tools for both code
and Work Items – Azure DevOps has got an API layer
anybody can take advantage of
13

14. Demo
14

15. Questions?
15

16. ThankYou!
https://slideshare.net/matteoemili
Matteo Emili
https://mattvsts.github.io