DevOps is the way a group of people, who typically hold different roles, skills, and responsibilities, work together to achieve some goal. Itβs a collaboration protocol, and asking one person or one team to βdo all the collaboratingβ makes no sense. Put another way, if you adopted DevOps because you had a silo problem, creating a new βDevOpsβ silo is unlikely to be an effective solution. (1)
Widely accepted definitions of DevOps:
Β Β Β Β CALMS (Culture, Automation, Lean, Measurement, Sharing)
Β Β Β Β The Three Ways (Flow aka "Systems Thinking", Amplify Feedback Loops, Continual Experimentation and Learning)
Β Β Β Β Accelerate metrics (Lead time, deployment frequency, MTTR, change failure %)
"We simply donβt give DBAs enough credit for all the tasks they do beyond writing queries."
https://towardsdatascience.com/has-devops-killed-the-ba-qa-dba-roles-fbc187abddeIndividuals and interactionsΒ
Working software
Customer collaborationΒ
Responding to change
over
Processes and tools
Comprehensive documentation
Contract negotiation
Following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Scaled Agile Framework (SAFe)
Scrum@Scale
Scrum of Scrums
Enterprise Scrum
Disciplined Agile (DA)
Lean Management
Spotify Model
Large Scale Scrum (LeSS)
Agile Portfolio Managemtn (APM)
Nexus
Recipes for Agile Governance in the Enterprise (RAGE)
Jira Align
Jira Software
Mural/Miro
Azure DevOps
Microsoft Excel
Microsoft Project
Trello
iObeya
Thoughtworks/Mingle
Microsoft Visual Studio
Eclipse