# DASA DevOps #### Coaching --- ## Coaching for Performance > Performance is the **total expected value to the organisation** measured against preset known **standards of accuracy, completeleness, costs, and speed**. ------ 1. Value to the Organization 1. Behaviours of Individuals and Teams 1. Quality, Completeness, Cost, and Speed ------ ### Objective & Key Results #### OKRs A performance framework OKRs help unlock performance potential by aligning goals across teh organization. The focus on OKRs enables employees to strive for accountability and success. ------ ### Measuring the Performance #### The DevOps Way
Customer and Business Value
Efficiency and Effectiveness
Quality and Velocity
Culture, Collaboration, and Sharing
External Factors
Internal Metrics
Foundation
------ ### Customer & Business Value * Net Promoter Score (NPS) * Lead Times * Customer Conversion * Revenue Per Feature ------ ### Efficiency & Effectiveness * FTE to Customer Ratios * Cost Per Transaction * Change / Release Cost Burden ------ ### Quality & Velocity * Mean Time to Recovery * Rollback Rates * Cycle Times * Deployment Frequency * Operational Support Costs ------ ### Culture, Collaboration, Sharing * Staff Retention * Morale / Job Satisfaction * Open Source Contributions * Mentoring --- ## Coaching for Change ------ ### The Three Ways 1. Understand their ecosystem from end-to-end 2. Operationalizing feedback loops 3. Optimizing the continuous delivery pipeline ------ ### The Three Stages 1. Scripting to Automated 2. Automated to Continuous Delivery 3. Continuous to Optimized ------ ### Individual vs Organization > The Change journeys undertaken at an individual level or at an organization level are distinct. > A team, as a group of individuals, can potentially go through the change journey of an individual. > Alternatively, the team as a microcosm of an organization can also go through the change journey to be described for an organization. ------ ### Individual Journey of Change Elisabeth Kubler-Ross Model or **Grief Cycle** 1. Denial (Info + Comms) 2. Resistance (Info + Comms) 3. Disorientation (Emotional Support) 4. Experiementation (Guide + Direct) 5. Commitment (Guide + Direct) ------ ### Denial * Avoidance * Withdrawal * Silence ------ ### Resistance * Pushback questions * Example: Why should we do that? * Highlighting all points of risks and failure ------ ### Disorientation * I do not have clarity on how to more forward * Can we work out a different timeline?> * Can we get additional resources? ------ ### Experimentation * Can we try some alternate options? * How about if we invest in tools / training? ------ ### Commitment * Happy that we got through this * Happy to contribute to this ------ ### Kotter's 8-Step Process 1. Create a sense of urgency 2. Build a guiding coalition 3. Form a strategic vision and initiatives 4. Enlist a volunteer army 5. Enable action by removing barriers 6. Generate short-term wins 7. Sustain acceleration 8. Institute change --- ## Coaching Competencies ------ ### Foundational Competencies Build a conducive ecosystem for individuals, teams, and the organization to live the 6x Principles. To do so, the foundational mindets required within the **"core self"** are: 1. Presence 2. Listening 3. Questioning 4. Direct Communication ------ ### Enabling Competencies 1. Contracting 2. Influencing 3. Feedback ------ ### Coaching Modes 1. Consulting 2. Facilitation 3. Mentoring 4. Coaching ------ ### Structural Competencies 1. Agile 2. Operations 3. Lean 4. Security ------ ### DASA DevOps Competencies 1. Enable and Scale 2. Specify and Verify 3. Create and Deliver --- ## Self #### Presence ------ > Presence is the ability to connect authentically with the thoughts and feelings of others to motivate and inspire them toward the desired outcome. ------ * You are connceted with yourself * You are attuned to be non-judgemental * You are set to be vulnerable * You are curious ------ > Presence inspires Trust and Intimacy that open deeper sharing and awareness. > It allows “aha! moments” that fuel new action. ------ > Presence allows a soft curiosity that opens a broader listening and powerful questioning to rise. > It helps create awareness. ------ * Preserve a posture of curiosity * Ask wide-open questions * Listen for energy levels * Thereby, know how to engage and support * Coach is showing the mirror to the coachee * Maintain awareness of how invisible you are ------ ### Presence get Challenged 1. When anxiety or worry creeps in 1. When apathy or boredon creeps in --- ## Self #### Listening ------ ### Levels of Listening 1. Internal listening (subjective) 2. Focused listening (passive) 3. Global listening ------ ### VIBE Model * Voice - intonation, energy levels, sighs, etc * Information - verbal and non-verbal * Body Language * Emotions ------ ### Keys to Active Listening 1. Paying attention 2. With-holding judgement 3. Reflecting 4. Clarifying 5. Summarizing ------ ### Principles of Active Listening 1. Deep listening (whole body) 2. Observing self (awareness) 3. Observing the client 4. Reflecting back ------ ### Shift Response #### Waiting-to-Speak Syndrome > Result of thinking more about how to shift the topic into whatever suits our purposes than what the other person is saying ------ ### Support Response #### Opposite of Shift Reponse > The two parties keep the discussion moving by providing and sharing their thoughts and understanding --- ## Self #### Questioning ------ ### Impact of Powerful Q's * Generates curiosity in the listener * Stimulates reflective conversation * Surfaces underlying assumptions * Invites creativity and new possibilities * Stimulates attention / thought-provoking * Generates energy and forward movement * Channels attention and focuses inquiry * Touches a deep meaning ------ ### Principles of Questioning * Open ended (not leading) * Explorative (not directive) * Others Perspective * Reflective * Contextual * Investigative or Challenging * Inspiring ------ ### Funnel Your Questions * Stage 1 (Open Qs) - Start topics * Stage 2 (Probe Qs) - Specific info * Stage 3 (Close Qs) - Checking info * Stage 4 (What if Qs) - Paraphase to summarize ------ ### Practices * Pause between questions * Do not ask Qs for the initial 30% of time * Ask the question to self first --- ## Self #### Direct Communication ------ ### Matrix #### Assertive vs Expressive | | Low E | High E | | ------- | ---------- | ------------ | |
High A | Direct | Spirited | |
Low A
| Systematic | Considerate | ------ ### Being a Direct Communicator > Be clear, articulate, and **direct** in sharing and providing feedback ------ ### Being a Direct Communicator > **Reframe and articulate** to help the client understand from another perspective what he/she wants or is uncertain about. ------ ### Being a Direct Communicator > Use **language appropriate and respectful** to the team members/teams, for example, , non-sexist, non-racist, non-technical, and non-jargon. ------ ### Being a Direct Communicator > Use **metaphor and analogy** to help illustrate a point or paint a verbal picture --- ## Enabling Competencies #### Contracting ------ > A contract is defined as an explicit bilateral commitment to a well-defined course of action to produce. > It is a specific agreement between a Coach and a coachee (Individual, teams, or organization) to accomplish clearly stated goals. ------ ### Types of Contracts #### Business Contracting > Business Contracting is developed to ensure practical arrangements, such as time, place, duration, fees (if any), and agreements with referring bodies or agencies. ------ ### Types of Contracts #### Professional Contracting Purpose and focus Shared articulation
(define and agree the problem / focus area) Clarity of wants and needs ------ ### Types of Contract #### Psychological Contracting > Psychological Contracting consists of unspoken and often unconscious expectations that are brought > to the Coach room by the Coach and the Coachee. It creates a sort of an implicit agreement between > the two that can have positive or negative consequences --- ## Enabling Competencies #### Feedback ------ ### Emotions #### Positive or Negative > Free from personal attack (move from Subjective to Objective) ------ ### Behaviour #### Passive, Aggressive, or Assertive > Meaningful, growth-oriented and forward moving ------ ### Clarity #### Fair or Poor > Alignment between employees and organizational needs ------ ### Relationship #### Make or Break > Demonstrate respect for the other person ------ ### Acceptance #### Compliance or Commitment > Complete understanding of the change expectations ------ ### Feedback Triggers 1. Truth - About the content 2. Relationship - About person delivering feedback 3. Identity - About relationship with self ------ ### Feedback Sessions 1. Build rapport (Relationship) 2. Be specific (Truth) 3. "Feedforward" (Identity) 4. "Growth Mindset" (Truth + Identity) 5. Stop (Identity) ------ ### COIN Method * **Connection** to the person's goals/interests * **Observations** that are specific * **Impact** on the business * **Next steps**: suggest, discuss, agree ------ ### Types of Feedback 1. Appreciative 2. Developmental 3. Evaluative ------ ### Types of Feedback #### Appreciative See, acknowledge, connect, motivate, and thank. > Fundamentally about a relationship and human connection. Being seen, feeling understood by others, matters deeply to all of us, and we connect with that individual well. ------ ### Types of Feedback #### Developmental > Help the client expand knowledge, sharpen the required skill, improve capability. Address the client's feelings or an imbalance in the relationship ------ ### Types of Feedback #### Evaluative > Rate or rank against a set of standards, align expectations, and inform decision-making ------ ### Setting up a Feedback Culture * Everybody is valuable and can improve. * Focus both on positive and negative feedback * Provide a supportive ecosystem * Aims at Objective, Actionable, Future-Oriented * Allow the recipient to decide
whether to ‘accept’ the feedback * No ‘self victimization’ by either party ------ ### How to build Feedback Culture * Role Modelling * Communicate beliefs/behavior * Clarify ’non negotiables’ * Resolve ‘what is in it for me’ * Highlight ‘early adopters’ * ‘Socialize’ down the Hierarchy * Stories and… more stories --- ## Coaching Modes #### Coaching ------ > Coaching is partnering with clients in a thought-provoking and creative process that inspires them to maximize their personal and professional potential. ------ ### Performance ### = ### Potential - Interference ------ The focus of coaching is to explore and get the coachee aware of these interferences and minimize or eliminate these to realize and translate the potential of the coachee into peak performance. ------ > Coaching is a way of working with people that makes them more competent and fulfilled so that they are more able to contribute to their organization and find meaning in what they are doing. ###### Coaching – Evoking Excellence in Others By By James Flaherty ------ ### GROW Model ###### By John Whitmore * Goal * Reality * Options * Way Forward ------ ### Goal * What do you want to achieve? * What is the ideal? * What are your objectives? ------ ### Grow - Examples * Competency wheel * SMART goals * Objective and key results (OKRs) * Team health check ------ ### Reality * Where are you now? * What is the current reality? * Ask for self-assessment * Get feedback ------ ### Reality - Examples * Force Field Analysis (FFA) * Agile assessments * SWOT analysis ------ ### Options * What can you do to bridge the gap? * What are the options? * Who can help you? * What do you need? * Brainstorm ------ ### Options - Examples * Brainstorming (as a team) * TOWS analysis * Impact mapping ------ ### Way Forward * What are the actions? * Commit to action * What are the next steps? * Timing and action plan ------ ### Way Forward - Examples * Minimum vialble improvement (MVI) * Roadmaps * Hypotheses to be tested ------ ### Coaching Operating Principles 1. Trusting relationship 2. Human potential 3. Pragmatism 4. Three-way learning 5. Context 6. Full engagement --- ## Coaching Modes #### Mentoring ------ > Mentoring is a partnership based process in which an experienced individual (Mentor) assists another person (Mentee) in making significant advances in knowledge, skills, perspective, and vision to develop their full potential. ------ | Element | Shift Required | | ----------------- | -------------------------- | | Mentor Role | Directive > Facilitative | | Mentee Role | Passive Receiver > Active Partner | | Learning Process | Mentor-Directed > Self-Directed | | Relationship | Calendar-Focused > Goal-Orientated | | Focus | Knowledge > Reflection & Application | ------ ### Focus on Learning Styles * **Activist** (Doing) - Hands on / open-minded * **Reflector** (Feeling) - Careful, thoughtful * **Pragmatist** (Thinking) - Practical, realistic * **Theorist** (Watching) - Logical, rational ------ ### Mentoring Techniques * **Support** - Holding Activity / Safe Place * **Support** - Identification of stumbling blocks * **Challenge** - Creative tension * **Challenge** - Feedback ------ | | **No Support** | **Support** | | :--- | :---: | :---: | | **Challenge** | Regression | Growth | | **No Challenge** | Stasis | Validation | --- ## Coaching Modes #### Facilitation ------ > Facilitation is a fluid process of engaging participants in creating, discovering, and tapping into group synergy that inspires them to maximize performance. ------ **Acts as a "guide on the side"** Assists the participants to enhance
the effectiveness fo their work Helps them know their common objectives ------ ### Benefits of Facilitation > Increases the quality of and commitment to decisions > Improves working relationships and implementation time ------ ### Benefits of Facilitation > Improves personal satisfaction and organizational learning > Discovers the wisdom of the team and enables its growth ------ #### 1. Observe and Select What do I see and hear? ------ #### 2. Make Meaning What do I think cuased this to happen? ------ #### 3. Choose How to Respond Is this worth saying something about? ------ #### 4. Test Observation I think I saw/heard X. Did I miss something? ------ #### 5. Test Meaning I'm thinking X. What do you think? ------ #### 6. Jointly Design Next Steps I think it would be helpful X. What do you think? ------ #### Explain reasoning and intent The reason I'm saying/asking this is X --- ## Mapping **Coaching Modes to Areas of Focus**
Facilitation
Coaching
Consulting
Mentoring
Ask
Tell
External Knowledge
Internal Knowledge
Focus on the process
to get to the outcome
Focus on converting
coachee's potential
to performance
Focus on the
outcome
Focus on converting
mentor's experience to
mentee's learning
--- ## Gemba Walk #### Different Views ------ ### Potential View * True potentials in teams and individuals * Trends that inform future strategies * New markets for products and services ------ ### Waste View * Waste identification and removal * Quality loss * Muri (overburden) * Mura (variability) ------ ### Problem View * How to solve the problems? * What are we trying to achieve? * What is getting in the way of this goal? * Consider: Policy, People, Process, Tech ------ ### Kaizen View * Patterns, forms, habits, routines * Gaps of perception with reality and culture ------ ### The 8x Wastes * Defects * Overprocessing * Waiting * Non-Utilized Skills * Transportation * Inventory * Motion * Extra-Processing (downtime) ------ ### The 5S * Seiri - Sort (easy to do work) * Seiton- - Strighten (organise) * Seiso - Shine (clean) * Seiketsu - Standardize (practices) * Shisuke - Sustain (training/feeback) --- ## Team Coaching ------ ### Attributes of Team Coach * Focus on the whole * Systems-thinking perspective * Comfort with ambiguity * Ability to set boundaries * Long-term view ------ ### Types of Intelligence > **Emotional intelligence** is the capacity to identify, express, and skillfully leverage emotions to complement each other skills. ------ ### Types of Intelligence > **Social intelligence** is the capacity to accurately empathize with another’s experience and create a relationship to meet the purpose of the team ------ ### Types of Intelligence > **Relationship intelligence** is the ability to interpret oneself as an expression of the DevOps team. What happens is not only personal, but it also belongs to the DevOps team --- ## Team Coaching #### Facilitation vs Coaching ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Approach** | Active guidance and leading for a specified method, process, or tool during a planned meeting or work session | Real-time interventions during regular team meetings and work sessions | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Reponsibility** | Implementing the method, process, or tool effectively to drive the team’s desired results | Sharing in-the-moment observations and questions that expand team awareness and potential for change | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Focus** | Around an event, such as a sprint planning, retrospective, and product roadmap | Bringing a team together to improve performance (both task delivery and collaborative behavior) and business outcomes | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Outcomes** | Achievement of a specific team goal or deliverable—the outcome is defined | haring in-the-moment observations and questions that expand team awareness and potential for change | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Performance** | Encouraged by the progress the team made, and the team leader and members may adopt useful facilitator behaviors and/or a new method, process, or tool | Positive changes in individuals and team members’ performance can be observed and reinforced right away | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Relationship** | Bring process expertise into the session without undermining the relationship with the group | Neutral and viewed with the perspective of “not an expert” to remain on an equal footing with the team | ------ ### Team Facilitation vs Coaching | | Facilitation | Coaching | | :--- | :--- | :--- | | **Frequency** | Mostly single session | Usually involves more than one session | --- ## Team Coaching #### Team Formation ------ ### DevOps Activities **Forming** * Defining goals * Outlining tasks * Reviewing procedures * Getting acquainted * Understanding roles ------ ### DevOps Activities **Storming** Having / having conflicts over: * Work behaviours * Ways of working * Goals * Roles and responsibilities ------ ### DevOps Activities **Norming** * Agree to decision making process * Setting up rules and norms * Establishing cutlure * Leading to commitment and cohesion ------ ### DevOps Activities **Performing** * Achieving effectively and efficiently * Accepting roles & responsibilities * Value interdependence of work * Working collaboratively * Learning from experience --- ## Team Formation #### Role of DevOps Coach ------ ### Forming * **Mentor / Consult** * Testing and dependence * Orientation to the task and testing * **Explaining** * Building trust & vulnerability ------ ### Storming * **Coach** * Intragroup conflict * Emotional response to task demands * **Demonstrating** * Productive conflict * Difficult conversations ------ ### Norming * **Facilitate** * Develop group cohesion * Open discussions * **Guiding** * Mututal accountability * Decision rights ------ ### Performing * **Facilitate** * Functional role readiness * Emergence of insights * **Enabling** * Commitment * Common purpose --- ## Team Coaching #### Team Coaching Process ------
Inquiry
Diagnosis
WoW
Sensing
Expressing
Presence
Design
and Review
------ > Being Present with all our faculties is critical to our ability to observe, perceive, infer, and partner with the coachee—individuals or teams. --- ## Sensing #### Behaviours for DevOps Culture ------ **Continuous Learning & Improvement** Retrospectives, facilitate knowledge sessions, hackathons, make people responsible ------ **Experimentation** Provide time, Instant sandbox environment, remove hurdles, applaud ideas, safe to fail ------ **Build Quality in** Test automation, responsibility for end-result, the team knows best, root-cause analysis, process automation (deploy, provision), continuous improvement, transparency (monitors) ------ **An Engineering Culture** Hire people with matching ambitions, every repeated task is automated, support experimentation, support automating manual tasks, do not focus only on utilization ------ **A Culture of Effectiveness** Begin with the end in mind, ask why? people broaden activities, handover moments avoided, move away from rigid processes, achieve results in small batches, Lean ------ **A Culture of Product Thinking** Customer to attend demos, user feedback onto the storyboard, allow customers to write about the product and respond, organize people around the product, team to write blogs about the product, you build it, you run it ------ **A Culture of Taking Responsibility** Address derailment openly, let people figure out how to do things, rewards responsibility, reward failure, transparency in what everyone is doing --- ## Sensing #### Behaviours for Organization ------ **Product Owner** The Squad has a dedicated Product Owner who prioritizes the work and takes both business value and technical aspects into consideration. ------ **Agile Coach** The Agile Coach helps the Squad to identify impediments and coaches them to continuously improve their process. ------ **Influence Work** Each Squad member can influence his/her work, be an active part in planning, and choose which tasks to work on. Each member can spend 10% of his/her time on hack days. ------ **Easy to Release** The Squad can (and does!) get stuff live with minimal hassle and synchronization. ------ **Process that Fits the Team** The Squad feels ownership of their process and continuously improves it. ------ **A Mission** The Squad has a mission that everyone knows and cares about. The stories on the backlog are related to the mission. ------ **A Culture of Taking Responsibility** The Squad knows where to turn to for problem-solving support, for technical issues, and ‘soft’ issues --- ## Sensing #### Behaviours for Process ------ **Peer Review** Peer reviews are conducted within the teams, not through separate teams. ------ **Version Control** Everything is in version control: code, tests, infrastructure definitions, deployment definitions, configurations, and deployment units. ------ **Continuous Delivery** Everything is automated: Peer Review Process, Build Automation, Test Automation, Deployment Automation, and Systems Provisioning. ------ **Functional Design** Functional designs are provided as test specifications that can be used for test automation. ------ **Process Improvement** 10% of time is reserved to continuously improve process and its automation aspects. ------ **Alignment** Business and IT are at the same location and part of the same team. They work together following the “de facto” standard for Scrum. ------ **Engineering Mindset** Manual recurring steps are automated instantly. --- ## Five Dysfunctions of Team #### By Patrick Lencioni ------ ### Lack of Trust > DevOps is about culture and collaboration, and the most important cultural and collaboration ingredient a team must establish and cultivate is trust. ------ ### Fear of Conflict > Roger Martin in his book **The Opposable Mind**, argues that “the ability to face constructively the tension of opposing ideas and, instead of choosing one at the expense of the other, generate a creative resolution of the tension in the form of a new idea that contains elements of the opposing ideas but is superior to each. ------ ### Lack of Commitment > Like any other people, team members will buy into something when their opinions are included in the decision-making process. Productive teams co-create transparent decisions and are confident that they have the support of each team member. The co-creation is not about seeking consensus but making sure everyone is heard ------ ### Avoidance of Accountability > A DevOps Coach can also support the team members to develop their confidence to hold one another accountable and clarify exactly what the team needs to achieve, who is responsible to deliver what and how others must behave in order to make it successful. ------ ### Inattention to Results > Inattention to result is the ultimate dysfunction of a team. It exists when individualism takes the precedence over collectivism. Group members seek out individual recognition and credibility at the cost of the collective results of the team and what the team should achieve. --- ## Building Trust #### ( C + R + I )/ S ------ ### Credibility * Logical, clear communicator * Honest and open * Demonstrates expertise * Strong credentials ------ ### Reliability * Consistent * Sees word as bond * No surprises ------ ### Intimacy * Others confide in * Empathetic * Discreet ------ ### Self-Orientated * Moves on easily from disappointment * Leads with curiosity, other-focus * Comfortable changing agendas / objectives * Focus on long-term relationships * Achieve goals through other's achievements --- ## Conflict Management **Strategies**
Assertive
Passive
Uncooperative
Cooperative
Competing
Collaborating
Avoiding
Accommodating
Compromising
------ ### Collaborating **High Cooperation, High Assertiveness** > The ideal strategy is win-win, which corresponds to both individuals staying firm about protecting their interests while being sensitive about the other’s interests. In reality, the percentage of conflicts being resolved in this manner would be small. They tend to get resolved through other strategies ------ ### Avoiding **Low Cooperation, Low Assertiveness** > It is the stage where there no effort is taken to further one’s interests or yield to the other’s interests. It is a no-action passive state. Most of the time, this tends to be a sub-optimal approach to conflict resolution. It demonstrates a lack of responsiveness and ownership for the issue at hand. It could also keep the conflict lingering for a long time. ------ ### Competing **Low Cooperation, High Assertiveness** > This is the stage where you may feel that your interests are of paramount importance and imperative to safeguard these. Typically, these can come out of contractual culpability conflicts. It may seem that you are not interested in resolving the conflict. This position does not mean that there is no dialogue, but that there is a huge responsibility to provide as much data and facts as required to persuade the other party to your point of view ------ ### Accommodating **High Cooperation, Low Assertiveness** > This is the stage where you feel it is fine to yield to the other party based on your assessment of the risks to your interests (being sufficiently low) and the need to nurture the relationship from a long-term perspective.