The document discusses the principles and practices of Agile development and DevOps, emphasizing the importance of speed and innovation in delivering software. It outlines various strategies for continuous integration, automated delivery, and feature delivery, highlighting how high-performing IT organizations achieve greater productivity and reliability. Additionally, it stresses the need to reduce silos and enhance collaboration across teams to drive improvements in development and operations.

1. Yuval Yeret
AgileSparks CTO
yuval@agilesparks.com
@yuvalyeret on twitter

2. Ongoing
Production /
Done
Roadmap Agile
Development
& Testing
Release
Activities
Done Ongoing DoneOngoing
Release
Backlog /
Product
Requirements
Done
Ongoing
Deployment
Done
Agile Development
V1V2V3
Continuous
Integration

3. • How frequently are you deploying to
production?
On demand –
multiple times
a day/week
Between once a
week and once a
month
Between once a month and
once every 6 months
Less frequent than every 6 months

4. What is your Change Lead Time - How long does it take for a small
change to go all the way from start to production?
<1 hour
<1 day
<1 week
<1 month
<6 months
>6 months
DevOps
Continuous
Delivery
Elite

5. Is this your workplace?
http://www.youtube.com/watch?v=FGfplQ1FUFs

6. “There are very few secrets
out there anymore.
The only competitive
advantage becomes speed.
Organizations need to keep
embracing innovation and
new technology models.
At the end of the day, it’s
about getting from point A to
point B quicker than
everybody else.”
Rollin Ford, CIO, Wal-Mart
http://www.slideshare.net/abbielundberg/cio-dilemma

11. “I call this the IT downward
spiral”
Gene Kim
http://itrevolution.com/construction-phoenix-project-and-selling-devops-downward-spiral/

12. The IT Applications Development and
Maintenance Expectations &
Landscape
Throughput/Value
Speed
Availability/Uptime
Cost

13. Aiming to break the legacy conflict between Dev & Ops by leveraging
lean/agile thinking/practices at a wider scope than just the
development
: http://devops.com/features/devops-killed-developer-star

14. Ongoing
To Do Agile
Development
& Testing
Automated
Delivery
Auto
Deployment
Done Ongoing DoneOngoing
Agile
Planning
Done Ongoing Done
DevOps Vision
Frequent Feature Delivery
Continuous
Integration
Predictable, Repeatable,
Non-Event
Production

15. Ongoing
To Do Agile
Development
& Testing
Automated
Delivery
Auto
Deployment
Done Ongoing DoneOngoing
Agile
Planning
Done Ongoing Done
DevOps Vision
Frequent Feature Delivery
Continuous Deployment
as part of development cycle
Predictable, Repeatable,
Non-Event
Production
The real

16. DevOps origins - WebOps

17. As of 2014 - Enterprises are going DevOps
as well...
*As reported by various DevOps tools/services vendors we are working with
Oct 21-23, 2014, SF
http://devopsenterprise.io

19. Firms with high-performing IT
orgs are winning
more likely to
exceed
profitability,
market share
& productivity
goals
Puppet Labs Webinar 2014 State of DevOps
2x higher market
capitalization
growth over 3
years*
50%

20. High-performing IT Orgs are
More Agile
Puppet Labs Webinar 2014 State of DevOps
30x 8,000x
more frequent
deployments
faster lead times
than their peers

21. High-performing IT Orgs are
More Reliable
Puppet Labs Webinar 2014 State of DevOps
2x 12x
the change
success rate
faster mean time to
recover (MTTR)

22. But when the
typical Enterprise
meets DevOps…
See Kent Beck’s idea as described by Markus Gartner at http://www.shino.de/2010/11/04/software-g-forces-the-effects-of-acceleration/

25. Ongoing
To Do Agile
Development
& Testing
Delivery
Deployment
Done Ongoing DoneOngoing
Agile
Planning
Done Ongoing Done
Use Kanban to work towards Biz-Dev-Test-Ops Flow
More Frequent Feature Delivery
Continuous
Integration
Production

26. Agile Team board & flow
DevOps E2E board & flow

27. Accelerate Time to Market &
Improve Productivity
Taiichi Ohno
Toyota

29. http://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/

30. Ongoing
To Do Agile
Development
& Testing
Delivery
Deployment
Done Ongoing DoneOngoing
Agile
Planning
Done Ongoing Done
DevOps != Continuous Deployment
More Frequent Feature Delivery
Continuous
Integration
Production
Continuous Deployment/Delivery will bring any
organization a lot of benefits…
but
there is a lot of value to be gained by DevOps
mindset/practices/tools even without going all the way

31. DevopsTools
Traditional
Processes
Ideal Batch
W/O
DevOps Investment
Reduce Batch Size
Further
WITH
Great automation and
leaner processes
DevOps != Continuous Deployment

32. http://clogeny.com/technology/devops-and-automation

33. Key Measurement – Work in Progress –
35
WIP
WIP
Stabilize
Reduce

35. Ongoing
To Do Agile
Development
& Testing
Delivery
Deployment
Done Ongoing DoneOngoing
Agile
Planning
Done Ongoing Done
Dealing with the Silos structure effect on people’s actions
Production

36. Try Feature/Service/Product
oriented
BizDevTestOps Teams

38. See Kent Beck’s idea as described by Markus Gartner at http://www.shino.de/2010/11/04/software-g-forces-the-effects-of-acceleration/
Leverage the friction/pain to drive/focus
improvement efforts

39. Assess your DevOps Maturity and
take the next steps
https://www.ibmdw.net/urbancode/docs/continuous-delivery-maturity-model/
*AgileSparks DevOps Readiness Model – Early Draft – Oded Tamir – ask him to show it to you today…

41. Across
4. deploy to production more
frequently than you can shoot a photo
on your phone. and have been doing it
for many years now.
6. Father of Extreme Programming
and now a distinguished software
engineer at Facebook.
8. only slightly less trendy than
"Mobile"
12. security tool where Gene Kim was
CTO
13. without it continuous is very hard
14. Salesforce is one of the first
companies to drive this trend
15. care mainly about delivering value
to production
17. The Don of Product Development
Flow
19. the bird that rose from ashes and
a great DevOps book
Down
1. used to store grain as well people in
functional organizations
2. one of the main reasons we need to
iterate
3. we like to get it early and often
5. the tool that used to be called Hudson.
7. Integration, Delivery, everything.
8. master of the kitchen as well as turns
infrastructure into simple code
9. care mainly about uptime and availability
10. indication of availability
11. release should be routine, not this
16. Build, Measure,
18. not just a video streaming service but
also one of the great DevOps companies out
there
The
DevOps
Puzzle
http://www.agilesparks.com/services/devops