Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Talk [clear filter]
Thursday, February 22

9:30am EST

100% Visibility
Monitoring systems has traditionally been the responsibility of Ops teams. But if our goal is to align devs, ops, and other roles in the organization, then we need to ensure they are all monitoring critical business systems and do so in a way that takes advantage of the unique perspective that each role offers.
In this session, I’ll break down the expansive monitoring landscape into 5 categories that each provide a unique view of your systems. I’ll show how each category allows your team to have complete observability, avoid blind spots, and work together to quickly resolve performance issues and avoid outages.


Thursday February 22, 2018 9:30am - 10:00am EST

10:00am EST

Everything Is A Product - How To Apply Product Management Practices to Technology Services
As we continue to work on improving our technology processes, there is much we can learn from the discipline of product management. I believe that by applying the techniques and approach of treating your infrastructure and service offerings as products, we can provide a more delightful experience and continuously improve.
Using principles and concepts from people like Marty Kagan and other experts in the product space, I will demonstrate applicable examples of applying the concepts of feedback, planning, and interative improvement to practices including software delivery process, service desk response, and infrastructure as code.


Matt Stratton

Matt Stratton is a DevOps Evangelist at PagerDuty, where he help dev and ops teams advance the practice of their craft and become more operationally mature. He collaborates with PagerDuty customers and industry thought leaders in the broader devops community, and his license plate... Read More →

Thursday February 22, 2018 10:00am - 10:30am EST

10:50am EST

Promoting Microservice Architecture Through Docker at Capital One
Docker has enabled our teams at Capital One to deploy faster, better, and more modular software, but the technical limitations of Docker also had a surprising effect - it forced teams to break down their monolithic, stateful applications and ultimately improved our organization’s architecture as a whole. Come explore with us as we talk about exactly how this happened and how tools can be a changing force in architecture.


Daniel Esponda

I am a Principal Software Engineer dedicated to creating the high-level software and system architecture of the Consumer Identity Organization within Capital One. I have spent the past 3 years moving various large enterprises from legacy on-premise servers to public cloud environments... Read More →

Thursday February 22, 2018 10:50am - 11:20am EST

11:20am EST

Change Management for Humans
Unfortunately, rolling out changes for humans is not as easy as merging a pull request. How many times have you seen a new project management tool get rolled out, sometimes with much fanfare and polish, and just not get adopted? Have you ever seen your company announce a new business unit which led to a minor revolt? How scary is the word “reorganization”? If you have ideas on how your group’s processes could be better, want to launch a new tool that will work better as your company grows, or have to adjust the way you do things to meet new regulations, learning the basics of change management will help you to get your plans going, launch them effectively, and ensure they stick around.
I’ve helped implement several tools, projects, and process changes over the years. In this talk, I’ll walk you through the basics of organizational change management with specific examples about * Why it’s so hard (Newton’s first law of motion; nobody likes surprises) * Points to consider while implementing (Am I sure I’ve identified all of the stakeholders? What do I do if I can’t satisfy all of their wants?) * Tactics to increase adoption (If you haven’t created evangelists, you’re probably creating enemies) * Keeping the change alive once launched (Can I keep showing improvements? Do I have materials that help newcomers?) * Pitfalls to avoid (Do you really have executive buy-in?)


Tiffany Longworth

Tiffany Longworth is a Site Reliability Engineer at Puppet. She has launched successful projects large and small, but has also worked on projects that were spectacular failures! She likes using her background as a Marine, her training as an English teacher, automation, and cat gifs... Read More →

Thursday February 22, 2018 11:20am - 11:50am EST

3:20pm EST

DevOps Comes to the Database
Databases are special because they’re stateful, and DevOps reflects this: in practice, databases are a lot harder to “DevOps” (as a verb) than other parts of the stack. It’s easy to “DevOps the infra” and “DevOps the web frontend” and so on, because you can just use a declarative tool to make it be the way it should be, and if one of them goes belly up you just kill and replace it. But you can’t do that with the database, and what often happens is orgs get really open-minded about EVERYTHING BUT THE FREAKING DATABASE.
And who suffers? One person often becomes the special database gatekeeper, like Gandalf saying “you shall not pass!” and they suffer. But you know who else suffers? Every developer who now has to coordinate with, get review from, and get permission from the database gatekeeper. Their productivity also suffers.
There’s a better way. It requires cultural support, it requires tooling (like most of DevOps, although it’s not about tools you can’t actually DO it without tools), and it requires a bit of courage. You CAN build tools and processes that help you move faster and be more agile even when – especially when – very large, heavily loaded, mission critical databases are involved. This talk is about how I’ve done it and how my customers have done it.


