DevOps & Atlassian Deliver Fast. Deliver Reliably.

SPEAKER PERSON | SPEAKER TITLE | @SOCIALMEDIAHANDLE SOLUTION PARTNER LOGO HERE

Workshop is optional. To run the workshop you will find instructions in a separate deck called Team Playbook. Please delete from agenda if not doing it.

Don’t forget to delete this instruction.

• What do you see here? A chaotic kitchen perhaps? Too many chefs? A bunch of servers and wait staff crowding to take out finished dishes? This is actually what it’s like in the kitchen at Eleven Madison Park, New York - a 3 Michelin star restaurant and rated third in the World’s 50 Best Restaurants list. • From the time you enter the restaurant, where you are greeted by the host, to the head server who seats you at your table to the sous chef who manages assistant chefs and line cooks, to the saucier chef who works on just sauces and the many variety of professionals in the kitchen - all these different teams come together to collaborate and serve a perfect plate of food, so that you can enjoy it and give feedback right away. (CLICK for transition) • You might wonder why I’m talking about food in a DevOps presentation. There is a lot in common! Just as in a kitchen at a Michelin restaurant, in enterprise companies too you have different groups of people coming together - software, operations, QA, IT - each with his or her own area of responsibility in shipping products to customers. • The team at Eleven Madison iterates over successive versions of the dish, working together to combine their respective aspects in a way that brings harmony and beauty to the dish. • Similarly, DevOps can be a recipe for success for these two very different teams - Dev and Ops - coming together to embrace a collaborative approach, to share feedback and experiment together with new techniques and new tools. • So before I get hungry, let’s talk about why we are really here today.. Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking

• Here’s the agenda. We’ll take a look at the history of Atlassian and how we got here today • Next, we’ll address some of the bigger challenges facing the software industry today and how DevOps addresses that solution • We will then take a look at what steps you can take to adopt DevOps - for your team and your organization. We’ll spend some time understanding the need for a culture shift and finding the right tools with Atlassian • You’ll also learn how a mid-size enterprise software company adopted DevOps using the Atlassian toolset

So let’s get started.. OUR MISSION

We believe behind every great human achievement, there is a team. Our mission is to unleash the potential in every team. 8 offices 2,500+ worldwide Atlassians

• I’d like to talk a little about Atlasssian’s journey so far in building great software. • There are currently more than 2,500 Atlassian’s working in offices in Sydney (HQ), San Francisco, Austin, NYC, Amsterdam, Gdansk, Manila and Tokyo to develop, support and market their products. Atlassian has grown quite a customer franchise over time. There are more than 68,000 customers innovating in every industry, empowering their teams to do incredible things. 80%

of Fortune 100 companies

Out of our 68,000 customers, over 80% are teams at Fortune 100 companies. Here are some interesting facts: • Among those customers that trust Atlassian with their business - they include 7 of the top 10 largest banks in the world. • More than 250 out of the Fortune 500 companies are Atlassian customers. Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking

So now let’s take a look at the state of software today and some of the challenges the industry is facing Software is eatingprogramming the world.

This is software

• 6 years ago, in Wall Street Journal, investor Marc Andreesen stated ‘Software is eating the world’. An iconic statement on how software was disrupting every traditional industry at that time. • These days the idea that every company is a software company is a cliche. No matter your industry, you’re expected to be reimagining your business to make sure you’re not the next local taxi company or hotel chain caught completely off guard by your equivalent of Uber or Airbnb. • Today every software has turned into a service. It’s an always on, always up, always available world

• Today, software is programming the world according to Andreesen. There are more opportunities for software to transform everything, from homes, to businesses to cars. Every industry is now software-first

• You would probably not consider these businesses software-first, but they’re increasingly just that - using software to distinguish themselves in competitive markets. • New high-end electric cars are among the most sophisticated machines on the planet, containing 10 million or more lines of code. Ovens and coffee machines in Starbucks are updated over the internet, so that when when a new food product is introduced to the store, it will instantly be heated to the right temperature in every location, with no learning curve.

Sources: P&G: https://conferences.oreilly.com/strata/strata-ny-2016/public/schedule/detail/51978 Starbucks: http://www.geekwire.com/2016/new-starbucks-cto-technology-creating-hyper-connected-coffee-shops-personalized-customer/ Chevrolet: https://www-01.ibm.com/software/rational/announce/volt/ GE: https://www.nytimes.com/2016/08/28/technology/ge-the-124-year-old-software-start-up.html Nike: https://techcrunch.com/2016/07/06/nike-releases-open-source-software-to-play-with-the-techies/ The way software teams work has changed

