1. DevOps Projects, assignments, lifecycle management, configuration
Maintenance & support, Server operations
DevOps
Release management and quality assurance

2. Why remove "grey zone" between development and operations
foster collaboration between development teams, quality assurance function and operations staff

3. Jez Humble
"The DevOps movement addresses the dysfunction that results from organizations composed of functional silos. Thus, creating another functional silo that sits between dev and ops is clearly a poor (and ironic) way to try and solve these problems. DevOps proposes instead strategies to create better collaboration between functional silos, or doing away with the functional silos altogether and creating cross-functional teams (or some combination of these approaches)."

4. How cross-functional team
team members virtually participate in development process with having responsibility for releases and configuration management
"owns" tools & infrastructure used in delivery and deployment process, including automation of deployments & releases

5. How
ensures communications with Server Operations regarding hardware related items
performs health-checks and monitoring of applications in environments
is primary entity receiving incidents from ICC and automated alarms

6. 10 Deploys per Day Dev & Ops cooperation at Flickr: http://www

7. Conclusions?

8. Traps for DevOps implementation in Enterprise
Lack of clear vision on outcomes
Lack of a transformation roadmap
Underestimating the scale of change and thinking of it only as a tooling or procedural change
Lack of management empathy

9. Traps for DevOps implementation in Enterprise
Lack of baseline measurement, clear definitions of done
customer satisfaction, cycle time, maybe, cost of delay
Rigid process framework
Operations-change management
Lack of agile and lean education for both leadership and staff

10. Implementation readiness
Prepare (for change in infrastructure operations, for restructuring, for removal of excessive approval gates, for culture change)
Invest (automation tools, communities, technical skills)
Start

11. Implementation Start with a team that wants to embrace change
Make developers and infrastructure talk the same language through tools
Bring in code-quality profiling and test automation
Make work visible through teams
Reduce batch size
Optimize teams based on value streams

12. Introducing DevOps to the Traditional Enterprise: http://www. infoq

13. How 'DevOps' is Killing the Developer

14. Many Hats
Due to constrained resources, the developer is forced to take on the role of DBA and fix the issue herself

15. The Totem Pole
Developers' job requires them to know much of the domain of "lower" roles
It doesn't work in the opposite direction

16. Jack of All Trades, Master of None
Forcing developers to take on additional roles traditionally performed by specialists means that they:
aren't spending their time developing
need to keep up with an enormous domain of knowledge
are going to burn out

17. Don't Kill a Developer
Not every company is a start-up. Let developers write code!
How DevOps is killing a Developer:

18. How DevOps is killing a Developer: http://jeffknupp

19. DevOps Tools Continuous integration: Provisioning: Coordination (–?)
CruiseControl
TeamCity
Provisioning:
Chef
Puppet
Octopus
Coordination (–?)
ZooKeeper
Salt, Ansible, Vagrant, Docker –– ?