These five development practices are core to Extreme Programming (XP) and essential for DevOps—automating the build for continuously integrating software as it is written, collaborating with team members through pair programming, practicing Agile design skills that enable testability, using test-first development to drive design, and refactoring code to reduce technical debt. Together, these five technical practices are proving to be essential for sustained success with Agile DevOps. However, many teams haven’t been exposed to the benefits of these practices or understand how to use them effectively. David Bernstein explores these engineering practices and their use in reducing risk and building quality in at every level of the development process. He makes the business case for these practices by showing how they address the inherent risks and challenges of building software. David then examines how these XP practices help us address the core issues of software development.

DevOpsの領域だけでは対応しきれない、プロダクトのグロースの部分をData-Drivenの考え方でどういうふうに開発プロセスを補完していくかについて述べていきます。

LeanStartupのBMLループを開発プロセスとして各ループ遷移(Learn→Idea,etc...)の中でどういったことを意識しながらData-DrivenとDevOpsの考え方を使ってプロセス設計していくかについて、KGI,CSF,KPIの設定からビッグデータ基盤・データ分析基盤、優れた指標などDMM.comの事例を用いりながら説明していくます。

サービス運用をまんなかにおいた開発についてお話します。

僕は2010年から楽天の大阪支社でウェブアプリケーションエンジニアとして仕事をしています。僕のいる部署は中規模から小規模のたくさんのサービスを担当していて、1つのチームまたはグループでサービスの開発と運用の両方を担当しています。

サービスの開発と運用の両方を担当しているため、僕らはサービスの運用のことを常に考えながら開発に取り組んでいます。運用のことを考えずに開発をすると全てが自分たちに跳ね返ってくるからです。

このセッションでは、サービスの運用をまんなかに置いて開発をするときに、どのようなことを考えるか、また、どのように他のチームや組織と向き合うか、について自分の経験を元にお話したいと思います。

資料は英語ですが、セッションは日本語です。

SIビジネスはなくなると言われ始めて数年、富士通のビジネスの中心はまだまだSIです。

• ウォーターフォール、多層請負契約が中心のSIプロジェクトがDevOpsというテーマにどう取り組んでいるのか？
• 富士通のSIプロジェクトは年間数千件。どのように標準化、適用推進活動をしているのか？
• これらのSIプロジェクトでは、どんなツールを使って、どんなプラクティスを実践しているのか？
• DevとOpsを隔てる壁へのアプローチは？
• そして、今後SIビジネスがなくなっていくことにどう備えているか？

こういった内容を泥臭い実践事例や苦労話を交えてお話ししたいと思います。

As CTO of CloudBees and the creator of Jenkins, I get to see lots of real-world software development. Our automation in software development is sufficiently broad that it is producing lots of data, but by and large most of those are simply thrown away. Yet at the same time, the management is feeling like they are flying blind because they have little insight! In this talk, Kohsuke will discuss how we collectively seem to miss the golden opportunity to improve the software development process itself, based on data. IOW, learning is lacking at the organizational level, let alone "machine" learning!

DevOpsを上手に回すために、開発チームとビジネスが一体となって動く必要があります。

一言でビジネスと言っても多種多様なセクションを含んでおり、なかなか一人で全てを回すことは現実的に難しい状況だと思います。

上手くDevOpsを回すための作戦としPOチームを組閣、社内の業務改善プロジェクトがどのように動いていったのか？

実際にPOチームに編入されたメンバーと、開発チームの双方の立場からプロジェクトを振り返ります。

DevOps のアプローチでシステム開発に取り組む上で、データベースに対する変更をどのように扱うかは難しい問題です。このセッションでは、ライフサイクルが異なるアプリケーションとデータベースに対する変更を適切に管理することを目的として、代表的なデータベーススキーマ変更の手法を紹介し、それを CI/CD パイプラインに組み込む方法について考えます。

最近は日本でも「DevSecOps」というキーワードがよく聞かれるようになりました。弊社はシステムインテグレーター企業ですが、開発プロジェクトではDevOpsを導入したり、アジャイル手法を取り入れるプロジェクトが増えてきました。しかし、DevSecOpsのSecの部分でいうといまだに迅速な変化に対応できていません。

そこで昨年からDevSecOps導入に向けて動き始めました。そこで、本プレゼンテーションでは実際にどのような壁に当たったのかなどを含めて、実践した内容を共有したいと思います。

Today the term "DevSecOps" has started to come up more recently in Japan. In our company, a system integrator, some development teams are changing to DevOps, but security rules and policies are still for "waterfall" development.

So now we are trying to start implementing DevSecOps. In this presentation, I want to share an case study of starting DevSecOps in Japanese Enterprises.

Infrastrucute as Codeを安定した品質とリリース速度を両立させるには、インフラCI(CI:継続的インテグレーション)の構築によるセーフティーネットとパイプラインの構築が欠かせません。

本セッションでは、筆者のサーバー環境の構築において、VagrantによるインフラCIの環境構築からPackerによるイメージ作成、そしてvagrant-awsとPackerの併用という現在の環境に落ち着くまでの道のりをとりあげ、インフラCIを現場に導入するにあたってのポイントを紹介します。

DevOps/DevSceOps is a journey and requires a lot of changes in your organization and the affected teams. I would like to take you on a journey from waterfall to DevSecOps. Looking at the traditional approach and the issues you will face or you are actually facing while implementing DevOps. Moving on with what will happen if you set up DevOps without security and finishing with best practices approaches and tips how to get security included in your DevOps process to finally implement a full, secure DevSecOps process.