• With software development moving so quickly and customers demanding constant improvements - it’s no wonder we’ve also seen changes to the way software teams work. • You see the greatest impact of this in version control and software development methodologies. In fact, it requires a huge change in mindset to build software that’s less buggy, that actually fulfills the requirements of end-users, and is released every 6 weeks versus once a year. THE NEW NORMAL

Agile & Git

overall

Teams of Teams of 77% Teams of > 150 Teams of 101-150 51-100 Teams of 10-50 report using < 10 AGILE 77% 84% 68% 79% 84%

• Speaking of changes, in the last 10 years we’ve seen Agile & Git adoption skyrocket. • In Agile, all roles on a development team come together to prioritize, scope, and support one another. And with Git, branching and merging has never been so easy. Decentralized version control systems are enabling teams to move faster than ever with higher quality. • According to the 2016 State of Software report by Atlassian, (where we surveyed 17,000 software professionals including 1,300 Atlassian customers), 77% of teams report using Agile methodologies.

Sources: 2016 State of Software report - Atlassian: http://www.netinstructions.com/the-case-for-git/ https://techbeacon.com/survey-agile-new-norm THE NEW NORMAL

Agile & Git

overall

Teams of Teams of 78% Teams of > 150 Teams of 101-150 51-100 Teams of 10-50 report using < 10 GIT 86% 83% 65% 73% 79%

• and 78% have moved to a distributed version control system like Git. This pattern is not just seen in small software teams, but across large enterprise teams as well. I’m sure most of you are also practicing these processes in various capacities. • While Agile & Git are great and have been around for a while, what lies ahead for software development and is there an opportunity to improve?

Sources: 2016 State of Software report - Atlassian: http://www.netinstructions.com/the-case-for-git/ https://techbeacon.com/survey-agile-new-norm PULSE CHECK

Do incident response times often exceed SLAs?

Is infrastructure always on fire?

Is there friction between development and operations teams?

Are releases slipping?

• Ask the audience: • Have you migrated to Agile & Git and are still dealing with these situations? • How many of you have been here before? Maybe you’ve noticed releases have been slipping? Has there been friction between dev and ops teams? Do you feel incident response times often cross SLAs? Has infrastructure often been on fire in your teams? • If you can answer ‘YES’ to any of these questions, you’ll realize that while Agile and Git are great, they don’t prevent silos and ‘walls of confusion’ from still forming. Silos are still forming

• Traditional development and operations teams tend to work in silos, limiting the amount of inter-team communication until software release times. • Such processes don’t always encourage software teams to communicate with people outside of their software bubble. • And it still doesn’t prevent ops teams from being woken at 2am to work on a problem they have no context about. • While Agile and Git are good prerequisites to a culture for DevOps, but there’s a lot more to building a culture that allows for cross-functional teams to maximize efficiency, collaborate and innovate. • Growing software enterprises must become more collaborative, else they will cease to exist. What’s next after Agile?

• The only way to break down the silos, open lines of communication, and make further gains on speed and quality is through a brand new way of working. We’re not just talking about tools here, but also best practices and a cultural shift to experiment and share information between teams.

• This is the catalyst for the movement we call DevOps. DevOps A culture where dev and ops collaborate to build a faster, more reliable release pipeline.

• For many of you here, you might be familiar with the term DevOps so let’s level set to understand what it is exactly?

• DevOps is a culture where dev & ops collaborate to build a faster, more reliable release pipeline. You’ll often see this manifest with changes to the software delivery pipeline and infrastructure. Rule of Three

Work flow Amplify feedback Continuous Visibility across groups Swarming on incidents Experimentation Culture of learning

• DevOps is underpinned by 3 principles - Gene Kim’s 3 ways (made popular by the Phoenix Project) • Flow - Make work visible across groups (i.e. Dev & Ops), limit work in progress, and reduce handoffs. Resist the urge to blindly throw work items over the fence to someone who has no context. Work as a system, not a silo. • Amplify feedback - Aim for fast feedback, catching failures before they make it downstream is imperative. Deliver quality by starting at the course. When incidents do happen, swarm across all stakeholders to resolve. • Continuous experimentation - Create a culture learning, where taking risks and learning from failure is viewed as a step forward. Daily work becomes better through constant experimentation and open mindedness. DevOps is everyone’s job

• And it takes a team, DevOps is not just one person’s job - it’s everyone’s job. • Compare this to a traditional enterprise model where dev and ops teams sit on opposite sides of the fence. • It’s a complete culture shift. A decision to be more transparent, understanding, and cooperative. You build it, you run it.

WERNER VOGELS | AMAZON CTO

