We have been focusing on the wrong part of CALMS.

Sure you can set incentives, you can reorganize and adopt SCRUM, but rarely does you achieve a DevOps culture through business led “digital transformation”.

Paul will talk about the concrete steps that you, as a leader or a practitioner, can take to utilize Automation, Measurement, and Sharing within a Lean framework, and how to drive towards a DevOps culture by doing the work and proving value.

Devops is now officially 10 years old. What have we learned? Although prescriptive practices like Lean, Agile, SAFE and even DevOps may be necessary for IT acceleration they are in most cases are not sufficient for long-term systemic improvement. In other words, you can’t Lean, Agile, SAFE or Devops your way around institutionalized organizational habits. Therefore, the key to long-term improvement lies in an understanding where human capital interconnects with technology. The following is a list of the “Seven Deadly Diseases”:

Invisible Work
Management System Toil
Tribal Knowledge
Misalignment of Incentives
Incongruent Organizational Design
Misunderstanding Complexity
Security and Compliance Theater

These seven diseases of organizational behavior must be uncovered with absence of prescriptive practice through a process of organizational fact-finding. In this presentation, we will look at the “Seven Deadly Diseases” of IT organization work and show examples of how to uncover these diseases through a process of organizational forensics (i.e., fact-finding).

Over the years the word devops lost it’s meaning at least it’s original meaning.

The real challeng for the next decade will be to see how we can revive those original values and ideas , if at all ..

This talk will give you some Ideas about that

DevOps have appeared on a conflict between development and operations, and commonly it is still like this. However, if we look deeper, it is all about culture and conflicts between people in a fast changing environment which we call ‘agile’. How to stay calm on the road of delivering happiness to customers, to preserve good relations with colleagues still being professional and delivering the product?

I will focus on several cases from my own experience which will show how to achieve the goal in cooperation with different people and their roles, from your teammate or product owner to senior management, even if you feel yourself on the opposite side.

“This will never work here” is what we often hear from companies just starting their DevOps transformation. The good news is that the change is possible.

In this talk, Sasha will explain how Microsoft moved from their three-year waterfall software delivery cycle to deploying multiple times a day.

Using the example of the live engineering environment for Azure DevOps Services, Sasha will walk us through the process of updating older systems, transforming automated tests, implementing CI/CD, and the major cultural changes needed to make it all possible.

This talk should trigger a lively discussion. As known by many, most pros in Ukraine have no idea what DevOps really is or why it makes sense to implement it in the first place.

They just do not have enough experience to do the right things in a right way. Also, they may not know how to learn on their own, or from the mistakes of others.

I will share my own experience with DevOps, provide detailed answers about what’s going on with DevOps in real life and about what we should be talking on DevOps with our partners and customers from Europe, the UK, and the US.

I will also share my knowledge of CoE and the idea of “flexible platform” based on my own and our group experience, and offer the world’s best practices.

The DevOps movement has been bringing Just Culture into the tech industry. It’s time to learn what it is and how you can harness it to make your teams happier. We’ll discuss some of the research from Sidney Dekker and the DevOps movement, and I’ll share some of the methods I’ve used during cultural transformations. Long Just Culture stands to benefit the tech industry and all industries greatly. It started in aviation and health care, but John Allspaw brought it into the tech field through DevOps. It has actually become one of the three pillars of DevOps according to Gene Kim and John Willis. I have been studying this field for years, and we’ll discuss some of the original research as well as some of the latest related to DevOps. Then we’ll discuss some of the methods I’ve used in transformations that have included culture. In fact, all transformations are underpinned by culture, and that is something I always focus on first. What will the audience get? The audience will understand what is Just Culture, where it came from, and how to implement it at their companies. I’ll also provide some additional resources for the audience to learn more after the session. Why me? I often find myself the leader of transformations, but I’m merely the representative for so many who brought about these transformations. I brought large changes to a large medical company as a junior software engineer. I transformed a multinational, fifteen thousand person company as a DevOps Engineer which included cloud migrations and culture changes. Then I moved to a 150-year-old non-profit where I brought cloud, data, and culture changes through a large transformation. Most recently, I started a transformation at a large multinational security software vendor with culture, cloud, and SaaS changes.

