# DASA DevOps #### 6x Core Principles
4x Focus Areas ---
PRINCIPLES
Customer-Centric Action
Create with End-in-Mind
End-to-End Responsibility
Cross-Functional Autonomous Teams
Continuous Improvement
Automate Everything You Can
DEFINES
FOCUS AREAS
Culture
Organization
Process
Automation
MEASUREMENTS + IMPROVEMENTS
The DevOps Core Principles Define All Aspects of Information Technology
--- ## Customer-Centric ## Action ------ > It is imperative nowadays to have short feedback loops with real customers and end-users. Therefore, all activities involved in building IT products and services should revolve around customers. ------ ### Mindset & Behaviours * Listening effectively * Asking questions * Receiving feedback * Adding value to offerings * Being receptive to frequence change ------ ### Enabling Culture * Operationalize customer empathy * Customer orientation and insights * Facilitate direct interaction with customers ------ ## "Courage" To act as Lean startup --- ## Create ## with the End in Mind ------ > The principle focuses on understanding the real needs of customers and working towards creating products and services that will solve their problems. In other words, the principle considers taking a holistic view of both the creation and use of the IT product/service ------ ### Mindset & Behaviours * Collaboration * Product and service thinking * Engineering mindset * Sense of direction / focus ------ ### Enabling Culture * Creativity and imagination * "Can do" attitude * High performance * Measurement matters * Minimum depdendencies * Ease to navigate architecture * Processess easy to adopt ------ ## "Product" DevOps teams need to act as 'product companies' --- ## End-to-End ## Responsibility ------ > In a DevOps organization, teams are vertically organized so that they can be fully accountable for the products and services they deliver. End-to-end responsibility means the team itself is accountable for the quality and quantity of services it provides to its customers. ------ ### Mindset & Behaviours * Learning attitude * Understanding others perspective and concerns * Empathy ------ ### Enabling Culture * Cultivating collective responsibility * Jobs with overlapping responsibilities * Redesign work procedures * Redesign organizations in consultation ------ ## "Vertical" Vertially organized so fully accountable for thier service --- ## Cross-Functional ## Autonomous Teams ------ > In product organizations, vertical, fully responsible teams need to be fully autonomous throughout the entire lifecycle of the product. The teams should possess all the necessary expertise to take on the end-to-end responsibility. ------ ### Mindset & Behaviours * Synergistic * Giving and receiving feedback * Purpose-orientated ------ ### Enabling Culture * Blameless * Trust * Autonomy ------ ## "T-Shaped" And complimentary skills --- ## Continuous ## Improvement ------ > In a DevOps culture, a strong focus is put on continuous improvement to enhance the products/services offered to customers. Some of the improvement activities include minimizing waste and optimizing speed, costs, and ease of delivery. ------ ### Mindset & Behaviours * Instil Lean behaviours * Eliminiating waste * Structured communications * Addressing problems quickly * Who creates problems fix them * Incremental journey ------ ### Enabling Culture * Shared understanding * Solving real problems * Make tacit knowledge explicit * Make change everyone's journey * Outcome measurement * Celebrating success ------ ## "Fail Fast" Plan, Do, Study/Learn, and Act --- ## Automate Everything ## You Can ------ > Automation is synonymous with the drive to renew the way through which the team delivers its services. Extensive automation means having a deep understanding of the processes needed to develop and deliver IT services. ------ ### Mindset & Behaviours * Way 1 - Flow & Speed * Cost, Quality, and Time triangle * Standardization * Automation first ------ ### Enabling Culture * Quality focus * Empower people to drive automation ideas ------ ## "Flow" Maximise flow. Repeatable rigor.