DevOps - What things to measure (Stage 1)
Before you begin your journey into DevOps, you should assess yourself and see where your project is at and where you can improve.
Your team
How long does it take for a new developer who has joined a team to get everything up and running?
*
Less than an hour
Less than a day
Less than a week
Longer than a week
Does your code have documentation to help a developer get up and running?
*
No - they work it out themselves
No - someone sets it up for them
Yes - there is a Word doc
Yes - there is a README file in the repo
Yes - there is a YouTube video
Yes - and the process is codified e.g. DevContainers
Other
How does your team communicate? (choose the most popular one)
*
No - we don't chat
Yes - Email
Yes - Microsoft Teams
Yes - Slack
Yes - Skype
Yes - Discord
Other
How big is your dev team?
*
Just me
2-5 developers
6-10 developers
10+ developers
Does your team do any of these types of meetings? (tick all that apply)
*
Daily stand-ups/Daily Scrum
Sprint Planning
Sprint Reviews
Retrospectives
Backlog Refinement
Other
Are your teams cross-functional?
No - teams only work within their speciality
Yes - some team members can pick up any item in the backlog
Yes - all team members can pick up any item in the backlog
Yes - all team members can pick up any item in the backlog (but some tasks go to specialty teams)
Other
Back
Next
Save
Deployments
When was your last deployment? (choose the smallest applicable one)
*
Please Select
In the last hour
In the last day
In the last week
In the last fortnight
In the last month
In the last quarter
In the last year
Even longer
How many deployments did you make in the last week?
*
0
1
2-5
5+
How much downtime did you have last week (minutes)?
*
0
1-15
16-60
60+
When there is a production issue - how long does it take to fix it?
Minutes
Hours
Days
Weeks
Longer
Which environments do you deploy to?
Devlopment
Test
Staging
UAT
QA
Production
Training
Other
How long does it take for a code change to reach production? (aka cycle time - time from starting to write code to be running in production)
*
1-5 minutes
5-60 minutes
Hours
Days
Weeks
Other
Back
Next
Save
Coding Practices
Are you using source control?
*
No
Yes - GitHub
Yes - Azure DevOps (Git)
Yes - Azure DevOps (TFVC)
Yes - Subversion
Yes - BitBucket
Other
Which branching strategy are you following?
*
None
Custom tailored for my company
Gitflow
GitHub flow
GitLab flow
Release flow
Trunk-based development
Other
Does your code go through pull requests/code reviews?
*
Yes
No
What does your pull request process look like? (tick all that apply)
Automation - check that the PR is linked to a PBI in the backlog
Automation - run unit tests
Automation - lint code
Automation - build solution
Automation - deploy solution to ephemeral environment
Automation - security scanning
Automation - performance testing
Automation - UI testing
Review Code - over the shoulder check (in-person)
Review Code - over the shoulder check (screen share)
Review Code - send a chat message (e.g. Slack) and wait for a response
Review Code - track feedback in the PR
Backlog Items - log any accepted tech debt in the backlog
Manually - lint code
Other
On average, how long are the pull requests open for?
< 1 hour
2-4 hours
4-8 hours
2-3 days
4-7 days
Up to 2 weeks
Up to 1 month
Longer than 1 month
How often do you check for outdated dependencies?
Never
When I notice it
Every code change
Every day
Every week
Automated e.g. Dependabot
Other
Back
Next
Save
Development Process
Are you following a development methodology?
*
No
Scrum - I am a white robe
Scrum - but we change things
Extreme Programming (XP)
Lean Software Development
Feature-Driven Development (FDD)
Dynamic Systems Development Method (DSDM)
Kanban
Waterfall
"Agile"
Other
Do you know where your technical debt is?
*
No
Yes - We have unit tests
Yes - We use SonarQube
Yes - Code Analysis
Yes - Logged in the backlog
Other
Back
Next
Save
Automation
Do you automate server/infrastructure provisioning?
*
No - We have a SysAdmin that create servers/VMs
Yes - We use Chef to provision clean VMs with features configured using a recipe
Yes - We use SCVVM
Yes - Docker
Yes - Kuberenetes
Yes - Azure Resource Manager (ARM)
Yes - Azure Bicep
Yes - Terraform/OpenTofu
Yes - Pulumi
Other
Do you have an automated build process (push code, code gets built on a server)?
*
No
Yes - GitHub Actions
Yes - Azure DevOps Pipelines
Yes - BitBucket Pipelines
Yes - Jenkins
Yes - Circle Cl
Yes - TeamCity
Other
Do you have an automated deployment process (push code, code gets built on a server, code gets deployed to a server)?
*
No
Yes - GitHub Actions
Yes - Azure DevOps Pipelines
Yes - Bitbucket Pipelines
Yes - Octopus Deploy
Yes - We have a script we run that creates a zip or deploys
Other
Do you automate UI Testing?
*
No - Developer does the testing
No - End user does the testing
No - We have a test team
No - Exploratory Tests
Yes - Playwright
Yes - Selenium
Yes - Puppeteer
Yes - Cypress
Other
Back
Next
Save
Telemetry
Do you use a tool to track errors?
*
No - we wait for the end users to send/call us and tell us
Yes - ELMAH
Yes - Raygun
Yes - Seq
Yes - Application Insights
Yes - Serilog
Yes - Google Analytics
Other
Do you track application and server performance?
*
No
Yes - Application Insights
Yes - Raygun
Yes - New Relic
Other
Do you track application usage?
*
No
Yes - Application Insights
Yes - Raygun
Yes - New Relic
Yes - Google Analytics
Other
Back
Next
Save
Your thoughts
Describe a statistic that you gather, that you consider important:
*
DevOps - What is the most pressing thing you want solved?
*
How happy are you with your current DevOps efforts?
*
1
2
3
4
5
6
7
8
9
10
Name
Email
example@example.com
Please verify that you are human
*
Save
Submit Form
Should be Empty: