What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: DevOpsDays-Tokyo-Opening
Select a size
DevOpsDays Tokyo 2017 のオープニング用の資料です。
25 April 2017
Why use DevOps?
より良く、より早く、より安く Better, faster, cheaper
世界中の企業がこれらのメリットを経験している Many companies around the world experienced these benefits
What is DevOps?
簡単ではない It’s complicated.
世界中で多くの違う定義がある Across the globe, there are a lot of different meanings
「正しい」定義はない None of them are the correct meaning
日本の中ですら、違うことを考えている Even in Japan, no one can agree
Two Universal DevOps Principles
チームをまたいだコラボレーション Collaborate across teams
Dev, Ops, QA, Management, etc.
できる限りすべてを自動化する Automate everything you can
Builds, Deployments, Infrastructure, etc.
How can I use DevOps?
DevOps マインドセット の理解
First, you must understand the DevOps mindset
Then, you must translate it to Japan
Then, you must translate it to your organization
Then, you must sell it to your organization
Think in English.
What is the DevOpsDays?
Thank you, sponsors
DevOps は日本企業には根づかない、 と思っていませんか？
Thank you, volunteers
Thank you, organizers
Although no one can agree on a definition everyone will agree on these two principles. They work together, and neither alone will achieve DevOps. Better automation helps teams collaborate, and better collaboration helps find what can be automated.
Although there is no single definition of DevOps, the mindset is universal.
DevOps is based on western culture, and it’s important to “localize” the DevOps mindset to Japan. This is more than just translating the language, it’s making sure the ideas make sense for a Japanese person inside of a Japanese company.
What works for Rakuten or Cookpad may not work for your organization. The business problems are different, and DevOps needs to be implemented differently.
Once you’ve understood and translated the ideas, you need to convince the organization --- not just the stakeholders , but the devs, qa, etc -- that this new DevOps idea is appropriate for the organization. It’s a change, and universally, people don’t like change.
Because Devops is evolving, it’s important to repeat the process. There will be new tools, new ideas, and the market will change. It’s important to continue improving your software delivery process.
And because DevOps and other engineering practices come from the west, it’s important to have a faEnglish
Because DevOps and other engineering practices come from the west, it’s important to have an English mindset when you translate DevOps. You don’t need to be able to comfortably speak it, but in order to understand what is uniquely western (and cannot be translated so well), but you have to be comfortable with some English. It’s the difference between watching a movie with subtitles and dubbed. The dubbing is never as good.
The purpose of DevOpsDays Tokyo is to help you understand, translate, translate, and sell DevOps.
Can you speak about them?
Powerful / Scalable
Easy to Use
Compliance / Auditing