DevOps Principles Meeting

Presented by : John Bright, Head IT Consultant

 Old Dev system Drawbacks

Too long cycles

Missing Team communication
Cost of deployment

Notes:
Too long cycles: 6 months in average !!
Missing communication between Dev & Ops Members More bugs and work
latency
Cost of deployment: less productivity and unmeasurable ROI.
 The Best alternative: DevOps

Notes:
DevOps = software dev + IT operations (Ops).
It aims to shorten the systems development lifecycle and provide continuous
delivery with higher software quality.
 Benefits of DevOps
• Agility
• Continuous Integration
• Continuous Delivey
• Quality Assurance
• Automation

Notes:
Agility is refering to the approach of discovering requirements and developing solutions through the collaborative effort of
self-organizing and cross-functional teams and their end user(s). It advocates adaptive planning, evolutionary development,
early delivery, and continual improvement, and it encourages flexible responses to change.
Continous Integration (CI) is a development practice where development teams make small, frequent changes to code. As a
result, development teams can detect problems early in a way to release incremental code changes to production quickly
and regularly.
Continuous Delivey (CD) is an approach to software engineering based on producing software in short cycles. By developing
in short cycles, teams can reliably release their software at any time. So, development teams can build, test, and release
software faster and more frequently. As a result, they can reduce the cost, time, and risk of delivering each change.
Quality Assurance Software is a means to ensure proper quality of the software. It includes standards (such as ISO 25010,
SPICE or CMMI) and procedures that managers, administrators or even developers may use to review and audit software
products and activities to verify that the software meets quality criteria which link to standards.
Automation engineering is the integration of standard engineering fields. Automatic control of various control system for
operating various systems or machines to reduce human efforts & time to increase accuracy.
 Value Stream Mapping

Notes:
To really get the team and our internal customers on board of this next step, I think it would create a lot of value by having them
involved in a value stream mapping exercise. It would really clarify where we have to put more focus and give us the right facts
and figures to set the right priorities going forward.
 DevOps Concepts (1): Three Ways
• It is an approach that describes 3 important ways in app development lifecycle:
First Way: Work always flows in one direction – downstream
Second Way: Create, shorten and amplify feedback loops
Third Way: Continued experimentation, in order to learn from mistakes, and achieve mastery

Notes:
The First Way:
The First Way states the following, about the flow of work: Work should only flow in one direction, No known defect should be
passed downstream, Always seek to increase the flow, The First Way helps us think of IT as a value stream. Think of a
manufacturing line, where each work center adds a component – value – to the line. Since each work center adds value, it is
preferred, that each work center does it right the first time around.
The Second Way:
The Second Way describes the feedback process as the following:
Establish an upstream feedback loop, Shorten the feedback loop, Amplify the feedback loop, The Second Way teaches us to think
of information as a value-addition. When timed right and used the right way, feedback can help optimize the value stream.
The Third Way:
The Third Way describes the environment and culture, as the following practices
Promote experimentation, Learn from success and failure, Constant improvement , Seek to achieve mastery through practice
The Third Way teaches us that culture and environment are just as important as the work being done.
It advocates a culture of experimentation and constant improvement. This results in measured risks and being rewarded for good
results.
DevOps Concepts (2): Improvement Kata

Notes:
The meeting broadly will have four steps…
1. Articulate the problem together
The first step of the improvement kata is to encourage participants to articulate the problem. We need to be able to simplify our language,
and describe the one issue that we are here to resolve. Cross-team communication for example. I put this description in the bottom left
corner.
2. Describe the best possible outcome
Next, we ask the room to articulate the best possible outcome that we could expect from our actions. In other words, if we assume unlimited
resources, and we have all the help and time we need, what would an excellent outcome look or sound like?
If the problem has been articulated clearly, then the awesome outcome should follow in a relatively straight-forward way. But this part is
really at the core of the kata, in that it encourages a change in thinking. We’re not discussing problem resolution now, we’re discussing how
to be more excellent. The target has shifted from ‘how do we put out this fire?’ to ‘how do we make things great?’
3. What is preventing us from achieving this excellent outcome?
The next topic is obstacles, and I put these in the bottom-right section.
Now that we all understand the problem we’re trying to solve, and we all agree on the most excellent outcome from our resolution, why
can’t we make this excellent outcome happen? This list will lead naturally into the last section.
4. Next steps, or tangible actions
In my experience, the suggestions for actions started really flowing once we had the shared understanding of the first three pieces. We’ve
defined a problem, we’ve set our target, and we understand the obstacles. Ok, now we talk about breaking down those obstacles and taking
small steps to improve the situation.
 DevOps Concepts (3): A3 problem solving steps
• 0: Identify the problem
• 1: Capture the current state of the situation
• 2: Conduct a root cause analysis
• 3: Define your target state
• 4: Develop a plan for implementation
• 5: Develop a follow-up plan with predicted outcomes
• 6: Build and Implement
• 7: Test
• 8: Release + results evaluation

Notes:
The A3 process allows groups of people to actively collaborate on the purpose, goals, and strategy of a project. It encourages in-depth problem
solving throughout the process to ensure that the project most accurately meets its intended goal.
0: Identify the problem : the first step is that you need to identify a problem or need.
1: Capture the current state of the situation: Once you align around the problem, capture and analyze the current state of the situation.
2: Conduct a root cause analysis: Try to figure out the root cause of the efficiencies such as : communication breakdowns? long delays without
activity? What information are we needing to collaborate more effectively/smoothly?
3: Define your target state : you are able to clearly define your target state through a process map.
4: Develop a plan for implementation : Implementation plans should include: A task list to get the countermeasures in place, Who is
responsible for what? Due dates for any time-sensitive work items
5: Develop a follow-up plan with predicted outcomes: A follow-up plan is a critical step in process improvement because it can help teams
make sure the: implementation plan was executed, target condition was realized, expected results were achieved
6: Build and Implement : Implement the source code and make the Build
7: Test: Make the necessary test : implementation test, functional tests, ..
8: Release + results evaluation: Launch the release and evaluate the validated results.
Towards a Generative Culture

Notes:
Let’s focus on the cultural aspect. I think we still see way too many elements : The Typology of Organisational
environments + Information processing style (a bureaucratic or even pathological culture in our working
environment) + Mutability to a new culture this will lead us to an Organisational Culture. Proper time and
attention to coaching and skill building is essential here. We also need to be consistent here across the
organization.
Next Actions Steps
• Value Stream Mapping
• Collect facts & figuresand setup workshop in 2020_Q4
• Three Ways
• Organize for downstream then feedback loops finally Continued experimentation in 2021_Q1
• Improvement Kata
• Implementing JIRA & Microservices for2021_Q2
• Generative Culture:
• Co-create development culture plan for dev team with HR support for 2021_Q3

Notes:
During this meeting I would like to take the time to discuss a bit more on DevOps proposals we
just talked about and I would also like to suggest a number of actions that would allow us to go
forward.
 The End

Thank for your time and consideration