Definition of done Making a case for dev ops
-
Upload
adetunji-sunmonu -
Category
Software
-
view
67 -
download
0
Transcript of Definition of done Making a case for dev ops
DEVOPS
Adetunji Sunmonu
D e f i n i t i o n o f D o n e
When is your software project
done?
2
You are not paid for your code
to run on machine, but in
production
3
Tunji Sunmonu
4
THEMES
5
C –CULTURE
A –AUTOMATION
M –MEASUREMENT
S -SHARING
6
CULTURE
7
Lowering the risk of change
(from all aspects of delivery)
8
“Synergy” between different
functions of business.
9
Keep the organization
competitive not just keep the
light on
10
There is no one right way
11
Scrum Master == DevOps Engineer?
Retros == Logstash?
12
AUTOMATION
13
“Automation allows more time
for Design”
“Repeatable Results, Faster”
14
Automated Testing
15
Infrastructure as code
16
One Source of Truth
17
Consistency - which enables
sharing and caring
18
(Continuous) Deployment
19
MEASUREMENT
20
Monitoring
21
Measure everything
22
Learn from your Infrastructure.
Anticipate
23
Extract business value
24
Metrics for learning and
feedback.
25
SHARING
26
Shared Goal – improve reliability
and speed
27
Shared Problem Space –
deployment, delivery
28
Shared Priorities – what gets
improved first
29
Shared Location – minimize communication
effort, make it personal
30
Shared Communication – chat,
wiki, mailing list
31
Shared Codebase – code and
infra code
32
Shared Responsibility – fix the
build, fix the deploy
33
Shared Workflow – one button
deply
34
Shared Knowledge
35
Shared Success and Failure –
common experience, history
36
ANTI-PATTERN
37
38
39
40
41
42
43
44
45
The software isn’t finished until
the last user is dead
46
Sidney Markowitz
References
Patrick Debois - Devops with the S for sharing
Matthew Skelton - What Team Structure is
Right for DevOps to Flourish?
47