Practices of DevOps Track
Chris Brown Track Chair |
|
DevOps is a cultural and professional movement that grew directly from the collective experience of practitioners. It is a reaction to the rise of online consumption and of customers’ expectations of increasing pace of development and delivery. IT, once a tool of back office efficiency, has become the front office. Devops integrates development and operations for safe, measurable and continuous delivery of business value.
We will have practitioners sharing how they are adopting practices like continuous deployment, production instrumentation, and telemetry to deliver higher-quality, more valuable software into users’ hands more quickly – whether those users are in the cloud or serviced with a hybrid cloud / enterprise infrastructure. |
|
Breakout Sessions
Mike Brittain Director of Engineering Etsy |
|
Advanced Topics in Continuous Deployment
|
|
Sebastian Holst EVP & Chief Strategy Officer PreEmptive |
|
Application Analytics: What Every Application Stakeholder Should Know
Accurate, timely, and relevant application usage analysis is a “no brainer” for any team committed to agile feedback driven design and development principles, but knowing what telemetry is actionable and actually delivering that data safely and efficiently to the right application stakeholders has been, more often than not, considered to be too difficult, risky, or expensive to implement. This session will use specific examples and demonstrations to quantify the value of application analytics and demystify the steps required to implement an effective application analytics implementation. The session will:
|
|
Rob Cummings Infrastructure Engineering Nordstrom |
|
Bootstrapping Continuous Delivery in the Enterprise
|
|
John Esser Director of Engineering Productivity Ancestry.com |
|
Continuous Delivery at Scale
|
|
Mahendra Pingale Senior Product Manager IBM DevOps |
|
DevOps: It’s More Than Just Getting Code into Production
But let’s think about the tools we give our practitioners:
During this talk, our speaker will talk about the collaboration challenges in software development and delivery teams, and how to address them with an emerging discipline called “Software Lifecycle Integration.” This discipline recognizes the diversity of tools and practitioners in the software development and deployment lifecycle, and seeks to improve the connection and collaboration among them. He will talk specifically about three collaboration/integration patterns and how to implement them. |
|
Richard Seroter Senior Product Manager CenturyLink Cloud |
|
How Any Organization Can Transition to DevOps – 10 Practical Strategies Gleaned from a Cloud Startup
|
|
Ed Blankenship Product Marketing Manager Microsoft |
|
Make Data-Driven, High-Impact Improvements to your Applications
|
|
Bernard Golden Author |
|
The New Cloud Application Design Paradigm
Specific topics addressed include:
|
|
Kevin Hancock Senior Director Worldwide Field Operations Collabnet |
|
A Practical Path: From Agile Teams to DevOps in the Cloud
|
|
Matt Ray Cloud Integration Lead Chef |
|
Principles for Navigating the Future Today
|
|
Claude Remillard Group Program Manager Microsoft |
|
Release Management Practices for the Enterprise
|
|
Lightning Sessions
Steve Neely R&D Engineer Rally Software |
|
Continuous delivery? Easy! Just change everything. (Well, maybe it isn’t that easy.) Continuous Delivery is a hot topic in both the engineering and business worlds. Adopting Continuous Delivery radically changes the cadence and fundamental processes involved in building and shipping software.This talk focuses on lessons learned by Rally Software as we transitioned from delivering releases every 8-weeks (with Scrum teams), to delivering on-demand with a continuous workflow model (Kanban). The presentation details struggles with build systems, test systems, customer enablement, and internal communication, and speaks to the light at the end of the tunnel -- greater control and flexibility over feature releases, incremental delivery of value, significantly lower risk, and much more. Don’t miss the chance to learn from our successes and mistakes, and get your teams deploying more frequently. As we focus on both business (product management) and engineering perspectives, this session will explain how to automate and manage simultaneous software release cycles while minimizing unnecessary risks. |
|
Sean Kennedy OSLC Community Development Leader IBM Rational |
|
Facilitating Stockdale: Confronting and Overcoming the Brutal Facts of Continuous Improvement To paraphrase, the "Stockdale Paradox" is: To have unwavering faith that you will prevail in the end, while AT THE SAME TIME, confronting the most brutal facts of your current reality. For product delivery organizations, the Stockdale Paradox can be a simple motto to help focus its energies in the face of aggressive competition, changing customer desires, challenging business climates, and more. For an Agile or Lean product delivery organization, it is also a reminder of the need for true, lifecycle-wide, continuous improvement. No matter how "brutal the facts of your current reality", however, sometimes there is nothing more brutal than trying to implement improvement in an established process - especially one (paradoxically?) that has recently been adopted as part of an "agile transformation" or "lean revolution". In this presentation we'll consider how the Stockdale Paradox applies to Agile and Lean product delivery organizations in general, and to their discipline of continuous improvement specifically. We'll take a look at some common barriers and reflect on some of the necessary characteristics for sustainable continuous improvement. |
|
Jose Luis Soria ALM Team Lead PlainConcepts |
|
Patterns and anti-patterns for (Continuous) Delivery: proven tips to improve the way you release software Successfully delivering software means much more than only coding or even testing. As Mary Poppendieck says, "How long would it take your organization to deploy a change that involves just one single line of code? Do you do this on a repeatable, reliable basis?" People have been worried about how to dramatically improve the way they code and test their applications, but it has not been until the popularization of movements such as Continuous Delivery or DevOps when they have begun to pay attention to the way they release. The way your team releases software is getting more and more important, even making the difference between a failed and a successful project. And it is getting to represent a key factor to help differentiate an organization from its competitors.This session covers useful patterns and practices to improve the way you deploy, release and deliver software, as well as some pitfalls to be avoided, both in Continuous Delivery environments as well as for more traditional release processes. It is not targeted to any specific technology or platform, since it is based on general principles that can be applied no matter the language or technology stack you use, although most of the guidance covered through the session is gathered from the book the presenter has co-authored about the subject, Building a Release Pipeline with Team Foundation Server 2012. Some of the key topics being covered are: tips for orchestrating a deployment pipeline, practices for deployment and test automation, configuration management for release artifacts, getting actionable feedback and metrics about your release process, and advanced release techniques. |
|
David Atkinson Red-Gate |
|
Automating database deployments in an agile world (From Wednesday BOF) Everyone is comfortable automating application deployments, but having immense difficulty with the database... |
|