• Run what you build is one result of DevOps and can be summarized in this quote here from Amazon - a leader in practicing DevOps for enterprise. • In a traditional scenario, dev teams engineer a solution and then hand it over to ops to deal with production issues. When things break, the ops team aren’t always equipped to deal with the fix and it’s a mad scramble to address the issue. • When both dev and ops teams come together to ‘run what you build’ you end up sharing responsibility, having greater transparency and accountability. • This is a great way to get dev and ops teams together on a singular vision - especially if you’ve noticed friction between these teams. • This approach helps to improve team efficiency, operational quality and results in more satisfied customers (and employees!). Teams practicing DevOps are overachieving!

22% 24x less time on faster recoveries unplanned work. from failures. 200x more frequent deployments 3x 2,555x lower change failure shorter lead rate. times.

State of DevOps Report (2016)

• What you can see here is that there is a strong correlation between teams practicing DevOps and delivering value. They spend more time on R&D than working on unplanned work or rework. • 24x faster recoveries from failure - that can be the difference between 5 9’s and 4 9’s. For those not familiar, 99.999 (often called "five 9s") refers to a desired percentage of availability of a given computer system. Such a system would probably have what some refer to as high availability.

• All of these things add up to more frequent deployments and at better quality. With each deployment there are less bugs, and a faster time to recovery from the bugs that do make it out. And guess what? As a result, infrastructure is not on fire anymore!

• These insights and more can be found in the State of DevOps report - a fantastic piece of research with insights from over 20,000 software and IT professionals with involvement from Jez Humble, Gene Kim and Nicole Forsgren. Puppet survey for 2017 is currently underway and should be available sometime this summer. Atlassian is excited to sponsor the report again this year.