In our team, the thing that we valued most is how our codes are making impact to business. It can be deploying feature that create new profit, fixing bug, increasing deployment time and etc.

Making impact means in the end codes have to be deployed to production. We never set rules related to deployment. Anyone, anytime, anywhere. We even do have so-called "First day deployment" operation which make sure new member make their first deployment to production within 24 hours since they join our team. How do we make sure that works ? We trust. In our team, everyone is AWS admin from the first day. We want make sure everyone has the essential tools to setting up infrastructure, coding, releasing, monitoring. Human being, when given trust they take full responsibilities. Responsibility to complete work and hence making impact to business.

It sounds like psychology, right ? Or I will just say culture.

In the end, it's all about trust, freedom and responsibility. Let me show you how and why we inject (or being injected) these cultures into our team, how we improve and make sure it's getting better.

井の中の蛙大海を知らず - "A frog in a well does not know the great sea."

Software engineering may be difficult, but fostering a working environment that enables skilled engineers to perform their best can sometimes seem downright impossible. Every day, many engineering teams are battling a messy whirlwind of forces like unmovable deadlines, impostor syndrome, psychological safety issues, personnel/leadership conflicts, fierce technological preferences, and more. With teams more distributed all over the world than ever before, cultural differences can exacerbate many of these difficulties.

As a software engineering coach, my job is to not only introduce new technology to software teams currently looking to transition to DevOps, but to strengthen their working relationships within their organization. Coaches aren’t simply technical instructors. Rather, they are change agents that guide a team towards better outcomes for their project as well as their interactions with one another.

In this presentation, I will discuss tips, tricks, and techniques that technical leaders and managers alike can utilize to better coach engineering teams, including concepts like the definition of empathy (and, more importantly, what doesn't count), the trust-influence relationship model, introducing new technologies in a meaningful and consumable way, and a 5-step process to provide teams confidence to own their new DevOps solutions moving forward.

スピーカーは日本語が分かるから、セッションコンテンツの日本語版もあります。

タイトルから分かる通り、ネタ枠ですよ！

一時期 devops がバズワードと化し、猫も杓子も devops、devops と言葉だけが先行していました。そういったことがなくなり、ほっと胸を撫で下ろしていると、

NoOps「devops は短サイクル開発なだけ！ SRE は devops の進化したもの！　NoOps は アーキテクチャ設計 に SRE と devops を内包したもの！」
devops やっているぞヒューマン「devops やっているって言うため、足りないときは空コミットしたりして、毎日 10 deploy してますが大変ですよね！」
devops わかってるぞヒューマン「私はビジネスを考えているので、devops なんていう dev と ops のことは開発だけでやってください！」

ということがここ最近よく起きるようになりました。というわけで、devops に対しての誤解を解くとともに、実際 devops をどういう風にしたのか、どういった成果、業績がでたのかを複数の事例でご紹介します。

タイトルから分かる通り、ネタ枠ですよ！

大事なことなので 2 回書きました。

Chaos Engineering, failure injection, and similar practices have verified benefits to the resilience of systems and infrastructure. But can they provide similar resilience to teams and people? What are the effects and impacts on the humans involved in the systems? This talk will delve into both positive and negative outcomes to all the groups of people involved - including users, engineers, product, and business owners.

Using case studies from organizations where chaos engineering has been implemented, we will explore the changes in attitude that these practices create. This talk will include a brief overview of chaos engineering practices for unfamiliar members of the audience, but the main focus will be on human elements. I will discuss successful implementations, as well as challenges faced in teams where chaos was a “success” from a technical perspective, but contained negative impact for the people involved.

After seeing this talk, attendees will have a better understanding of the human factors involved in chaos engineering, good practices to care for the people and teams working with chaos, and be even more excited about this practice.

Chatbots are one of the most widely adopted AI/ML implementations in the business sector. A chatbot is an intelligent machine used to imitate human conversation through text and voice commands. Today bots are widely used as a personal assistant, customer service, HR, sales and marketing to name a few. In short, bots are everywhere and we rely on them to a certain extent, this makes it extremely important to assure the quality of the chatbots and test them thoroughly. They are built using NLU/NLP-Services (Natural language understanding and processing) and are subjected to constant training and improvement which has direct impact on tests. Voice based bots like Siri and Alexa depend on speech recognition technologies. As the chatbots user do not have any barriers and due to the unpredictable user’s behavior it becomes utmost difficult to verify the correctness on the output. In this talk, we will discuss how the chatbots are different as compared to the other applications and the challenges they bring onto the table while verifying their behavior, and focus on the testing strategies and automation testing of the bots.

In today’s ever-changing and competitive landscape of online retailers, companies invested heavily into end to end testing practice to ensure the best quality for their product. The seamless shopping experience between mobile and physical store is the universal high bar for success.

Retailers that embraced omni-channel mobile first strategy often build their system top a multi-tenant architecture. In order to make all tenants work in harmony as one unit, across all engineering teams, Test Driven Development (TDD) must be one of the Objective Key Result (OKR). The center piece of that effort is the investment in automated end-to-end testing. During this session, come join David for a in depth look of how Cypress.io enabled dev team incorporate automated testing for both internal web applications, and its public facing e-commerce site.