The Importance of Behaviour in a DevOps Environment
The behavior of people shows the culture of an organization. Which behaviors can you define, which would fit a DevOps environment? Did you think of these terms?
These are all relevant statements, but none of them is real behavior. Try to define behavior in terms of “what you see someone do or hear someone say.” Make it observable, measurable. Making it small and tangible, will enable the teams to visibly grow towards the new behaviors in incremental steps.
Examples of DevOps behaviors include:
- Multidisciplinary: “Team members actively pick up each other’s tasks when they see a team member is too busy or unavailable”
- Transparency: “The team publishes real-time progress reports on the floor monitors”
- Ownership: “The Product Owner drives the demos and adequately informs all his/her stakeholders regarding progress and deliverables”
- Prioritization: “The PO and TMs jointly discuss at least once per sprint the prioritization of the work on both functional and non-functional work items”
- Improve: “Every severe incident is followed by a blameless postmortem, where everyone involved shares ideas & opportunities for improvement”
- Fail safe: “All managers openly reward the identification, prevention ánd resolution of errors.”
Source: DASA DevOps Fundamentals coursebook.
Curious to know more?
DASA DevOps Fundamentals is the starting point for anyone involved in an Agile and/or DevOps team. Improved workflows and faster deployment start with a core understanding of DevOps fundamentals by all team members.