Atlassian in Seoul 2018 발표 자료입니다.

2. 황 희 연 | A G I L E & D E V O P S C O N S U L T A N T | C U R V C
The CALMS Framework for
DevOps

3. Agenda
Today’s Situation
Understanding DevOps
CALMS Framework
Keep CALMS
DevOps Maturity Self Checking

4. Rising business expectations
TODAY’S SITUATION

5. Quality
TODAY’S SITUATION

6. Stability
TODAY’S SITUATION

7. Ops, QA, Testing, Support not aligned
with development
TODAY’S SITUATION
Developme
nt
QA
team
Ops
team
Support
team

8. New technologies
TODAY’S SITUATION
Cloud Big Data AI Containerizatio
n
Mobile
Agile development

9. Competitions
TODAY’S SITUATION

10. Work and life balance
TODAY’S SITUATION

11. DevOps Overview

12. What is DevOps?
UNDERSTANDING DevOps
Everyone involved in
developing
Software products and
services
Development Operations
Everyone involved in
developing
, mapping and supporting

13. Goal of DevOps
UNDERSTANDING DevOps
Deliver software with increased speed and high
reliability

14. DevOps | ALM* | Agile
UNDERSTANDING DevOps
DevOps is the ultimate outcome of implementing
ALM within the Agile framework.
* ALM (Application Lifecycle Management)

15. DevOps Principles: The Three Ways
UNDERSTANDING DevOps
Looking Performance as a whole
Dev Ops
Business
Custome
r

16. DevOps Principles: The Three Ways
UNDERSTANDING DevOps
Amplify feedback loops
Dev Ops
Business
Custome
r

17. DevOps Principles: The Three Ways
UNDERSTANDING DevOps
Culture of continual experimentation and
learning
Dev Ops
Business
Custome
r

18. Enablers
UNDERSTANDING DevOps
Agile and lean Cloud &
Container
MonitoringInfrastructure
as code
Automation
CM tools

19. DevOps adoption trends in 2017
UNDERSTANDING DevOps
Considering
15%
No plans
6%
Never heard
6%
Just undertaken
25%
Few teams
24%
Majority of teams
14%Entire company
10%
Adopted
73%
By Statista 2018

20. C.A.L.M.S.
DevOps Values

21. CALMS is a framework of
DevOps and used as a
maturity model
THE C.A.L.M.S. FRAMEWORK for DevOps
Culture Automation Lean Measurement Sharing

22. Culture
THE C.A.L.M.S. FRAMEWORK for DevOps
DevOps is ”cross-functional collaboration”.
DevOps doesn’t solve tooling problems but solves
human problems.
DevOps isn't one team's job. It's everybody's job.

23. Culture
THE C.A.L.M.S. FRAMEWORK for DevOps
Development team invites operation team
member to join sprint.
Operations team invites developer to join sprint.
The most successful companies are on board with
DevOps culture across every department.

24. Culture
THE C.A.L.M.S. FRAMEWORK for DevOps
Good communication
• Standups
• Kanban boards
• Chatrooms or sharing space
Focus on results

25. Culture
THE C.A.L.M.S. FRAMEWORK for DevOps
Teams that practice DevOps deploy 30x more
frequently, have 60x fewer failures, and recover
160x faster.
— Puppet Labs 2016 State of DevOps Report

26. Automation
THE C.A.L.M.S. FRAMEWORK for DevOps
Investing in automation eliminates repetitive
manual work, yields repeatable processes, and
creates reliable systems.
Build, test, deploy, and provisioning automation
are typical starting points.

27. Automation
THE C.A.L.M.S. FRAMEWORK for DevOps
DevOps’ major contributions is the idea of
“configuration as code”.
Both development and operations can
incorporate new languages or technologies via
the provisioning code, and share the updates with
each other.

28. Automation
THE C.A.L.M.S. FRAMEWORK for DevOps
Knowledge management
End-to-end linking
Reliable development
Test automation
Proactive monitoring

29. Lean
THE C.A.L.M.S. FRAMEWORK for DevOps
Eliminating low-value activities and moving
quickly.
Continuous improvement and embracing failure.

30. Lean
THE C.A.L.M.S. FRAMEWORK for DevOps
Eliminate waste
Driven by customer demand
Continuous improvement
• Small iterations
Failure is normal

31. Measurement
THE C.A.L.M.S. FRAMEWORK for DevOps
If you can’t measure it, you can’t manage it.
If you can’t measure it, you can’t improve it.
Measure everything – people, process and
technology performance.

32. Measurement
THE C.A.L.M.S. FRAMEWORK for DevOps
How long did it take to go from development to
deployment?
How often do recurring bugs or failures happen?
How long does it take to recover after a system
failure?
How many people are using your product right
now?
How many users did you gain / lose this week?

33. Measurement
THE C.A.L.M.S. FRAMEWORK for DevOps
Measure is more powerful when shared with
other teams – especially teams in other
departments.

34. Sharing
THE C.A.L.M.S. FRAMEWORK for DevOps
Sharing is the Feedback loop in the CALMS cycle.
The long-standing friction between development
and operation teams is due to a lack of common
ground.
Developers and operators pair with each other in
each phase of the application’s lifecycle.

35. Sharing
THE C.A.L.M.S. FRAMEWORK for DevOps
What to share:
Goal, Process, Views, Priorities, Workflow,
Knowledge
Codebase, Ownership, Toolsets, Learnings,
Success
And all the information of development and Ops.

36. Sharing
THE C.A.L.M.S. FRAMEWORK for DevOps
Creating a culture where people share ideas and
problems is critical not only because it enables
improved communication and collaboration but
also because it helps organizations to improve.
Positive feedback from peers motivates us as
much as our paychecks and career ambitions.

37. Keep C.A.L.M.S.
Through Atlassian Solution

38. KEEP C.A.L.M.S.
CALMS Atlassian Solution Support
Culture
Confluence, Jira, Service Desk, Stride/Hipchat,
Bamboo, Bitbucket
Automation Jira, Bamboo, Service Desk, Hipchat
Lean Confluence, Jira, Service Desk, Bamboo
Measure
Confluence, Jira, Service Desk, Bamboo,
Bitbucket
Sharing
Confluence, Jira, Service Desk, Stride/Hipchat,
Bamboo, Bitbucket

39. KEEP C.A.L.M.S.

40. TIPS – DevOps MATURITY SELF CHECKING
DevOps Maturity Self Checking
https://www.atlassian.com/devops/maturity-
model

41. TIPS – DevOps MATURITY SELF CHECKING

42. TIPS – DevOps MATURITY SELF CHECKING