Thursday February 22, 2018 3:20pm - 3:50pm EST
Friday, February 23

9:30am EST

A DevOps Practitioner's Guide to Kubernetes
An introductory presentation on Kubernetes focussed on the relevant interests and concerns of curious DevOps practitioners. The talk starts with an overview of the components that make up Kubernetes and how they work together to form a platform for scheduling and scaling containers. I will then talk through the various resources that Kubernetes make available to the user and how they can be composed together to deploy scalable and robust applications, not only for “cloud native” app but also for existing apps, even the dread legacy apps. I’ll also talk about how it fits in with the existing ecosystem of tools and practices that you’re likely already be using. You’ll leave this talk with a solid understanding of the fundamentals of Kubernetes, how it could fit into your DevOps toolchest, and sense of whether you should use it or not.


Paul Czarkowski

Paul Czarkowski is a recovering Systems Administrator who has run infrastructure for longer than he cares to admit. After cutting his teeth in the ISP and Gaming industries Paul changed his focus to using (and contributing to) Open Source Software to improve the Operability of complex... Read More →

Friday February 23, 2018 9:30am - 10:00am EST

10:00am EST

The Rise of Culture - Taking Your DevOps To The Next Level
Banks are the perfect storm of DevOps anti-patterns where Technical, Organizational and Cultural barriers are all stacked against you.
Cultural sprawl is huge. You don’t have to unlock and influence just one culture; you will encounter a half dozen. As an example, the top 4 banks (Wells Fargo, JP Morgan, Citi, & Bank of America) were 35 separate companies in 1990. They are an average of 175 years old.
In most organizations of almost any size, there are challenges with compliance, tech sprawl, obsolete technologies, and bloated processes. The delivery chain is often split among 3-4 organizations. Culturally, there is fear of change, group overlap and protectionism.
It sounds hopeless, right?
Through long, painful journeys, we learned principles and techniques you can use to weather your storms. These techniques evolved over 10 years in transformations which crossed 3 banks and 4 distinct large-scale transformations. Each transformation was unique, but the principles were universal. They apply to organizations of all sizes, ages and industries.
This talk will detail the principles of how we navigated and influenced cultures of organizations to achieve massively scaled DevOps transformations. We’ll talk about the importance of Leadership and why it is necessary to transcend the cultural challenges in any size organization. Leaders must be willing to go against the grain every day while providing vision, inspiration and protection. We’ll touch on Servant Leadership, Transformational Leadership, Fear of Change, Motivation and Trust.
We’ll explain the “Why” of those principles. From there, we’ll go down a path of applying those principles to actions you can take immediately to begin creating collaborative DevOps cultures.
We’ll discuss how to grow a coalition, anchor behavior, and defend your efforts from those threatened by them. The techniques help incubate your transformation until there is enough critical mass to make it tough to derail.
The three action areas we’ll discuss to help you successfully scale DevOps are: Alliances, Data, & Startup Mentality.
1)Alliances: We’ll discuss how to identify, create and leverage alliances. We’ll show how this helps bypass resistance, plot your strategy and keep your assembly line of on-boards moving.
2)Data: We’ll show how to use data to prove success, communicate weekly, and keep your execs asking for more.
3)Startup Mentality: This keeps your team focused and passionate. I told my teams: “Pretend you are a small company inside a big one. Every day measure our contribution and expect to fold if you don’t deliver.” Acting like a startup means being hungry every day, delivering in increments, focusing on just a couple efforts at a time (80/20), and pivoted rapidly. Deliver small, consistent wins to build a track record and credibility and trust. Focus on customers and their experience.
We struggled, slipped and hit brick walls, but one thing kept us going. Every member of our team believed that what we were doing was the most important thing in the world to our companies. This gave us the courage to keep pushing.
Was it worth it? Yes, every minute of it. We ultimately automated over 800 applications at Bank of America. It can be done in any organization.


