- A gap between strategy and delivery – we know what we want to do, and we have the people and tools to do it, but we can’t seem to do it. We end up building something different to what we intended in the strategy. This may be a sign of weak strategy, or it may be a product ownership problem – translating business strategy into the products and services to be delivered.
- A gap between desire for pace of delivery and ability to deliver. We want to go at 100mph, but we can only go at 30mph. The pace of delivery may be constrained by capability, tooling, process, constraints, or simply capacity. It’s usually not actually a capacity problem, however. In technological domains, this is the realm of DevOps transformations and the practices that enable value to be delivered at high velocity whilst maintaining reliability and quality.
- A lack of organisational observability that results in poor understanding of value flows across the organisation, poor awareness of sociotechnical aspects of the system as a whole, resulting in problems that are known by teams taking leadership by surprise, if they ever become aware of them. A lack of systems thinking, combined with poor psychological safety across the organisation, results in executives only being told what they want to hear, or information becoming diluted as it flows “up”.
- Short termism – poor incentive structures (indeed, most incentives) or cultures mean that people are focused on immediate short term wins rather than long term value and outcomes. This is also manifested by an adherence to project methodologies where the delivery of value has a start and, specifically, an end date, instead of a long-lived product approach that provides people with greater ownership of outcomes, longer lived teams, lower technical and operational debt, and higher quality products and services.
- Quality issues. We can build the right things, but we can’t do it well. Conflicts of interest or capability issues mean that products and services are delivered, but they suffer from reliability, consistency or architectural problems. Technical and operational debt is high, and teams feel like they are always firefighting and dealing with unplanned work. An approach of late inspection rather than building quality in to the process is often part of the cause of this dysfunction.
- Poor organisational ability to learn. Systems, cultures and processes hinder people’s (and groups of people, such as teams or business units) ability to learn from failures and successes. The same mistakes are made repeatedly, and when successes do get made, the valuable learning from them is not institutionalised. Psychological safety, along with rituals such as retrospectives, may be lacking in this organisation.
- An excessive inward focus. Focussing too much on “what we do” rather than looking out at the world for challenges, opportunities, and a changing landscape means that opportunities are wasted and challenges can present existential threats to the organisation through a lack of capability to become aware of them, let alone adapt to them. A strong organisational cultural identity, whilst a powerful and valuable aspect of an organisation, can result in this dysfunction.
- An excessive outward focus. A focus only on the external means that market and environmental opportunities and threats are detected, but threats to performance or opportunities for improvement arising from inside the organisation are not detected, mitigated or exploited.
- A bimodal approach to value where the products and services delivered to customers far exceed the quality and features of those delivered to people within the organisation who are expected to use those services to do their job. We wouldn’t provide surgeons with blunt scalpels and expect a great result for the “customer”, but many organisations provide poor quality services and tools to employees whilst expecting high quality outcomes.
The 2 state of DevOps reports each year aggregate the current state of technology organisations globally in respect to our collective transformation towards delivering value faster and more reliably. Or as Jonathan Smart puts it, “Sooner. Safer, Happier”.
The DevOps shift has been in progress for over a decade now, and whilst DevOps was always really about culture, the most recent reports are now emphasising the importance of culture, progressive leadership, inclusion, and diversity more than ever before.
Last year, in 2020, the core findings of the State of DevOps Report focussed on:
- The technology industry in general still had a long way to go and there remained significant areas for improvement across all sectors.
- Internal platforms and platform teams are a key enabler of performance, and more organisations were starting to adopt this approach.
- Adopting a long-term product approach over short-term project-oriented improves performance and facilitates improved adoption of DevOps cultures and practices.
- Lean, automated, and people-oriented change management processes improve velocity and performance over traditional gated approaches.
This year (2021), there are a number of key findings in the Accelerate State of DevOps Report, building on previous iterations:
- The “highest performers” continue to improve the velocity of delivery, through practices that enable teams to continually identify improvements to tooling, technology and process.
- Adoption of SRE practices improves wider organisational performance. Teams that prioritise both delivery and operational excellence report the highest organisational performance. Reliability is as important, if not more so, than short lead time for changes.
- Adoption of cloud technology accelerates software delivery and organisational performance, and enables the five capabilities of cloud native technology. Multi-cloud adoption is increasing, so that teams can utilise the strengths of each provider and improve resilience against risk of a single provider failure.
- Secure Software Supply Chains that integrate security practices into pipelines and processes enable teams to deliver secure software quickly, safely and reliably.
- Documentation is important. Teams that create and maintain high quality documentation are more able to implement technical practices, make changes, and recover from incidents.
- Inclusive and generative team cultures improve resilience and performance. Teams with psychologically safe and inclusive cultures suffered less from burnout during the Covid-19 pandemic.
View the entire 2021 Accelerate State of DevOps report here.