2. About Me
● Technical Lead, SEEK Asia
● I was with 5 start-ups ( ServiceClicks, txn.my, aquamob,
tkt.my, CurrenSeek )
● Helped startups to design systems, build teams
● Currently helping enterprise change and adapt to Agile
and DevOps culture.
http://github.com/mazjs
Twitter : @mazharul_anwar
3. What we will be talking about today :
- What is DevOps ?
- Why DevOps ?
- How to Devops ?
12. Call it a culture, a movement, a philosophy.
In short, DevOps is a partnership between
development and operations that emphasizes
communication, collaboration, and integration.
- Atlassian
14. What DevOps is not ?
Team(s), and/or person(s)
“Doing so perpetuates the kinds of silos that DevOps aims to break down and prevents
DevOps culture and practices from spreading and being adopted by the wider
organization” - Rouan Wilsenach
30. Teams that practice DevOps deploy 30x
more frequently, have 60x fewer failures, and
recover 160x faster.
- Puppet Labs 2016 State of DevOps Repost
31. Benefits of DevOps
- Faster Delivery of features
- Improved communication and collaboration
- More time to innovate, less bug fixings
- Continuous product delivery
- Productive and happy teams
- Better career development opportunities
35. There are no simple 5 steps to get there. It is
a journey, and people can support it by
working in small batches, making their work
visible, and committing to a blameless
culture that responds to failure with learning
- Jessica DeVita
39. People
● Cultural paradigm shift
● Shared responsibility
● Cross training of skills
● Always asking : Is my application driving business
value ?
● Building quality in the development process
● Forms Autonomous Teams
44. Culture
“Even with the best tools, DevOps is just another buzzword if you don't have the right culture.” - Rouan Wilsenach
- Cross Functional Collaboration
- Product / Project Oriented team instead of functional team
- Having a common goal and plan to reach it together as a team
- Blameless Culture
- Autonomous
- Communication Driven Development
47. Measurement
- Feature usage
- MTTR
- System failures
- Application failures
- Deployments
The first step is to measure whatever can be easily measured. This is OK as far as it goes. The second step is to disregard that which
can't be easily measured or to give it an arbitrary quantitative value. This is artificial and misleading. The third step is to presume that
what can't be measured easily really isn't important. This is blindness. The fourth step is to say that what can't be easily measured really
doesn't exist. This is suicide.
— Daniel Yankelovich "Corporate Priorities: A continuing study of the new demands on business." (1972)
48. Sharing
- Sharing responsibilities, success and failures among teams
- Shared Codebase / Collaboration / Toolset among teams
- Open Information sharing; Go Open Source!
Highly improbable event with three principal characteristics: - Unpredictable , Carries a massive impact, after it happens, we realise there is a possibility of that happening which we didn’t see because of our psychological bias
Place of immortality!
Blameless - No finger pointing
Autonomous - Taking decisions
In the context of DevOps, failure is not a punishable offense.