• Source: 24x faster recoveries from failure - that can be the difference between 5 9’s and 4 9’s (https://www.intermedia.net/blog/2014/01/28/99-999-uptime-vs-99-9-uptime-the-difference-two-extra-nines-makes/) 30x 200x more frequent deployments more frequent deployments 2015 2016

• Compare this to past reports and it’s easy to see that teams are continuing to get added value from adopting a DevOps culture. • If you are delivering more often, that means more reliability. Limiting scope allows you to release with more confidence. In other words, releases get more frequent and predictable, which means your teams are not missing or slipping on ship dates anymore!

• And as dev and ops teams free themselves from downtime and rework, they now have a lot more time on their hands to devote to achieving greater business results..

2015 —— This year, nearly one in five respondents came from DevOps departments, compared to fewer than one in six. 4,976 respondents completed the 2015 State of DevOps Survey

2016 — — Surveyed more than 4600 technical professional, with an increase in responses from people working in DevOps departments. 10% More Engineering Time What does this mean for your teams?

• With this newfound engineering time, what does this mean for engineering teams? Feature velocity Experiment more and release with fewer bugs.

Invest in future quality Maximize automation to increase throughput and speed in dev cycles.

Competitive edge Bring new features and products to market faster.

• With this newfound engineering time, teams can now experiment more, learn from successes and and roll out results of these experiments to new markets Feature velocity Experiment more and release with fewer bugs.

Invest in future quality Maximize automation to increase throughput and speed in dev cycles.

Competitive edge Bring new features and products to market faster.

• DevOps maximizes automation of quality & testing activities, which means teams can now achieve greater speed in deploying features and this ultimately results in Feature velocity Experiment more and release with fewer bugs.

Invest in future quality Maximize automation to increase throughput and speed in dev cycles.

Competitive edge Bring new features and products to market faster.

• Faster time to market for your organization. Using the time recovered from excess rework and downtime can be used to develop new products and features or implement process improvements - giving your organization a competitive edge Up to 100 releases per day Netflix has more than 30 million streaming members

• And while companies like Netflix or Amazon are often mentioned when it comes to DevOps and some of you might want to hear how to do 100 releases per day or 50 million deployments per year. • Not everyone of you can or want to do that. What’s important to remember is that Netflix and Amazon did not get there overnight. • Which brings us to the question that I get asked most often, “Where do we begin with DevOps?” or “What’s the best way to get started” Amazon has thousands of teams and millions of users 50 million deployments per year

• Which brings us to the question that I get asked most often, “Where do we begin with DevOps?” or “What’s the best way to get started” Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking

• So now let’s learn about some of those best practices in the next section of our agenda today - Steps to DevOps. • So how do you get started? We know DevOps works for small teams and organizations, but can it work for the Enterprise? The answer is yes, and here’s how you get started with Atlassian ATLASSIAN FOR DEVOPS

Atlassian is the culture and collaboration layer of DevOps.

• Atlassian is the culture and collaboration layer of DevOps - we put teams first, providing tools and guidance to successfully implement DevOps practices. • The Atlassian stack of tools puts teams first. Our tools help foster a collaborative culture by offering complete visibility from issue to source. • Atlassian tools can speed up your releases by automating menial tasks and defining set processes. • Atlassian can help accelerate time to resolution with faster feedback loops and the ability to swarm around incidents. • And we help you prioritize when unplanned work arises • So now let’s dive in to the steps you can take to DevOps with Atlassian STEPS TO DEVOPS

Culture Practices Tools

1 2 3

• It starts with culture - a core ingredient for successful implementation of DevOps.

• Practices follow next - once you’ve established a culture that is conducive to DevOps, it is essential to have methods in place that allow collaboration to thrive.

• And finally, having the right tools at your disposal help speed up your releases by automating menial tasks and defining set processes. STEPS TO DEVOPS

Culture Practices Tools

1 2 3

Let’s now look closely at each of these steps. Building a culture of collaboration

Shared responsibility Cross pollination of teams Everyone shares in wins & failures Build empathy & understanding

Encourage transparency Effective communication Information is readily available Teams talk to one another

• Culture is the foundation on which every successful team is built. Does your culture foster experimentation and encourage transparency? Do members of your team or organization feel comfortable approaching one another with problems? Do product incidents lead to finger pointing instead of learning?

• Taking steps to build a culture suitable for DevOps is the first step. Build a sense of shared responsibility and empathy across teams. Be open and transparent and provides means to effectively communicate. Of course this will go hand in hand with other tactics, but without this everything else will become much harder.

• If you know you need to address some team dysfunction, where do you begin? www.atlassian.com/team-playbook

• One small but impactful way to initiate culture change is to run workshops that identify areas you can improve amongst your various dev & ops teams. • We do this often at Atlassian. So much so, that we decided to write the process down. Introducing: the Atlassian Team Playbook - a guide designed to help teams work better together. • Go check it out at atlassian.com/team-playbook. Its totally free to download and use. TEAM HEALTH MONITORS TEAM PLAYS

LEADERSHIP

SERVICE

PROJECT

• The Playbook consists of health monitors used to identify areas for improvement based on your team type. • For example, ‘are responsibilities evenly balanced across team members? or do all team members have a shared understanding of current projects, etc… • Once you’ve identified areas for improvement, you can move on to recommended plays for each area. For example, if you’ve uncovered that your team is constantly running into the same problems during every incident or release, it’s time to implement a retrospective, or incident post-mortem. If you don’t learn from your mistakes, your doomed to repeat them. • Running health monitors and plays can help your teams move toward a culture ready for DevOps. • Currently the Team Playbook is organized based on team type - Leaders, Project, & Service. For DevOps specifically, you’ll want to run plays for both the Project & Service teams. • We’re currently working on building a DevOps specific grouping of monitors & plays - so stay tuned for that. • Optional for Solution Partner: To help get you started today, we’re doing a short breakout session at the end of this session on a health monitor for service teams. [Solution Partner can choose to do a Project or Leadership team health monitor workshop as well. Choose what is primary to the role of your audience.] STEPS TO DEVOPS

Culture Practices Tools

1 2 3

• Let’s move on to the next essential step in DevOps - Practices Practices

Continuous Agile DVCS Integration

• Add a little context on ‘practice’ • Alright, once you’ve started establishing a culture suitable for DevOps it’s time to look at some other important practices • It’s important to note, that these next recommendations will also help aide in your culture shift. • These things won’t happen one after another - it’s definitely a concurrent effort. So you might start with distributed version control (DVCS) and then agile, followed by continuous integration. Any of these changes will help in bringing a cultural shift to your dev and ops teams. • Let’s take a closer look at each of them AGILE

Supports culture shift

Quick reaction to change What is Agile?

atlassian.com/agile

• Are you Agile? You can’t be agile without DevOps and you can’t do DevOps without Agile. • How are your agile processes working for you? DevOps processes can only be achieved once you’ve mastered working in an Agile way. • If you think there are areas to improve, the the Team Playbook can help. • We’ve also pulled together Agile best practices and guides on our Agile microsite - https://www.atlassian.com/agile. GIT

Quick iterations

Branching & merging

atlassian.com/git

• Have you migrated or started using a distributed version control system, such as Git? If not, that’s okay - don’t freak out. • You can still move towards DevOps without this, but it’ll be much harder. • DVCS is all about quick iterations and lots of branching and merging - all things you’re going to need in a lean DevOps environment. • We can provide guidance here as well, check out our Git microsite at atlassian.com/git. • The Git microsite has helped over 1,000,000 people thus far, definitely check it out if you need some guidance. CI / CD

Fast feedback

Automation

atlassian.com/ continuous-delivery

• Lastly, but certainly not the least, is continuous integration and continuous delivery. • In DevOps, automation and deploying often is the goal - the basis of which is a sound continuous integration pipeline. Is it common practice to write tests during new development? Are you living and breathing by a red/green build wallboard? Getting your build infrastructure and process nailed down is absolutely something to strive for. How do you begin? • Automation is critical to DevOps, and there are a bunch of tools out there that do autmation. At some point, there are some tasks that need to be done by humans and JIRA tickets are that translation between machines and the people that do the work. • Well, we have some help for you here too at our continuous delivery microsite. https://www.atlassian.com/continuous-delivery STEPS TO DEVOPS

Culture Practices Tools

1 2 3

• Okay, that’s a lot. But Agile, Git, CI/CD, and a team playbook is getting you only partly there. What are you supposed to do now and how can you make the transition to all of these things easier? The answer is tooling. Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking D R N N E E N P A O A IO L I L T O L T P A Y - R T A C G E I C O T M I N N T I E N I N C U U O M O

U M

M S

M O F

E U

C E

D N

E B

A I

C

M S

I U C

K A

T O

-

U T

L E

B N I

I T O

A U T A N

E IL N R R D O E C OP

• At Atlassian we see DevOps as a complete software development lifecycle. Each phase flowing into the other, breaking through silos and informing key stakeholders along the way.

• PLAN • Confluence is a terrific product to collect and organize customer feedback and list requirements or user stories. You can then export these into JIRA Software issues in one click and start tracking the progress of your stories and epics in your software project.

• BUILD • Using JIRA Software you can create branches in Bitbucket for each feature that you need to create and when developers create a pull request or code review to flag code for the team’s attention in Bitbucket, it automatically updates the related JIRA Software issue’s status

• With CONTINUOUS INTEGRATION, you can tie automated builds, tests and deployments together. Prevent "it works on my machine mentality" and DEPLOY faster, thanks to continuous delivery with Bamboo and its AWS CodeDeploy and Docker capabilities. Also you can get full visibility on branches, builds, pull requests and deployment warnings in JIRA Software Release Hub.

• OPERATE • Once you’ve deployed your code into production, you can track and resolve incidents faster with JIRA Service Desk. You also have complete traceability from JIRA Service Desk changes and incidents to JIRA Software tickets. Finally you can manage your runbooks, knowledge base articles and any related documentation in Confluence.

• With JIRA Service Desk requests, you can provide CONTINUOUS FEEDBACK to your software teams

• And at every step your teams can use HipChat to collaborate in real-time, swarm on incidents wherever they are - via desktop, mobile and wearable apps.

• It’s important to note that Atlassian products can get you most of the way there, I’d say 70%, but there’s also a wide range of other tools that will land somewhere along the infinity loop. Things like Docker, Puppet, NewRelic, or Splunk. (all integrate with the Atlassian Stack). A DevOps Story

• Now let’s understand the full DevOps approach using the Atlassian toolset. • This demo is based off of our Bitbucket Cloud team’s workflow, but applied to a fictional DevOps team working on the Teams in Space project. • We’ll look at how the team handles an incident - in this case, their web application starts to experience some performance trouble. Ops and Dev will swarm on the issue, identify a temporary & permanent fix, then implement and release the change. • Throughout, take notice how the tools enable the team to implement DevOps practices - including open communication, automation, and visibility. An incident occurs

D

Sam Ops Engineer

• Meet Sam, our Ops engineer. He’s in charge of supported the live Teams in Space app. • Sam heads into work one morning and starts catching up on things that happened while he was out. • Shortly after his first cup of coffee, notifications start rolling in… something is wrong with the application cluster supporting the Teams in Space app. In this case, PagerDuty pings the HipChat room. Devs are notified

Sally Developer

• Sam and team quickly realize this will take some work, so he goes to log a service desk ticket to track progress. He creates the Hotfix ticket in JSD. • Once the ticket is created, it pings the Teams in Space development HipChat room. • Sally, a developer sees the ticket and hops into the related HC room to help. The HipChat mobile app can also inform developers instantly. Swarming begins

• The Ops & Dev teams are working together to find the root cause and identify a fix. • 2 things happen at once, the Ops team updates StatusPage (or they have their external monitoring system do it automatically), and they search through their knowledge base for a quick solution • The team identifies a quick fix - add another node to the cluster to support the increased usage. This will hold them over until the development team can fix the bug during their next sprint • Sam brings another node into the cluster Fix added to backlog

• Sally adds the bug fix to the backlog in JIRA Software, linking to the JIRA Service Desk ticket for traceability Incident post-mortem

• With the issue resolved and ready to go in the backlog, the team runs a retrospective or an incident post mortem • HipChat captures the timeline and teams can put this on the post-mortem report • Everyone involved in the incident is involved - that means Ops & Dev teams! Development begins

Jennifer Developer

• The development team starts their next sprint. Sally’s colleague, Jennifer, begins work on the bugfix • Using the integration between JIRA Software and Bitbucket, Jennifer creates a branch. At Atlassian and in our example, the team follows a feature branching workflow - for even the smallest item of work. Once changes are made we run builds on those branches before merging them back into the master branch • Development begins in Bitbucket, once the change is ready for review, Jennifer creates a pull request • Pull requests are a vital part of the workflow, automation through tests is a huge piece of DevOps, but so is collaboration • PRs get team members talking, share knowledge, and catch bugs that made it through your CI process • If you implement one thing out of all of this, PRs should be it • Creation of the pull request automatically transitions Jennifer’s JSW issue • The team approves her change, Bamboo builds are passing, it’s time to merge • With development complete, all the updates are available inside JIRA Software - complete visibility Release

John Release Manager

• Finally it’s time to deploy • The release manager, John, can see the status of everything in JIRA Software’s release hub • Once things are dubbed “done” , the release manager can deploy from JIRA or directly from Bamboo • The fix is now live on production Atlassian Saw… Since adopting DevOps, teams have seen some changes

• Over the past few years teams at Atlassian have been adopting the best practices I went through today. More builds* Increase in builds per month whilst keeping engineering teams about the same size.

Greater velocity Deploy changes faster with greater confidence .

More independence We can move faster, more reliably, with greater sense of ownership.

• Since adopting DevOps, Atlassian has roughly seen a 10x increase in the number of builds run per month, whilst keeping the size of the Build engineering team about the same. More builds* Increase in builds per month whilst keeping engineering teams about the same size.

Greater velocity Deploy changes faster with greater confidence .

More independence We can move faster, more reliably, with greater sense of ownership.

• . Teams are also now able to deploy changes with far higher confidence and at a much greater velocity than before. More builds* Increase in builds per month whilst keeping engineering teams about the same size.

Greater velocity Deploy changes faster with greater confidence .

More independence We can move faster, more reliably, with greater sense of ownership.

• Teams also have a greater sense of ownership and can move faster through software development cycles D R N N E E N P A O A IO L I L T O L T P A Y - R T A C G E I C O T M I N N T I E N I N C U U O M O

U M

M S

M O F

E U

C E

D N

E B

A I

C

M S

I U C

K A

T O

-

U T

L E

B N I

I T O

A U T A N

E IL N R R D O E C OP

• Looking at the infinity loop you can see Atlassian does a lot, but wedon’t do it all. It’s important to note that Atlassian products can get you most of the way there to DevOps, I’d say 70%. • DevOps incapsulates a lot that we didn’t mention, like containerization, orchestration, monitoring, test management, and so on. • This is why we partner with key players in those areas - like Amazon, xMatters, SauceLabs, Puppet, etc.. PARTNERS

Atlassian integrates with key DevOps tools

• So no matter what you’re looking to do, it’s likely Atlassian tools will have an integration available for you. • In the Atlassian Marketplace, you can find integrations to your favorite tools and a wide variety of add-ons to customize your Atlassian tool suite. D R N N E E N P A O A IO L I L T O L T P A Y - R T A C G E I C O T M I N N T I E N I N C U U O M O

U M

M S

M O F

E U

C E

D N

E B

A I

C

M S

I U C

K A

T O

-

U T

L E

B N I

I T O

A U T A N

E IL N R R D O E C OP

• These tools perform key processes and integrate with the Atlassian tool stack to share critical information automatically. CLICK for Transition • Speed through sprints by managing documents, resources and workflows. directly within HipChat, JIRA or Confluence. • Enable automated continuous integration for your BitBucket projects with popular CI tools • Automatically create or append JIRA tickets with metadata and context from testing and monitoring solutions. • Speed code deployment to a variety of hosting options with packaging, orchestration and deployment tools • Keep everyone up to date by exposing status information at every stage in the tools you work in every day. • Resolve issues sooner and provide feedback at any stage with service and alert add-ons that send information automatically to the right people. • Get the right information to the right person automatically with alert tools. Partner integrations

• CLICK for Transition • For example, let’s say that you’re running Splunk to monitor your infrastructure and there’s a problem. Splunk can automatically create a JIRA Service desk issue, complete with metadata to help identify the problem. Sauce Labs, which automates testing, can also be used to directly create detailed JIRA tickets. • Then with xMatters, resolvers will be notified based on a predefined set of rules like on-call schedules or skill set. They can be notified in multiple ways, including directly within a HipChat room. Once the problem is resolved, you can create Puppet jobs directly within HipChat, monitor and control live running. You can also deploy code straight from BitBucket to AWS using the CodeDeploy tool of your choice. • The team will be notified when the updated code is successfully deployed and ticket closed. • With these integrations, you can collaborate seamlessly and automate tasks while keeping everyone in the loop and contributing to the next release. Talking Point Use this format instead of bullet points Automatefor greater impact testing and clarity.

Create JIRA tickets from a test details page & automatically attach screenshots, videos and logs from Sauce Labs test details

• Let me show you how some of these integrations can streamline and even automate your DevOps practice. If you're on the QA team, you know how important automating testing is. With Marketplace Add-ons to Atlassian, it's easy to automatically provide context and rich data to get bugs squashed more quickly. CLICK for Transition • For example, Sauce Labs has many add-ons that trigger action and provide rich detail. Here you can see how you can create JIRA tickets from a test details page and automatically attach screenshots, videos and logs from a Sauce Labs test details page. The right people can then view the metadata directly in JIRA. • It's likely that your test tools are already integrated with Atlassian to improve collaboration and automate what you do manually. Talking Point Use this format instead of bullet points Monitoringfor greater impact tools and clarity.

Real time searches in Splunk trigger incidents in JIRA Service Desk with detailed operational information and configurable levels of service

Alert notifications in HipChat keep right people informed

• Here's another example of how Atlassian helps every member of the team. As an IT team, you know that monitoring tools are critical for maximizing uptime. Atlassian Add-ons can help here too. CLICK for Transition • Built by Forty8Fifty, the "Real Time Splunk for JIRA Service Desk" leverages real time searches in Splunk to trigger incidents in JIRA Service Desk that are enriched with detailed operational information and configurable levels of service. This empowers you to lose the loop on issues taking place in your environment. Then, view rich visual data analytics on both operational occurrences and the service desk experience associated with it. It also offers integrated alert notifications to HipChat rooms to keep the right people informed

• Customers who have adopted Atlassian for DevOps found their teams to be faster, more reliable and more independent. • Speaking of customers, let’s now take a closer look at how JAMF, a leading mid-size enterprise software company, adopted DevOps with Atlassian. • JAMF Software develops enterprise management software for the Apple platform, simplifying IT management for Mac, iPad, iPhone, and Apple TV. From National Geographic to Oxford University, more than 7,000 global customers rely on JAMF to manage 5.5 million Apple devices. • In 2012, Michael Kren joined the engineering team to assist with infrastructure deployment and maintenance. “We were painfully slow. We could code fast, but we had to ‘hurry up and wait’ for testing and building. We needed a stronger set of processes and technologies to get us there,” says Kren. CLICK to Play Video +

“The benefits of having a DevOps team and using Atlassian tools is that collaboration becomes a lot easier. The quality of the code increases because of the tools and integration that Atlassian provides. Meanwhile, we’re delivering software to customers faster than ever before.”

- Eric Kraus, Director of Cloud and Delivery

• JAMF found the solution with Atlassian. After adopting Git, they moved to Bitbucket Server for managing their code repository. They added Bamboo for its killer plan branches and branch updater features and JIRA Software for issue tracking and its tight integration with Bitbucket and Bamboo. Finally, they added JIRA Service Desk for tracking requests.

• The new implementation builds on JAMF’s previous success with Atlassian. Teams including Internal Support, IT, Human Resources, Sales Operations, and Security already rely on JIRA Service Desk to efficiently manage requests. Meanwhile, employees across the company use HipChat for streamlined communication and Confluence for knowledge management. By integrating JIRA Service Desk with HipChat and Confluence, employees can easily pull up data about hardware assets or quickly access the internal support knowledge base. Atlassian for DevOps How Atlassian’s products set you up for success

• So to conclude our journey with DevOps and Atlassian so far.. remember that Culture Collaboration and complete visibility

Speed Release faster and work smarter through automation

Resolution Fast feedback loops and incident management

Prioritization Manage unplanned work with clear prioritization

• It starts with culture - a core ingredient for successful implementation of DevOps. The Atlassian stack of tools puts teams first - providing a collaboration layer on top of DevOps practices. Our tools help foster a collaborative culture by offering complete visibility from issue to source. Culture Collaboration and complete visibility

Speed Release faster and work smarter through automation

Resolution Fast feedback loops and incident management

Prioritization Manage unplanned work with clear prioritization

• Atlassian tools can speed up your releases by automating menial tasks and defining set processes. Culture Collaboration and complete visibility

Speed Release faster and work smarter through automation

Resolution Fast feedback loops and incident management

Prioritization Manage unplanned work with clear prioritization

• Atlassian can help accelerate time to resolution with fast feedback loops and the ability to swarm. Culture Collaboration and complete visibility

Speed Release faster and work smarter through automation

Resolution Fast feedback loops and incident management

Prioritization Manage unplanned work with clear prioritization

• And help you prioritize when unplanned work arises MOST IMPORTANTLY

Atlassian provides the tools that your software and ops teams want to use.

• MOST IMPORTANTLY Atlassian provides the tools that your software and ops teams want to use. Let’s face it, most of the other DevOps tools out there are hard to implement - they just don’t work as well with critical DevOps integrations. With Atlassian, you have a toolset that eliminates the walls and silos between customer feedback, ops, IT & dev and puts all of them on the same platform. Unlike other products that segregate support from dev, we connect these teams. We connect them with something better than email. We allow teams to see each others boards, comments, issues and queues. • And for those of you wondering: How do you get started with the right tools for DevOps? We have the answer! Atlassian Stack A complete DevOps solution for enterprise

• Introducing the Atlassian Stack: a complete DevOps solution for enterprise that has everything your dev and ops teams need on one platform • With the Stack, you can standardize on a platform that your teams know and love, a platform that makes your teams happy and is easy to adopt (internally and from a purchasing perspective) • Teams self-select Atlassian products- which gives teams what they want and keeps them connected • The Stack provides visibility across multiple work streams • and helps simplify procurement • The Stack has everything your teams need to get started with DevOps and Atlassian for one simple price Atlassian Stack

JIRA Software HipChat Capture for JIRA Confluence JIRA Core Portfolio for JIRA Bitbucket Bamboo Team Calendars for Confluence JIRA Service Desk Crucible Questions for Confluence FishEye Crowd

• You get one license of each product listed here Atlassian Stack Premier Support

Dedicated Faster SLAs 24/7 coverage support team

• Plus, Premier Support • Premier Support goes above and beyond our standard offerings to provide account-level support from a team of senior support engineers across all your business-critical Atlassian applications. • Premier Support provides: • Account-wide service* across all your Atlassian applications • Up to 3 named contacts from your company can open Premier Support tickets • First-line response from a dedicated team of senior support engineers* who are familiar with your unique environment • Development escalation priority* - Higher priority development escalation queue placement ensures your issues are triaged by development more quickly • Customers will know more quickly the root cause of an issue, whether it’s been fixed or whether it will be fixed • Faster SLAs* and improved responsiveness •30 minutes for critical/L1 issues, and 2 hours for L2 issues. • Weekend and phone coverage •Regional phone numbers allow you to speak directly with the team supporting you. •Coverage for all products over the weekend (see chart for detail) • Warm handoffs and escalations around the world to regional teams • A thorough on-boarding process* - We’ll work to understand your network and environment by: • Reviewing and opening support tickets and looking for trends • Documenting your environment details, plug-ins and customizations • Audit use of support best practices and recommend proper system configurations to shorten troubleshooting time Customers who choose Atlassian for DevOps

and these are just some of the customers who choose Atlassian for DevOps, among many, many more… Closing title / DevOps with Atlassian key takeaway

• So remember earlier I asked you if you thought there was anything in common between running a restaurant and DevOps? • I hope you see now that just like in Software and IT, in a kitchen there are a number of chefs and people in various roles, each with his or her own area of responsibility • For making a dish a true success, it’s important to not just have access the right tools or have the most qualified people, but to instill a culture that makes it easy to collaborate, trust, be transparent and encourage continuous iterations on the go. • I hope you enjoyed your journey to DevOps with Atlassian today. Contact us for a personalized demo of Atlassian tools for DevOps or reach out to us for questions. Q&A

Let’s now open it up to questions.. Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking

• Instruction to Solution Partner: Launch the Workshop deck if running Team Playbook exercise Atlassian

State of software Agenda Steps to DevOps DevOps - the Atlassian way

Workshop: Team Playbook

Networking Thank you Subtitle

SPEAKER PERSON | SPEAKER TITLE | @SOCIALMEDIAHANDLE