The word DevOps is quickly becoming the new Agile—an overused word that has lost its meaning. Cutting through the jargon, Lee Eason gets to the heart of what DevOps means, where it came from, and why it is crucial for your company to embrace it. If you want to deliver on the promise of agile—to improve quality and reduce time to market—you must understand and implement DevOps. Lee shares three mechanisms of change—enablement, mentoring, and coaching—you can use to drive the transformation, as well as key performance indicators to measure your progress along the way. Learn where the big technical roadblocks lie, why they exist in your company, and how to navigate them successfully. Finally, Lee shares key benefits you can expect with your shift to DevOps—the effect on consumers’ loyalty, developer satisfaction, systems uptime, and software quality.

1. DW3
DevOps
11/16/2016 1:30:00 PM
DevOps Is More than Dev and Ops: It’s
about Tearing Down Walls
Presented by:
Lee Eason
Ipreo
Brought to you by:
350 Corporate Way, Suite 400, Orange Park, FL 32073
888--‐268--‐8770 ·∙ 904--‐278--‐0524 - info@techwell.com - http://www.stareast.techwell.com/

2. Lee Eason
Ipreo
As the director of DevOps at Ipreo, a provider of financial services technology,
data, and analytics, Lee Eason is serious about high-performing teams. Like many
IT professionals, he started out writing software. As his career progressed and
responsibilities grew, Lee learned that success in software development doesn’t
come from taking away the team’s responsibilities for infrastructure, monitoring,
and deployment. He learned the importance of giving the team control and
accountability in those areas, and that ensuring they are simple and reliable,
leads to consistent, repeatable software development and deployment. Read
Lee’s articles on LinkedIn and follow him on Twitter @LeeJEason.

3. 11/1/2016
1
DevOps:
More than Dev and OpsMore than Dev and Ops
It’s about tearing down walls
Defining DevOps
Getting back to the roots

4. 11/1/2016
2
“If you have a DevOps
team, you’re doing it
”
team, you re doing it
wrong.
-- Lots of people on the internet
It’s not a tool, process, or team.
Adopt
a pet
Adopt
a pet
Paying
Taxes
Paying
Taxes
Good
Person!
Good
Person!
Usually
Sober
Usually
Sober

5. 11/1/2016
3
Daily
Standup
Daily
Standup
JiraJira
Agile!Agile!
Scrum
Master
Scrum
Master
“DevOps”
Team
“DevOps”
Team
JenkinsJenkins DevOps!DevOps!
GitHubGitHub

6. 11/1/2016
4
Bit of history…
 2000: .com bubble burst
 2001: Agile Manifesto created2001: Agile Manifesto created
 2003: Ben Traynor Sloss founds SRE
 New tools:
 Selenium (2004), Puppet (2005),
AWS (2006), Chef (2008)
 Lean startups, tech resurgence
 Facebook, Flikr (2004), Etsy (2005);
culture changes expectations
 Patrick Debois and Andrew
Shafer form Agile Systems
Administration Group in 2008
 Put on DevOpsDays and trend
twitter with #DevOps in 2009.

7. 11/1/2016
5
DevOps is a reaction against the friction of separated roles
Just as Agile was a reaction against the friction of Waterfall project management
DevOps allows Agile to deliver on its promises.
- Rapid iteration (2,555x faster lead time), increased quality (3x lower failure rate)
-- Puppet State of DevOps Report 2016

8. 11/1/2016
6
DevOps is enablement and empowerment
of cross functional teams
OperationsOperations
Backend
CodeSecurity
Frontend
Code
Design
Database
Driving DevOps transformation
Enablement, mentoring, and coaching

9. 11/1/2016
7
Enablement: Tooling
 Work item tracking: Traceability!
 Jira, Rally, VersionOne, TargetProcess, TFS
 Monitoring / Alerting Monitoring / Alerting
 DataDog, Splunk, App Insights, New Relic, AppDynamics, PagerDuty, OpsGenie
 Version Control System (VCS)
 GitHub, BitBucket, TFS
 Continuous Integration (Your build tool)
 Jenkins, TeamCity, CircleCI, TFS
 Package Server