The presentation describes how IT infrastructure has evolved from spaghetti infrastructure, a setup where organic growth and individual parts of the system were inter weaved into the architecture where developers were operations, the prevalence of virtualization and the increase in IT usage created individual layers in the infrastructure and created silos of specialization and this created a difference between developers making software and operations managing the infrastructure. From this lasagna based system, that was cumbersome and difficult to manage the idea of developer techniques and methodology were added to create teams, describing infrastructure as code. This lead to team being able to deliver software faster and deploy easier, the infrastructure was still not as agile, however in an effort to make infrastructure to be as agile the idea of containers where used to make infrastructure more agile, creating small environments for specific usage, to be able to manage it easier and quicker, and so the ravioli infrastructure was born. The presentation also side lines some examples more in detail and some misconceptions.

Running Windows docker container on Amazon Elastic Container Service with task definition conventions to easily inject sensitive information stored in AWS Systems Manager Parameter Store.

Developers are making a difference in the world. We are solving hundreds of tough world problems. We invent and build lots of products which solve customers needs. And the considerable part of it is solutions for B2B. We are solving operational and productivity problems for fields like marketing, sales, finance, etc.
That is what we can do for the world, but who will care about our productivity and happiness?

That is time for a new evolution in Software development, and only developers can make it!

What is time? Is it fixed or fluid; physical or philosophical; quantifiable, or completely questionable? These deep questions may never be answered, but one thing is clear: the measuring, recording, and interpretation of time is a fundamentally important mission for humanity. In the modern age of computing, the accurate reckoning of time across cities, countries, and even planets is performed by a fantastic patchwork of actors – from governments and corporations, to academicians and hackers of all colours.

In this ignite presentation, we’ll explore some of the different ways time is measured, look into the real-world ramifications of time reckoning on the Internet today, and even have some fun with time zones, broken datetime libraries, corrupt nation-states, and a bunch of charts, graphs, and maps.

Long story short, every work has its begging and the end. Every project begins with something and ends up at some point. In case we don’t want to follow the stream, – we should create innovations and start new directions. Let’s make a journey and reach all the checkpoint we need to make the continuous innovation happen. Step by step we will solve different cases in the state of uncertainty to achieve our goal being the leader of innovations.

Cloud solution architects and DevOps engineers want to have a faster conversion from idea to product. What if there would be a way to draw an architecture online and get the infrastructure for it implemented as code automatically. This is the reality.

Whether you are just starting out as a technician, a help desk associate, developer or an operations engineer, everyone wants to grow and advance their careers. This talk shows you how to intentionally advance your career one day at a time.

The second Ignite Talk theme: “How High Availability Works in SQL Server”.

Running mission-critical SQL Server databases requires an understanding of the underlying infrastructure in order to meet high availability requirements. But all high availability solutions confuse us with their complexities. This talk shows you how high availability works in SQL Server in simple every day terms that we all could understand.

I want to give a brief overview of Azure Boards, Azure Repos, Azure Test Plans and Azure Artifacts. And explain mode deep about Azure Pipelines what is available in a free and paid subscription. Also, give a demo example of how to set up CI/CD and integration with Github and Azure.

Everyone or almost anyone relies on monitoring to prevent saturation and disk overload, as well as to manage other crucial metrics and stats about a specific app or the entire system. With advance of public cloud, however, DevOps engineers should now consistently take care of spinning the resources up or down, since every sec of time and every bit of data impacts your app’s agility. In this talk, let’s dig into the capabilities of monitoring on AWS, from an infrastructure monitoring and cost savings standpoint.