2. Who am I?
Murughan
Heading DevOps @Euromonitor
Website/Blog
https://elevate-org.com/
LinkedIn
https://in.linkedin.com/in/murughan
Twitter
@Murughan_P
3. What is DevOps?
DevOps is a cultural and professional movement.
Adam Jacob (Founder of Chef)
DevOps Goal is to build a Culture which Increases the flow of work,
enable fast feedback and fast forward loops, and Continuous
Improvements – Gene Kim
5. 1. Culture
DevOps is a Cultural paradigm shift, it’s a group of people with a common set
of values and beliefs. Culture is the set of shared attitudes, values, goals, and
practices that characterize an institution or organization.
• Empowering team members.
• Team members with shared responsibility and everyone is accountable.
• Teams are cross-functional.
• Shared pain and shared success.
• Teamwork is a huge part of the cultural aspect of what it really means to be doing
DevOps.
• Autonomous teams.
• The culture of learning and sharing.
6. 2. Communication & Collaboration
collaboration is critical, right? Constant collaboration and involvement of
teams across all aspects from designing through monitoring of the
application.
• Making our work visible to everyone who plays role in delivery. Any given point of
time team members has up-to-date information about work progress. tools like JIRA
or TFS is useful.
• This eliminates surprises, waiting waste and bottlenecks.
• Enables quick response and time to market.
• Rapid communication & discussion rooms with slack.
• Knowledge repository with Wiki and Sharepoint.
• Real-time chat with Slack.
• Monitoring and alerts for fast feedback.
7. 3. Trust
Trust is a big aspect, you can’t be successful if you can’t trust other parts
of an organization. When we’re surrounded by people who believe what
we believe, something remarkable happens… trust emerges.
• Team members need to build Trust with IT team themselves and some of the
other parts of business.
• The trust will make the relationship stronger across an organization and
increases the quality of work.
8. 4. Decreasing silos
Many organizations are Functional Oriented to organize team by their
specialties. Departments like Development, QA, Database Developers,
Database Administrators, Network Administrators and so forth. We need to
change to “Functional Orientation” to eliminate Silos.
• Resolves “Wall of Confusion” between departments.
• Decreases lead time.
• Creates team members to be generalized than specialized.
• Knowledge sharing among departments and everyone is responsible for delivering.
• This eliminates saying of ”well, my part works, but they can’t get in running”.
9. 5. Fast Feedback loops
Enable constant feedback from right to left at all stages of the value
stream, This allows us to detect and remediate problems while they are
smaller, cheaper, and easier to fix, avert problems before they cause
catastrophe.
10. 6. Systems thinking
Gain a true understanding of the business system that IT operates in. W.
Edwards Deming called this ‘appreciation for the system.’. this
emphasizes the improvement of the entire system, as opposed to a
specific silo of work or department.
11. 7. LEAN
Lean manufacturing sets the standard for discipline, efficiency, and
effectiveness of an organization.
The Seven Principles of LEAN are
1. Eliminate Waste
2. Build Quality In
3. Create Knowledge
4. Defer Commitment
5. Deliver Fast
6. Respect People
7. Optimize the Whole
12. 8. Automation
Jez Humble says “Computers do repetitive tasks, people solve problems”
• Automate all the repetitive tasks.
• Automate everything!
• Release management
• Testing
• Code review & Code Analysis
• Provisioning
• Configuration management
• Systems integration
• Monitoring and control.
• Enable deployment pipeline.
• Enable continuous Integration.
• Enable continuous Delivery.
• Enable continuous Deployment.
13. 9. Measurement
John Willis says - If you can’t measure, you can’t improve. A successful
DevOps implementation will measure everything it can as often as it
can… performance metrics, process metrics, and even people metrics.
14. 10. Continuous Improvement
Create a culture of Continuous Improvement in everything we doing
with respect People, Process, Technology and Management.
• Promote learning culture.
• Improvement of daily work.
• Sharing new learning to across organization through Brown-bag sessions,
conferences, Sharepoint and Wiki for knowledge repository.
• Make all blameless post-mortem reports visible to teams trying to solve similar
problems.
15. Further Studies/Reference:
• DevOps handbook – Gene Kim, Jez Humble, Patrick Debois, & John
Willis
• Implementing Lean Software Development: From Concept to Cash –
Mary Poppendieck & Tom Poppendieck
• Introduction to DevOps: Transforming and Improving Operations –
John Willis
• Continuous Delivery – Jez Humble
• DevOps: The Big Picture - Richard Seroter