Continuous Delivery
 Nexus, NPM, Artifactory, TFS
 Release/Deploy Automation
 Octopus, ElectricCloud, Travis CI, TFS
 Feature flagging
 LaunchDarkly, roll your own
CI Feature Flags
Deploy Automation
“You can have my TFS when
you pry it from my cold,
”
you pry it from my cold,
dead fingers.
That guy who passive aggressively makes every decision-- That guy who passive-aggressively makes every decision
take way too long.

10. 11/1/2016
8
“The tools we use reinforce the
behavior; the behavior
reinforces the tool Thus if you
”
reinforces the tool. Thus, if you
want to change your
behavior, change your tools.
-- Adam Jacob, CTO, Chef
Lessons from the trenches
Jira GitHubJira
 Know your stakeholders – they
aren’t always obvious
 History matters! “We’re a MSFT
shop”
 Strive for intellectual honesty –
smart people recognize
h ll
GitHub
 Strategic considerations are
important (BitBucket)
 Features on paper don’t always
work out in real life
 Emotional response matters!
shallowness

11. 11/1/2016
9
Mentoring: Individual skills
 “How To” of tools “How To” of tools
 Teach best practices, but not as
“only” practices
 Create a forum for people to
demonstrate their successes with
the tools
 Guild meetups, Sprint Demo’s
 Goal is to create community
 Slack, Water cooler conversations
Coaching: Group skills
 Group level mentoring Group level mentoring
 Piggy back on Agile coaching
 SAFe incorporates DevOps by
design
 Focus on continuous
improvement!
 Don’t be afraid to bring in outside
voices

12. 11/1/2016
10
Measuring the change
“You cannot improve what you do not measure”
-- Lee Eason
eNPS: Employee Net Promoter Score
W ld d P t t f d Would you recommend
your ORGANIZATION as
a place to work to a
friend or colleague?
 Would you recommend
your TEAM as a place to
f i
Puppet report found
high performing
teams 2.2x more
likely to recommend
their organization;
work to a friend or
colleague?
g
1.8x for teams.

13. 11/1/2016
11
Deployability
 On a scale of one to ten how confident are you that a deployment is going On a scale of one to ten, how confident are you that a deployment is going
to be successful?
 Many considerations:
 Overall quality, testing
 State of automation
 Feature thrash
 Monitoringg
 More closely linked to DevOps focused change than eNPS

14. 11/1/2016
12
MTTR: Mean Time To Recover
 How long does it take to go from
Hi h f i How long does it take to go from
a problem appearing in
production to a resolution being
deployed successfully?
 Start by being disciplined about
bug tracking.
 Define severity levels
 Use tagging and timestamps to
High performing
teams are 24x faster
than low performing
teams.
 Use tagging and timestamps to
link to deployments
 Base reports on time ranges rather
than minutes, especially early on
Lead Time
 Time it takes to go from code commit to code in production Time it takes to go from code commit to code in production
 Puppet report puts high performers at less than an hour
 Low performers take 1-6 months.
 SAFe teaches the best and easiest way to accelerate is eliminate delays;
lead time is all delay
 Committed code not in production is like retail product on a shelf – it’s
overhead.

15. 11/1/2016
13
KPI’s can be overwhelming
Need to build support
fast?
Have support but no
data?fast?
 Start with subjective
measurements and tie them to
industry research.
 Focus on building a narrative
around best practices and
continuous improvement.
data?
 Start with objective
measurements
 Establish baselines for your KPI’s
 MTTR, Quality, Deploy Frequency

16. 11/1/2016
14
Summary
E t bli h b li f D i h th h Establish baselines for
your KPI’s
 Subjective measurements
are good starting points
while you build up tooling
for objective data
 Work with leadership to
 Drive change through
Enablement, Mentoring,
and Coaching
 Build a culture that
values Continuous
Improvement
 Work with leadership to
establish a common
understanding of
DevOps
 Use your KPI’s to drive
investment decisions
Thanks!Thanks!
Reach out:
http://linkedin.com/in/leejeason
Twitter: @leejeason