DevOps Improvements

Acronymat DevOps Areas of improvement - 24 DevOps Capabilities in 5 categories: CD, Architecture, Lean Management and Monitoring, Cultural.
Read more
Article

DevOps Areas of improvement


Continuous delivery

  • Use version control for all production artifacts
  • Automate your deployment process
  • Implement continuous integration
  • Use trunk-based development methods
  • Implement test automation
  • Support test data management
  • Shift left on security
  • Implement continuous delivery (CD)

Architecture

  • Use a loosely coupled architecture
  • Architect for empowered teams

Product and process

  • Gather and implement customer feedback
  • Make the flow of work visible through the value stream
  • Work in small batches
  • Foster and enable team experimentation

Lean management and monitoring

  • Have a lightweight change approval processes
  • Monitor across applications and infrastructure to inform business decisions
  • Check system health proactively
  • Improve processes and manage work with work-in-process (WIP) limits
  • Visualize work to monitor quality and communicate throughout the team

Cultural

  • Support a generative culture (as outlined by Westrum)
  • Encourage and support learning
  • Support and facilitate collaboration among teams
  • Provide resources and tools that make work meaningful
  • Support or embody transformational leadership

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.