DevOps Practices Survey

Please answer the following questions to evaluate DevOps practices in your organization

QUESTION 1 of 4

Managing Work in Progress

How does your team manage how much work is taken on at once, especially when other teams, stakeholders and outside customers are involved?

We start almost all work whenever it’s requested from us. We deal with other teams or dependencies ad hoc.

We try to limit new work items and we stop accepting new work when other items are delayed or blocked. Dealing with other teams is often reactive or short before needed.

We have some limits on how much work we do at the same time. We stop working on items when new items with a higher priority are requested. We try to be aware of other teams’ timelines, but frequently they’re waiting for us or we’re waiting for them.

We have fixed limits on how many work items we work on at the same time. We only pick up a new work item when an old item is finished. We take other teams schedules into account to avoid waiting time and delays.

QUESTION 2 of 4

Organized teams

How is your team’s work organized and how do you track progress and handle blocked work?

We don’t follow a specific way of working; work items are worked on for many days, progress can only be seen when work is almost finished and people outside the team don’t know when something is

We try to follow a method (e.g. Scrum, Kanban), but most work isn’t finished at the end of the iteration. We track blockers, but most of them aren’t solved on time for work to be finished at the end of the iteration.

We follow a clear method (e.g. Scrum, Kanban). We break work into smaller pieces, and use a visual board, but identifying or resolving blockers is still a challenge. A majority of the work is delivered within an iteration.

We consistently use a structured method, work in small batches, track progress visually, quickly identify and address any blocker, and almost all work is finished within an iteration.

QUESTION 3 of 4

Result Focus & Data Driven

How are your goals created and used, and how does data and experiments influence your day-to-day decisions?

Goals are often high-level and mainly set by leadership. They arent tied to specific outcomes or used in our daily work. We rarely look at data unless theres a problem. Team members trying out new ideas or tools, but without measuring success.

Leadership defines measurable goals, and teams deliver input. They aren’t used in our daily work, and reviewed with intervals of more than a month. Decisions are mostly based on individual opinions and experience. We try new things occasionally and we show the results to others, but without a clear process, measurement or follow-up.

Leadership defines clear goals per quarter and helps teams to shape them in SMART outcomes. We use dashboards or reports to track progress and adjust our work and priorities when SMART outcomes are at risk. Experiments follow an agreed format, data driven and learnings are followed up.

Goals are constantly cocreated, SMART, and directly linked to daily work. Data is used daily to guide priorities, spot opportunities, and evaluate outcomes. Experimentation is a core part of how we work. We test to validate ideas before scaling them. These experiments are structured, tracked, and discussed in a culture of continuous improvement.

QUESTION 4 of 4

Organizational Culture

How would you describe the way your team or organization approaches challenges and communicates across roles and teams?

Our leaders are empowered as the central decisionmakers, and their guidance help the teams stay focused and high performing. Information is shared when needed, and problems are escalated to those with authority to resolve them efficiently.

We rely on well-established rules and formal processes to handle challenges. Everyone understands their responsibilities, and information is shared through clear channels to ensure consistency and accountability.

We work together across roles to solve problems, processes are helpful rather than strict boundaries. Information is actively shared and used to support collaboration and informed decision-making.

We raise concerns, contribute ideas, and take initiative – regardless of our role or seniority. Problems are seen as opportunities to learn, and are addressed quickly. We regularly reflect on how we work and improve not just our outcomes, but our ways of working.

Please answer all questions before viewing results!