DevOps Summit: Adopting DevOps 26 June, London

Published 1 May 2014

Efficient Teams • Streamlined Processes • Right Tools

Adopting a new capability requires a plan that includes people, process, and technology. Although the name DevOps suggests development- and operations-based way of working, DevOps is an enterprise capability that includes stakeholders, business owners, architecture, design, development, quality assurance (QA), operations, security, partners, and suppliers. Excluding any stakeholder will lead to incomplete implementation of DevOps.

Changes need to be made, but it is difficult to go against the usual flow and investments too are also required. But before you consider adopting new technology and methods, consider the challenges within your organization that that needs addressing. The expert practitioners and thought leaders at this DevOps Summit will give help you to develop your business case and build the foundation towards getting significant return on investment.

EFFICIENT TEAMS

DevOps culture: Collaboration and communication across stakeholders — that’s the culture of DevOps.

A DevOps culture is characterized by a high degree of collaboration across roles, focus on business instead of depart- mental objectives, trust, and high value placed on learning through experimentation.

• Standardisation for multiple Scrum + ‘DevOps’ teams with no separate Operations team
• Is DevOps just a job title?

PROCESS IN DEVOPS

• Dealing with ALM processes
• DevOps and Agile – how they align

Application lifecycle management (ALM) is a set of processes employed to manage the life of an application as it evolves from an idea (a business need) to an application that’s deployed and eventually under maintenance. Hence, looking at DevOps as an end-to-end business capability makes ALM part of the DevOps process.

• Identifying business objectives: DevOps helps you to reach your goals.
• DevOps practices
• A few specific practices that need to be include when adopting DevOps:
  • Release planning
  • Continuous integration
  • Continuous delivery
  • Continuous testing
  • Continuous monitoring and feedback
• Where does DevOps start and finish (from a process perspective)?
• Where does ‘Operations’ sit in the ITIL model? All over the place? e.g. Service Transition?
• Is co-location of resources necessary for successful DevOps?
  

TECHNOLOGY IN DEVOPS

A common set of tools allows teams to work anywhere, and new team members need to learn only one set of tools — a process that’s efficient, cost-effective, repeatable, and scalable.

• Open source DevOps/release/orchestration tools
• Measuring technology adoption
• Measuring return on investment tools and technology
  

NEW CHALLENGES WITH DEVOPS

• Coping with the cloud
• Enabling mobile applications
• The Internet of Things

Matthew Skelton(Chair person) DevOps Summit London May 2013

Published 17 Jul 2013

DevOps Amsterdam Interviews

Published 20 Nov 2012

Conference Sponsors:

 

Media Partners: