DevOps for Japan (Tokyo DevOpsDays 2017)
•Download as PPTX, PDF•
5 likes•1,199 views
This document summarizes a presentation about DevOps in Japan. It discusses how DevOps and agile practices were initially foreign concepts in 2011 but are now gaining adoption. Localizing DevOps from Western approaches requires understanding the underlying issues, solutions, and cultural differences between avoiding blame cultures and avoiding shame cultures. ChatOps was presented as a DevOps idea to improve communication, and the document discusses how to thoughtfully adapt such ideas by understanding problems and comparing situations in different cultural contexts.
Recommended
More Related Content
Similar to DevOps for Japan (Tokyo DevOpsDays 2017)
Similar to DevOps for Japan (Tokyo DevOpsDays 2017) (20)
Recently uploaded
Recently uploaded (20)
DevOps for Japan (Tokyo DevOpsDays 2017)
- 1. DevOps for Japan Alex Papadimoulis DevOpsDays Tokyo 2017
- 2. Hi. I’m Alex Papadimoulis. • パパヂモウリス • Software developer • Automation/process consultant • 2007: Founded Inedo • 2012: Understood “DevOps” buzzword
- 3. Why Japan? • 2011年、米国で • Hiranabe-san • Change Vision US Expansion • “Come see SODEC tradeshow!” • … ok! Why not?
- 4. 東日本大震災 • 3月11日 • 4月 7日: 宮城県地震 • 5月11日: SODEC • “Japan is soooo Dangerous” • Almost canceled
- 5. SODEC 2011: What did I learn? • ちょっと違う • Companies weren't agile • DevOps didn't exist • Not a good market for Inedo
- 6. The Battle for Agile in Japan • System Integrators • Embedded culture • Drive for quality
- 7. Lots of Trips to Japan • Tradeshows • Meetings • Conferences • お花見 • たこ焼き • 飲み放題
- 8. 2016: A New Feeling • Cloud usage expanded • Major factor:東日本大震災
- 9. 2017: Expansion to Japan • Japan is ready for DevOps • Opening Inedo office • Building DevOps community
- 10. DevOps Requires Agile Agile Requires DevOps
- 11. Agile: Idea to Results Faster
- 12. Agile Process Idea Specs Code … Deploy Verify Result … … …
- 13. DevOps Accelerates Agile Idea Specs Code … Deploy Config Result … … …
- 14. •DevOps •Agile
- 16. DevOps Gone Wrong Failure to Localize
- 17. An Interesting DevOps Idea
- 18. Netflix Chaos Monkey • Randomly terminates EC2 instances • In production • During business hours • Would you implement this?
- 20. HOWTO: Localize DevOps Ideas • THEIR PROBLEM: Understand what the underlying issue is • THEIR SOLUTION: Understand why they chose their solution • YOUR PROBLEM: Understand your underlying issues • COMPARE: Understand how the situations differ
- 22. • DevOps • Agile • 和Culture • 洋Culture
- 23. You don’t know Japanese IT culture. Or Western IT culture for that manner.
- 24. We don’t know our own language.
- 25. For example, “Adjective Order” • That is a big red car. • That is a red big car. →ダメ: Engrish 1. Size 2. Color 3. Material? 4. Temperature?? 5. ?????
- 26. 例えば、「～んだ」 • 今日は、DevOpsDaysへ行く。 • 今日は、DevOpsDaysへ行くんだ。 1. Explanation of action (買う。安いんだ。) 2. Interpretation of situation (酸っぱいんだ。) 3. Discovery of new information (腐ったんだ。) 4. Summary of situation (病院へ。病気んだ。) 5. Leading remark (臭いんだ。買わないよ。)
- 27. How to Learn Japanese IT Culture Learn Western IT Culture First
- 29. How to Learn Japanese IT Culture • Experience Western IT Culture. • Talk to foreigners in IT. • Question everything!
- 31. 面白いDilbert Strip
- 32. America: Culture of “Blame” • Cover your ass. • Never apologize. • Self above team and company.
- 33. 洋DevOps is “Avoiding Blame”
- 34. Japan: Culture of …?
- 35. 東日本大震災
- 36. Kiyoshi Kurakawa “What must be admitted – very painfully – is that this was a disaster ‘Made in Japan’. Its fundamental causes are to be found in the ingrained conventions of Japanese culture: our reflexive obedience; our reluctance to question authority; our devotion to ‘sticking with the programme’; our groupism; and our insularity.”
- 37. Japan: Culture of “Shame” • 出る杭は打たれる • 土下座 • たぶん。。侍と忍者？
- 38. 和DevOps is “Avoiding Shame”
- 39. Let’s Localize!
- 40. ChatOps知てる？ “ChatOps connects people, bots, and tools, making information readily available and creating an easier workflow.”
- 42. Localizing DevOps Ideas • THEIR PROBLEM: Understand what the underlying issue is • THEIR SOLUTION: Understand why they chose their solution • YOUR PROBLEM: Understand your underlying issues • COMPARE: Understand how the situations differ
- 43. 洋Problem Understand what the underlying issue is. • Different teams aren’t communicating • Information is not being shared
- 44. Office Space
- 45. Office Space
- 46. Geography
- 47. 洋Solution Understand why they chose their solution. • Many western offices are not collaborative • Many people work different offices or from home • Culture of Blame
- 48. 和Problem Understand your underlying issues. • Information isn't readily available • People aren't communicating
- 49. Compare Understand how the situations differ. • Same office, same timezone, same language • Chat is not as nice as face-to-face
- 50. Translate Adapt the solution. • More in-person, casual meetings • Kanban boards • Big status LCD Monitor
- 52. Only Japanese People Can Localize DevOps ありがとうございました
Editor's Notes
- NOTE -- the notes in this slide are provided to convey the general feeling for English >> Japanese simultaneous translation.
- Hi. I'm Alex P. Most people have a difficult time pronouncing my last name. Japanese people, however, can say it just fine! I started my career as a software developer, and quickly discovered there were faster, better, and cheaper ways to build software. So, I helped organizations adopt agile, continuous integration, deployment automation, etc. In 2007, I founded Inedo to continue with this consulting. Eventually, we became a software product company and sell tools that help enterprise companies adopt DevOps. Although DevOps is an older world, it took me a long time to realize that Inedo was a DevOps company.
- Back in 2011, I met with Hiranabe-san, then the CEO of Change Vision, to help with Change Vision’s US expansion. They make a UML modeling tool, Astah. Although it’s not really related to DevOps, Inedo still works with Change Vision outside of Japan. After our planning meetings, Hiranabe-san invited me to visit SODEC, to learn about the market. Although I had traveled through Europe a lot, I had never been to Japan, and I figured… why not?
- Well, one reason not to come to Japan was the Great Japan Earthquake. It was a major worldwide event, and the American news made Japan seem very dangerous and unsafe. And then one month later… there was another earthquake! So, many people told me not to go to Japan yet. Fortunately, I did not listen to them and I visited Japan.
- Everything was different. Not just the food and culture, but the way software was built and sold. The fact that companies weren’t agile was really strange; It was hard to imagine how, in 2011, most software as built in Waterfall. And obviously, no one had even heard of DevOps. Obviously, this wasn’t a good market for Inedo.
- But I couldn’t get over the fact that companies weren’t developing using agile software. I asked Hiranabe-san, and many others why. This is when I learned about System Integrators. Wow. That’s different. And a very good reason why Agile isn’t easy to adopt. We can’t just blame the SI’ers though. Agile is not a great fit for embedded, safety-critical software, and a large portion of Japan’s software engineers work on those systems. The Japanese drive for quality is also a challenge; Agile doesn’t produce bad software necessarily, but the process is velocity- and results-driven, not quality driven.
- Over the years, I made many more trips to Japan. There were a lot of different things to do… Tradeshows… Meetings… Conferences, those sorts of things. (each bullet will appear when I say it, but the last few words are meant to be read)
- In 2016, things felt different. This image is from a Gartner report showing that a majority of companies are considering agile practices. This was a large shift from just a few years earlier. Interestingly enough, the earthquake was a major driver for this. To ensure uptime, this encouraged companies to go to the cloud, which meant more agile… and devops practices would be required.
- This year felt like the right time to expand to Japan. I believe, Japan’s market is now finally ready for DevOps, and all of us can work together to make it happen. My company is opening an office to sell our software products. We have tools for DevOps that have helped many organizations around the world transition and improve their DevOps process. But I also believe in community, which is one of the reasons we’re helping organize this and other DevOps events.
- It’s important to first consider the relationship between Agile and DevOps. Most realize that it’s not possible to achieve DevOps without first becoming agile. But, to become truly agile, you must use a DevOps process eventually.
- Fundamentally, agile is a very simple idea. Take an Idea and get the Result faster.
- This means that the scope of Agile is fairly wide. It includes not just thinking of small ideas, but specifying them, coding them, etc. The process doesn’t end with deployment, the business result must also be verified.
- The scope of DevOps, however, is smaller. It focuses on helping deliver those smaller changes sooner. A DevOps mindset doesn’t need to care about the business impact of different changes… just that those changes are small and can be delivered in a consistent manner.
- DevOps is Built on top of Agile. Agile is a business mindset. DevOps is a technology mindset
- But Agile is built upon a new mindset, and a new culture. You cannot implement Agile on top of a “Waterfall” mindset. You must get the business to think of smaller ideas, and be able to measure those results sooner. This is particularly difficult, because every workplace culture is different. Agile is about changing that underlying culture. We must also change that same culture when we implement DevOps.
- Fundamentally, DevOps works, and will help companies release their small ideas faster. Every single DevOps failure can be attributed to applying wrong DevOps Idea to the wrong culture.
- How many of you are familiar with the Chaos monkey? Actually, it’s pretty old of an idea. Perhaps, 2011. It was created by Netflix, and was as topic they blogged about quite a lot.
- Here is how it works. Netflix uses hundreds of Amazon EC2 servers to provide their services, and this Chaos Monkey tool will randomly terminate those servers. In production. During business hours. How many of you would implement this in your company?
- Of course, none of you think it’s a good idea for your own services. The reason is that you have a “dual understanding” of the situation. You know what Netlix does – stream movies – and you know what your company does – maybe a bank, maybe something else – but because those situations and cultures are different, you know that this idea wouldn’t work for you. That doesn’t mean the Chaos Monkey is a bad idea however!
- Let’s consider how to localize. First, consider their problem. Netflix wants engineers to write resilient software. This is a nice goal. But why did they chose this solution? Well, They have a culture of “ownership” – developers own their deployments and failures. This means when there’s a failure, developers are the ones who are called at 3AM to fix it. This motivates them even more to write resilient code. Let’s consider your problem. Of course you want resilient software too. But now we need to compare. They stream movies. You don’t. The cost of having customers experience outages randomly is simply not worth the benefit of teaching developers to write more resilient software. So how can we adapt it? Well, maybe you can simulate outages in testing environments instead. During work hours.
- This was easy with technology, because most of you have an engineer background… and you can understand their technology easy. But this is not easy with culture. In order to compare cultures, you need to know BOTH workplace cultures in order to TRANSLATE the idea.
- This is especially difficult for Japan, because DevOps is a western idea. This means that Devops for Japan is built on Agile for Japan, which is built on Japan Culture, which is built on Western Culture.
- But there’s a big problem with this, because you don’t truly know your own culture. That seems impossible… after all, you are Japanese. But the same is true for me. I don’t know American Culture. Why? Because it’s natural to me.
- Let’s consider language. As a native english speaker, I actually don’t know English that well. I can speak it very well, I can write it, and I can read it. But that doesn’t mean I understand how it works, or how to explain it to other people.
- Consider this red hummer. How can we describe it? It’s a big red car. But can we say “that’s a red big car”. No. I’ll understand what it means, but it’s wrong and sounds like Enrgrish to me. Many of you have learned why in school. That’s because English has a very specific order for adjectives. First, you describe the size. Big, small, medium, whatever. Then the color. Then, I believe, the material. Like metallic or wooden. Perhaps, the temperature comes next? Like, “big red metallic hot car”? Or maybe it’s first, “hot red metallic big car”? Now I’m confused. Actually, I don’t know the order. I will always say it correctly if I don’t think about it too much… and I can tell you when it’s wrong.
- In the same manner, you don’t really know Japanese. One thing that was difficult for me to understand at first was something called the “のです nominalizer”, or んだ in spoken Japanese. [read two sentences ]. I asked a lot of Japanese people what the difference was, and actually, they all gave a very simple, one-word answer. “難しい－” Well, now I can explain it to you how it works. /// NOTE this will be very difficult to translate into Japanese, so we may want a different
- You cannot understand what’s unique about your culture until you study another culture.
- The easiest way to learn about a foreign culture is to experience it. But short of spending a career in American IT, you can just read and watch content.
- But it’s more than just watching TV. You need to talk to foreigners to learn how their work is different. And most importantly. Question everything! Don’t apply your native Japanese mind to western culture, or you will get it completely wrong.
- Let me give you an easy example. How many of you have seen an image or concept like this in a movie or TV show somewhere? Like Someone drinking beer in a paper bag outside? I bet none of you questioned it. Maybe, you just assumed it was a convenient way to drink? Or, their hand doesn’t get wet? The concept makes absolutely no sense, and you need to question it. The reason people do this is because, in America, we have something called “open container” laws. That means, it’s illegal to drink alcohol in public places, or anywhere without liquor license. It’s very strict, but this is an American norm. Actually it’s weird to see beer vending machines and people walking down the street with chu-hi. But this still doesn’t explain the situation. It’ obviously an alcohol in a bag. Well, we also have “4th amendment” culture, which is too much to explain now, but basically the police are not allowed to ask you what is in the bag. If they can’t see what’s in the bag, they can’t arrest you for public drinking . We all know this Americans, and it’s weird to think it’s any other way. So this way, you learned two interesting facts by questioning a simple idea. Anyway, I don’t recommend doing this in America.
- That was easy, but now let’s consider this comic strip. To me, it’s very funny --- and most americans will laugh when they read it. But why? In this case, Dilbert is working on a project that will fail no matter what they do at this point. The only thing they can do today is decide who will take the blame when the project fails. The boss agrees with the situation, but makes it clear that he wants no involvement in the plan. If he gets involved, then he might be blamed for participating in a failed project. It’s not very funny when I have to explain it. But you shouldn’t be reading these for humor, but to learn. In this case, we are exposing something very intereting an America…
- I call it the culture of blame. This is the American workplace culture, and most of America actually. We learn a phrase, early on, called CYA. It basically means, make sure that there is no way that you can be made to blame for a situation failing. This is one reason that American contracts are dozens of pages long. Don’t say I’m sorry. That implies that you are at fault. Alsways put your own job above your team and company. If you have to choose between the company failing but you keeping your job… you keep your job.
- Thus, Western DevOps is about changing this culture and helping to Avoid Blame. When there s a failure, Ops will blame Dev for writing bad code. Dev will blame QA because it wasn’t tested. QA will blame Ops because it wasn’t configured.
- But Japan, what kind of culture is it? It’s not a culture of Blame…
- An interesting insight into Japanese workplace clture came from.. The great earthquake. The 600+ page summary report talked about the reason that the nuclear power plant failed. One big reason was Japanese culture.
- Kurakawa-san wote the english summary. // this quote is very difficult english…
- My impression is that Japan a culture of Shame. In America, we have an expression “the squeaky wheel gets the grease.” But the Japanese equivalent is “the nail that sticks out gets the hammer.” The culture of apology in Japan is big. Even if you don’t mean it, or have no responsibility for the situation, you apologize. And then maybe something with ninjas and samurais. I don’t really know. I ‘m having a hard enough time studying the language, let along workplace culture. I’ve learned far more about America’s IT culture in the past couple years by learning about Japans culture.
- In any case, I do know its not about avoiding blame… but perhaps Japan DeVOps is about avoiding shame.
- So now let’s practice localizing another idea for Japan.
- Who is familiar w/ Chat Ops?
- Basically, it is a group chat room, that receives messages from automation services instead of email.
- As a review, here is the process to apply.
- What problem was ChatOps trying to solve? On the surface, these are common problems. Now, let’s consider why the chose the solution.
- This is a typical American office. Actually, it’s from the movie Office Space! Note how spread-out it is.
- Many American offices have large “cubiciles” with high walls. So, in order to talk to a co-worker, you walk to their desk and talk to them.
- And of course, companies are spread all across the country. Sometimes a company will have an India or London office as well. This means there are diferent time zones to consider as well.
- These reasons are why ChatOps is a good way to bring these teams – which may be separated physically in the office, or geographically separated. And don’t forget the culture of blame! Chat Ops creates a train of evidence that proves you shared a vital piece of information with a coworker. This way, that coworker can’t blame you because you didn’t tell him
- These problems may be the same in your company.
- However, consider that Japan and Japanese offices are very different.
- So how can we adapt this? Well, let’s take advantage of the open-office plan in many Japan offices. Why not just have more casual meetings? Or, perhaps, use Kanban boards? This is a nice way to quickly share and visualize status. And since everyone is in the same room, it’s easy to see the information. Maybe you could even use monitors to display information. Or a projector.
- I don’t know if it’s a good idea. I can’t tell you how to localize DevOps because I’m not Japanese.