• Sustainable Innovation - the Business Mantra for DevOps in Enterprise (Anoop Kumar Bhat)
• The Power of Personal Influence (Kimble Ngo)
• Agile: Break it down (Yue Lin Choong)
• #noprojects (Evan Leybourn)
• Crawl before you Run, Implementing DevOps (Jason Man)
• Automated Docker Image Builds with Jenkins, Packer, and Kubernetes (Oyvind Roti)

We will share our success stories and lessons learned on working toward Continuous Delivery on a public facing web application for a popular website. This will cover Infrastructure Engineering, Build and Release Engineering, End to End Auditability and Tracability, 1 Click Application Deployments, and Security from the Infrastructure to the Application Workflow.

As service providers(Telco's) begin to transform their business to embrace Virtualization & Cloud ( ie SDN & NFV) their network operations/service delivery teams needs to evolve. While Virtualization & Cloud make it easy to rapidly expand the size of infrastructure, but the habits and practices they used in the past with hardware-based infrastructure don't keep up. The Network operations teams need to adopt IT’s DevOps practices to maximize the potential benefits of the evolving software-defined infrastructure. This includes adopting new tools that enhance agility, implementing agile operational and organizational models and procedures, and in some cases adopting a new culture. The benefits of such an approach are compelling: lower costs and increased agility, including the ability to implement new services in days rather than weeks or months

In this session, we will look at how to take advantage of technologies like cloud, virtualization, and configuration automation to manage IT infrastructure using patterns, practices, and ideas that have been adopted from software development, especially Agile concepts, and brought into the Network Operations world as part of the DevOps movement. Also, we will also go through the challenges and problems created by all these new tools, and the principles and mindset changes that a team needs to make to use them effectively.

There was a company which had typical long running releases and the business was not happy. Business wanted change but IT was not sure how to deliver. Then they heard about Agile. It looked like the magic potion to all their problems.They started doing Agile but it just meant more work for the team and a chaos during the last days of the sprint. Operations was still not happy. Then they heard about another magic potion called Devops, which forced them to think about continuous delivery. I'll talk about the various tools being used in order to bring about this change and what were the challenges that they faced in this journey.The talk has two dimensions: First, The tool chain and Second, how the team was convinced to hop on this journey of continuos delivery. Let me begin by saying that both of the points are equally important and correlated because convincing a team to change is very difficult if the tool selection is not right. I'll also get into a demo of the working pipeline using this toolset.

REA Group is the parent company of one of the most popular Australian websites - realestate.com.au.

Over the past 7 years REA Group has scaled from a 30 odd IT workforce to 200 across multiple locations.

From Waterfall to Agile. From archaic to an employer of choice.

Over my 7 years at REA we have lessons which I’d love to share on

• Hiring Operations and Developers
• Getting Operations and Developers to collaborate
• Optimising teams to be more effective
• Overcoming cultural differences in a distributed team - particularly Asian and Western cultures
• How to knowledge share technical information across the entire company

Developers are trained to communicate to things with a goal in mind. When you're talking to something like, say a computer, you type in your code and it responds by giving you back what you want. Nine times out of ten, it works perfectly. Why, then, is it so difficult to do this same thing when talking to a client about a project, updating a superior on your progress, or pitching an investor your million-dollar idea? Because talking to people requires a special set of skills - namely, empathy and a little bit of storytelling. In an industry filled with brilliant minds, great ideas and mass disruption, so few of the best and brightest know how to tell their compelling story. The takeaways from this workshop will be learning how to value the listener and use vulnerability to improve your social connection.

It's 2:30 AM and you hear your phone buzz. You reach over and see an alert from PagerDuty. That new service your team has been working on for a few weeks has crashed and you don't know the first thing about debugging Clojure apps. After crawling out of bed and logging into your company's VPN you discover your co-workers have left you absolutely no documentation on what to do when "bad things happen". You sit there wondering if you'll be getting back to bed tonight.

Sound familiar? It doesn't have to be this way. On-call doesn't have to be a pit of lost productivity and stress. On-call can actually be a very rewarding experience that improves application stability, increases uptime, and avoids those dreaded 2:30 AM PagerDuty notifications. Let's start thinking about on-call for Humans.