1. Introduction to DevOps
Instructor: Sri Parthasarathy, Enterprise Agile Architect & Coach
4100 E. Third Ave, Suite 205, Foster City, CA 94404 | 650-931-1651 | www.cprime.com
The leader in training and consulting for project management and agile development

2. Who is cPrime?
Engaged for Your Project Management Success

3. Who are you?
• What is your role?
• What benefits are your seeking in implementing
DevOps?
• You utilize automated code deployment...
• Where are you in your DevOps maturity?

4. Today’s Presenter
Sri Parthasarathy is an Agile Coach and Trainer
with more than 27 of technology experience. He
started out as a developer for both business as
well as scientific applications, while always
having a passion for people and process side of
product and team development. . He spent a
number of years creating and managing the
software process that was instrumental in taking
a Silicon Valley startup to 30,000 customers. He
has a straightforward, approachable style and is
empathetic to multiple perspectives. Sri has a
CSM, CSD and Scaled Agile Framework (SAFe
SPC) certifications. He received his Bachelors
Degree in Computer Science from SUNY Buffalo.

5. Industry Transformations
• Software industry changing – more service oriented
• Applications
• Platforms
• Infrastructure
• Greater Adoptions of Lean and Agile
• Technology changes
• Growth of the cloud
 DevOps is not just for the cloud industry

6. Lean Thinking
•
•
•
•
•
•
•
•
Holistic (or “wholistic”)
Adherence to quality
Rapid feedback loops
Empowered and learning organization
Exploit variance
Eliminate waste
Make decisions as late as possible
Deliver value quickly and frequently

7. Agile – Development delivers faster
• Product development - development and test joined
• Business joined in as well.
Product Backlog
Daily
Scrum
Sprint
New
Functionality

8. Did anyone tell Ops?
Operations:
• Stability trumps change
New
Functionality
Piling Up
Product Backlog
Daily
Scrum
Sprint

9. Silos
DEV
OPS
Different
Managers
Different
Business Units
Different
Companies

10. Why Does it Matter?
CODE HAND-OFF
• Developers with no incentive to make site easier to support
operationally
• Operations who inhibit development of new functionality to keep
stability
• Resist deploying new versions/create roadblocks for implementation
to reduce risk.
• Product Stability and New Feature Delivery Suffer

11. Why Does it Matter?
CODE HAND-OFF
• Developers with no incentive to make site easier to support
operationally
• Operations who inhibit development of new functionality to keep
stability
• Resist deploying new versions/create roadblocks for implementation
to reduce risk.
• Product Stability and New Feature Delivery Suffer
Different vision, different mission – Tear down that wall!

12. Business needs
• More frequent product deployment
• Operations needs to get on the agile train
• Faster everything
•
•
•
•
Product Deployments
Testing
Development
Feedback loops
• What about stability? What about operations time?
• Enter DevOps

13. What is DevOps
• Dev + Ops
• The union of functionality and operability
• The overall application of the lean mindset across product
development and operations teams
• Developers to incorporate
 Operations functionality into the product
 Operations mindset to their work
 Perform ops work to some degree
• Operations
 To be involved early and through the development life cycle
 Treat operations as a product
– Infrastructure as code
– Support continuous processes
• Breaking down one more silo
• extending lean further across the value stream

14. DevOps is also…
• Commonly used term to describe
• The transformed operations teams
• The community of these like-minded individuals

15. Dev and Ops need to
• Automate everything they can
•
•
•
•
•
•
Deployment infrastructure
Product deployments
Testing
Integration
Development services
Development
• Risk mitigation
• Test every change immediately
• Process and react to feedback quickly

16. Transformation
• Leadership well versed in lean
• Development strategy to support continuous integration
• Deployment strategy to support lean deployment





Small queues
Minimum wait time
Technical excellence
Rapid feedback
Understand and exploit variance

17. Deployment is Core
• Deployment is no longer a contextual exercise
• Product vision needs to embody deployment concepts:
•
•
•
•
•
•
•
•
•
•
•
•
•
Lead time - time from concept to value delivery
Speed of deployment
Reduce cost/time to deliver
Reduce time/cost to test
Increase test coverage
Increase technology/environment utilization
Minimize deployment related downtime
Minimize deployment time issues (weekend long deployment marathons)
Minimize roll-backs of deployed Apps, Platforms, Infrstructure
Increase the ability to reproduce and fix defects
Minimize ‘mean-time-to-resolution’ (MTTR) of production issues
Reduce defect cycle time
Reduce challenges related to Dev and Ops collaboration

18. Product Management / Product Owners
• Roadmap for development and deployment
• Architectural vision needs to support modularity for
• Build time
• Deployment time
• Run time
• Product Owners
• Support both functionality and operability
• POs for Dev and Ops work together
• Understand that “non-functional” requests are as important as
new features
• Support overall corporate strategy and metrics

19. Release Planning and Execution
• Release Planning
• Include DevOps vision
• Agile practices for Dev and Ops
• Scrum and/or Kanban
• XP practices
• Team structures
• Imbed Ops personnel in the Dev Scrum Teams
• Source code management
• Branch as late as possible
• Keep to one stream
• Source Build and Continuous Integration

20. Technical Stuff
• Source code management
• Branch as late as possible
• Keep to one stream
• Source Build and Continuous Integration
• Automated Testing

21. Technical Stuff
• Source code management
• Branch as late as possible
• Keep to one stream
• Continuous Delivery
• Infrastructure as code
• Results based deployment decisions and time based
deployment decisions
• Automated, on-demand deployment
• Roll back, hot swap systems
• Monitoring systems
• Deployment documentation

22. Technical Stuff
• Source code management
• Branch as late as possible
• Keep to one stream
• Source Build
• Automated, on-demand build
• Accessible build
• Build infrastructure as code
• Automated Testing
• Test harness as code
• Automated, on-demand testing
• Collective ownership

23. After the webinar…
• We will send directions to collect the PDU you will
earn from attending this webinar
• We will also send a links to the recorded webinar
and presentation slides once they are posted online
For more information, visit www.cprime.com