Chris Nowak

Chris has 20+ years of experience in Change Management, SDLC & DevOps. He was Head of DevOps Services at 2 of the top 4 US banks. He designed, led and scaled services from the ground up, including service strategy, process optimization, organizational change, large-scale engagement... Read More →

Friday February 23, 2018 10:00am - 10:30am EST

10:50am EST

Rethinking enterprise architecture, escaping the condemnation of DevOps, cloud native, and agile
Beyond the microservices gordian knot nonsense
Current application theory says that all responsibility for software should be pushed down to the actual DevOps-style team writing, delivering, and running the software. This leaves Enterprise Architect role in the dust, seamingly killing it off. In addition to this being disquieting to EAs out there who have steep mortgage payments and other expensive hobbies, it seems to drop out the original benefits of enterprise architecture, namely oversight of all IT-related activities to make sure things both don’t go wrong (e.g., with spending, poor tech choices, problematic integration, etc.) and that things, rather, go right.
I’ve spoken with several EA teams over the past few years about the changing nature of how EAs can help in a DevOps- and cloud-native-driven culture. I’ll share their experiences including what type of EA help is actually needed and helps organizations thrive.


Michael Coté

Michael Coté works at Pivotal on the advocate team. He’s been an industry analyst at 451 Research and RedMonk, worked in corporate strategy and M&A at Dell in software and cloud, and was a programmer for a decade before all that. He blogs and podcasts at Cote.io and is @cote in... Read More →

Friday February 23, 2018 10:50am - 11:20am EST

11:20am EST

Everything I need to know about DevOps I learned in The Marines
The military is the ultimate in command and control, making sure your every second is accounted for and every step planned. This is pretty much the opposite of a DevOps culture where sharing and accepting failure are norms… right?
Not so fast…
When I got to boot camp 30 years they made us sit cross legged on bare concrete for “classroom” sessions. Try it for more than 10 minutes some time. It hurts. It made no sense. Of course you get used to it after a few weeks.
Around the sixth week they started teaching us shooting positions. Turns out one of the most stable is sitting cross legged. Stability is important at 300 yards. Something that hurt a couple months earlier was now second nature. We had the foundation required to learn the next steps (literally).
Ready to shoot, right? Yeah, not so much. Now we got to spend a week sitting on grass and pretending to shoot before we ever saw a round of ammunition. Staging deployment anyone?
In much the same way, solid technical principles enable a DevOps culture.
If we make good automation, good test practices, good code quality, useful measurement and helpful feedback loops second nature, we’re free to let our teams solve the hard problems with reduced risk. Command and control can be at the organizational level where it needs to be, with the people best suited to it (our development teams) providing the value required to support that mission.


Ken Mugrage

Ken Mugrage has more than 25 years of experience in the IT industry, spending the last 8 at ThoughtWorks. During his entire career, Ken has focused on using technology to increase business effectiveness, as opposed to using the ‘latest cool thing’. Ken has been focused on Continuous... Read More →

Friday February 23, 2018 11:20am - 11:50am EST

3:20pm EST

On Lambdaing Well
Hailed as The Future by server-smashing conference sponsors worldwide, #serverless might be an option for you, your team, or your company. But serverless – whichever of its definitions you choose – isn’t easy and creates a new set of problems to solve. The AWS Lambda platform, still the most popular option for serverless apps, is one such shiny bag of problems, even as you integrate it with the broader set of AWS services. Documentation provides some advice but its toolbox approach leaves a lot out: which tools should you use for which cases, and how do you make managing it sane? We’ll talk about when you should use Lambda (maybe not as often as you’ve been lead to believe!), how you should organize projects that use it, which tools for it are worth using, and problems to know about as you scale a Lambda infrastructure or attempt to troubleshoot one.
And, I hope, we’ll all leave with the same wistful sense that Amazon’s API Gateway could be so much simpler.


Thomas Hopkins

Thomas is a software engineer and semi-professional ranter with side bets in anthropology and music. He enjoys programming, teaching, and the intersection of culture and technology.

Friday February 23, 2018 3:20pm - 3:50pm EST