The Dunning-Kruger effect can cause self-organizing teams to overestimate their maturity, creating a need for a structured check to provide alignment.
A maturity check should foster continuous learning, create a shared understanding of DevOps, and promote networking, not serve as a performance management tool.
DevOps is defined by three pillars: technical capabilities, a culture of collaboration and responsibility, and standardized processes like the Scaled Agile Framework (SAFe).
An effective check is a self-assessment focused on generating actions, with public results to encourage collaboration rather than for objective team comparison.
The maturity check is split into two parts to independently assess team-level collaboration and the technical maturity of each specific application they manage.
The team check evaluates collaboration, value orientation, team setup (like T-shaped skills), agile ways of working, and how the team manages its ecosystem dependencies.
The application check assesses key technical practices including collaborative development, continuous testing, automated deployment, monitoring, and customer feedback loops.
The self-assessment tool is designed for ease of use and has successfully helped both mature teams identify blind spots and new teams begin their improvement journey.
28:54Martyna Zurek
37:33Tobias Dunn-Krahn
42:29Lars Hesel Christensen & Basil Brunner
47:10Martin Nader
1:41:05Mathias Tausig
44:40Christoph Ruggenthaler
57:45Robert Hoffmann & Christian Denich
34:46Bruno Amaro Almeida
.webp?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
smartclip Europe GmbH
Hamburg, Germany
iits-consulting GmbH
München, Germany
Quanos Solutions GmbH
Nürnberg, Germany
