This document discusses DevOps from a practitioner's perspective. It argues that DevOps is often viewed tactically by technology teams rather than strategically by the business. True DevOps prioritizes customer experience and sees infrastructure as the delivery vehicle for that experience. The document advocates for a continuous delivery mindset of proactively seeking issues, enhancing based on feedback, and rapidly delivering updates based on an examine-empathize-enhance cycle.

1. Devops in reality
A doers’ perspective
Priyank Gupta
Sahaj Software Solutions

2. A prevalent business view of DevOps

3. Building it for 3.7 billion people
7.47 Billion - World population
4.91 Billion - Unique mobile users
3.75 Billion - Internet Users
Digital in 2017 Global Overview - Report
Internet is you primary marketplace

4. Mechanics of business
Your digital
platform is your
primary
marketplace
A well functioning delivery truck helps you keep your promise to your
customers
Customer
experience is
your
differentiator
Infrastructure is
your customer
experience
delivery truck

5. Shipping to your customers
Do you release
more than once
a week?
Are your
deployments
automated?
Is your primary
motivation for devops,
faster shipping of
business value?
Is primary medium for
customer feedback,
email and feedback
forms?
Is technology
group a primary
force behind
devops?

6. Keeping your promises and ...
Cost savings
Save cost and deploy
repeatedly/frequently.
Predictable
Release product reliably.
Minimize human error.
Compliance
Stay compliant by ensuring deviation free
standardized build & release process
Operational
awareness
Merge operational
concerns as part of
development cycle.
Operational to business

7. Be faster to market!
Tactical to
business

8. Holding the fort with DevOps

9. Customer experience is core but customer
experience delivery is ancillary

10. Not core to business. A paradigm employed
and managed by technology team

11. Primary motivation is to make operational
aspects work

12. Worth an upfront investment as may pay off
in long run!
=

13. Empowers technology team with agility to
ship business value frequently

14. Is that enough?
Unfortunately, all forts become monuments eventually, if they fail to keep up

15. Is your coffee fresh and hot?

16. Continuous delivery is a mindset not a tool
ShipEnhanceEmpathizeExamine
Proactively seek pain
points and gaps
Internalize the
learning and
formulate a solution
Build to
augment/repair
system
Deliver the
new/enhanced
experience back to
customer

17. Examine: Are you still sending customers
feedback emails?

18. The gratification work-stream
Community
requested features
and logged errors
Auto sorting based
on community
upvotes / criticality
Low effort and high
impact.
Design and
development
Gratification
delivered
Reported Midnight Morning Morning Evening

19. Empathize: Are you still doing user testing in
a room?

20. Data driven decisions with A/B testing
vs
Gut Data

21. Enhance: Are you innovating in a corner of
your office?
FEDex Week!

22. Build ephemeral features
Let’s waste some code
to gain some
perspective

23. Enhance: Are you depriving yourself of
ancillary revenue streams?

24. Explore revenue streams on the back of SLAs

25. Enhance: Are bugs causing an occasional
domino effect?

26. Do a canary release
vs
Successful canary release Canary release preventing domino effect
Release Release

27. The journey ahead

28. Embrace freshness!
Ideas are like
perishables. Associate a
shelf life to an idea,
validation and its
delivery.
30 minutes or free!

29. Delivery is part of
the product
First class concern for
the business not
technology.

30. Discovery is at the
end of an exploration
Experiment often and
seek feedback.

31. Thanks for pulling through!
@priyaaank
Sahaj Software Solutions