This presentation was at a local company brownbag to dispel myths about DevOps.

1. dev-ops
@shoaibshaukatAgile Brownbag

3. development operations

4. development operations
dev-ops

5. development operations
devops

6. development operations
We know what Dev
Ops is?
A unified system to
replace so many
systems we have…
Push button
environments

7. operations
9 Months+
6 team members
Virtual Machines on
demand
But not in a state to be used
by Development teams..

8. operations
9 Months+
6 team members
Virtual Machines on
demand
But not in a state to be used
by Development teams..
FAIL

9. development operations
We know what Dev
Ops is?
We’ll use puppet?
Deployment scripts in
Ruby…
We know what Ops
want …

10. development
2 Months+
Automated deploys into
test
Production on windows
Operations want a UI

11. development
2 Months+
Automated deploys into
test
Production on windows
Operations want a UI
FAIL

12. dev-ops
Job Description
Tools
Access Rights
Product
Methodology

13. Before you begin the journey!
Why How What
One’s destination is never a place –
but a new way of seeing things.
…. Henry Miller

14. Why? ResponsivenessFrequent releases
Innovation
Customer Delight Quality
Time to Market

15. Project Outcomes (Marginal and Failed)
Standish Group Chaos Report 2015

17. Success Factors: Project Success
• Research at The Standish Group also indicates that smaller time frames,
with delivery of software components early and often, will increase the
success rate.
• Shorter time frames result in an iterative process of design, prototype,
develop, test, and deploy small elements. This process is known as
"growing" software, as opposed to the old concept of "developing"
software.
• Growing software engages the user earlier, each component has an owner
or a small set of owners, and expectations are realistically set. In addition,
each software component has a clear and precise statement and set of
objectives.
• Software components and small projects tend to be less complex.
• Making the projects simpler is a worthwhile endeavor because complexity
causes only confusion and increased cost.

18. Organisation (Inside-Out)
• Start at the top.
• Appoint Specialist Managers.
• Allocate people to divisions/teams.
• Communicate a strategy.
• Determine performance targets.
• Define the delivery process.
• Engage the customer.

19. Organisation (Outside-In)
• Start with the customer.
• Develop a strategy.
• Design initial process.
• Define process metrics.
• Structure to support processes.
• Appoint process managers.
• End at the top.
• Adapt & Improve.

21. Dev + Ops + …

22. Dev + Ops + …

23. Dev + Ops + …

24. Dev + Ops + …

25. Dev + Ops + QA + …

26. Dev + Ops + QA + Business
Biz Dev Ops
Agile Development DevOps
Customer Value Deliver
A culture and mindset to collaborate between Development
teams and Operation teams with a clear goal to achieve
business outcomes.

28. What I need to do?

29. code
Rackspace
New Relic
Splunk
Tooling …

30. Dev-Ops
A culture and mindset to collaborate between Development
teams and Operation teams in order to delight customer by
reducing time to market and continuously innovate.
DevOps integrates delivery and operations teams in order to
improve collaboration and productivity by automating
infrastructure, automating development workflows and
continuously measuring application performance.

32. Recap…
• DevOps is not a job title, method, product, tool etc.
• You do DevOps for the same reason that will force
you to do Agile.
• DevOps is the extension of Agile + Lean thinking
into Operations.
• DevOps is about extending the Agile culture and
collaboration to Operations.