Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? Engineering is the application of iterative, empirical, practical science to real-world problems. Craftsmanship is a wonderful thing, and as a reaction to the terrible abuses of the term Engineering in software development Software Craftsmanship has helped in our learning of what really works.

The term "Software Engineering" has gained a bad reputation. It implies "Big up-front design" and "Mathematically provable models" in place of working code. However, that is down to our interpretation, not a problem with "Engineering" as a discipline.

In recent years we have discovered what really works in software development. Not everyone practices approaches like Continuous Delivery, but it is widely seen as representing the current state-of-the-art in software development. This is because at its root CD is about the application of an iterative, practical, empirical, maybe even science based approach to solving problems in software development. Is this a form of software engineering?

Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering, neither is Electrical Engineering. Engineering is different in different disciplines. Maybe it is time for us to begin thinking about retrieving the term "Software Engineering" maybe it is time to define what our "Engineering" discipline should entail.

The first decade of DevOps is over. In this presentation, we will look at some of the ideas needed to enhance the movement in the next decade.

How Servirtium use could smooth your integration woes

Everyone else is better than me better than me. I am not as good as people think I am and am going to be found out”. Is this what you feel too? If yes, then you are an imposter. To build a highly engaged and committed workforce, it’s important to focus on every employee of the organization, understand their behaviors and ensure it aligns to the overall culture of the organization. We all have different motivators; however, all people have a basic human need to feel valued and appreciated. Imposter syndrome can be one of the general and significant aspects that could prevent people in the organization to achieve their full potential impacting it from developing a high performing culture. The intent of this talk is to highlight importance to identify people in teams with Imposter syndrome and help them overcome in order to build high performing teams that help organizations thrive.

Software development methodologies often lack the details of how UX fits into projects. Some suggest that a Product Manager describing features is enough for developers, UX should train others to do their specialized jobs, or excluding UX experts solves them being “too siloed” and “not collaborative.” This happens with no other role in software dev; it’s hurting culture, efficiency, and productivity, and creating poor products for customers.

Your customer only sees your UX, not 1000 developers or if you were Agile or Lean. Companies are figuring out that UX specialists and the User-Centered Design process are good investments that more than pay for themselves. Recent highly-publicized UX failures remind us that skimping on the UX process can alienate customers, create negative media attention, and burn millions of dollars.

Learn how the UX process fits into Lean and Agile; augments software dev goals; increases customer satisfaction; and saves time, money, and sanity before developers write a line of code.

Do you want to know what this Docker buzz is all about? Do you want to hear a zero to a not-so-hero story (with demos) from a real human being who learned docker while putting a product out on production? Do you want to avoid the mistakes that this person did in his journey and save (quite) a lot of time? Oh yes, do you want to know how to do all this, keeping your technical agility intact? If yes, then this session is for you. This will be a keyboard-driven demo/re-enactment session with a live storytelling of how to put a product out in the production using containerization and the learning gained from this endeavor.

Do you want to know what this Docker buzz is all about? Do you want to hear a zero to a not-so-hero story (with demos) from a real human being who learned docker while putting a product out on production? Do you want to avoid the mistakes that this person did in his journey and save (quite) a lot of time? Oh yes, do you want to know how to do all this, keeping your technical agility intact? If yes, then this session is for you. This will be a keyboard-driven demo/re-enactment session with a live storytelling of how to put a product out in the production using containerization and the learning gained from this endeavor.

While not adapting to "Being Agile" with a change in the mindset to approach the problem solving was a big mistake in the pre-COVID state, today in the COVID state and tomorrow in the post-COVID state, this attitude shall be suicidal. Organizations that believe in delivering solutions with the frameworks and approaches build ion the 1960s and 1970s era are bound to be wiped out of the industry shortly. In my talk, I shall share with you the three big challenges the enterprises are facing today and also a quick thought on how to approach the problem. I shall provide you the toolset and skillset and it is the leaders and the individuals who need to change their mindset.

Test driving Machine Learning (ML) based software systems have always been a challenge to TDD and ATDD practitioners. In this talk, we will investigate one such approach that will make an AI software developer's job at ease by enabling her to drive the development guided by test. The key challenge for testing ML-based systems is the introduction of a new variable “the model” along with code. In conventional software, the output of a system is the function of the code, wherein in the case of an ML-based system, the output of the system is a function of the code and model. This means the output of that system can change by only changing the model and models these days are designed to continuously evolve. This would mean traditional state testing methods will not work as the tests need to be modified every time the model changed. In this talk, we will explore one such strategy that will enable developers to overcome the dilemma of how to test drive my ML-based software system.

Google did it again. They gave us another buzzword that is changing how organizations operate. Site Reliability Engineer (SRE) is both a strategy and in some organizations brand new function that helps complete the DevOps lifecycle. In this session we will talk about how the SRE function is changing the way organizations think about on-call and completing the DevOps feedback loop from prod to plan. We will cover:

1) The rise of the SRE role.
2) How the SRE function is not rooted in monitoring and ops anymore.
3) How high-performing teams are leveraging SRE to advance their delivery chain.
4) What modern on-call looks like.
5) Best practices and Considerations.

If you are in IT operations, development, SRE or DevOps this talk will help frame the overall objectives and responsibilities of the SRE function, and new ways to approach on-call.

On one side we see a sharp rise in adoption of agile in terms of processes, ceremonies and roles, on the other side when it comes to strategy and goal setting the waterfall command & control mindset is still the norm.

Most organizations are still using an annual, waterfall, top-down process to create a static set of goals that conflicts directly with Agile. The process is even called "cascading goals" - you can't get more waterfall than that.

This webinar is going to highlight the importance of Objectives & Key Results (OKR). This webinar will help you to understand the method and the framework in detail and show why it is so successful in times of digital transformation.

1. What is OKR? Why is it so popular nowadays?
2. How is different then KPI? Who uses it?
3. How does it work?
4. How to write OKR? How do you set good OKRs example
5. How do we measure it or score it?
6. OKRs in a large scale agile transformation?

Do you know why you should develop  code using Test Driven Development? Maybe you even do TDD but have forgotten some of the benefits it brings. Lancer Kind, an Agile Coach from Asia and the US will take you through his TDD challenge which will test your understanding of the benefits of TDD. During this talk he’ll demonstrate some benefits using software he calls the TDD Convincer. The winner of the challenge wins a copy of his action thriller, Agile Noir: https://pothi.com/pothi/book/lancer-kind-agile-noir

DevSecOps derives its own name from being an amalgamation of formerly three separate common teams within most IT organizations, Development, Security and Operations. With the onslaught of new technologies and methods to build, deploy and secure such solutions, it's become paramount to unite and streamline these traditionally separate activities. This doesn't come without its own set of challenges; from turf wars to knowledge and abilities, with most of the effort trying to wed-up the right puzzle pieces to ensure overall team successes.

There’s also no success in this area given to a group of “rock stars” or “prima donnas” but more from “roadies” and “sidemen” who work to make sure the whole show is going to be good rather than try to take center stage. Finding, identifying, and nurturing the staff and talent that is willing to work through the change not only within the IT organization, but are also ambassadors to the rest of the organization to help them through the new ways of exploiting the new ways of integrating technology into business.

Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns or mistakes. It is one of the widely used topics. In this talk, we will talk about What is Psychological Safety and What it is not? Why is it important to measure and improve the same? Practical experience sharing of building Psychological Safety in an Agile Transformation engagement.

Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns or mistakes. It is one of the widely used topics. In this talk, we will talk about What is Psychological Safety and What it is not? Why is it important to measure and improve the same? Practical experience sharing of building Psychological Safety in an Agile Transformation engagement.

Emergent Architecture is an art of designing applications where technical decisions are empirical and just enough. The design should emerge over time that remains flexible yet robust. In this talk we will share good design principles, engineering practices, and tools that helped us in keeping the architecture emergent.

Emergent Architecture is an art of designing applications where technical decisions are empirical and just enough. The design should emerge over time that remains flexible yet robust. In this talk we will share good design principles, engineering practices, and tools that helped us in keeping the architecture emergent.

Development platform for Kubernetes applications.

Build better applications by developing and testing your code directly in Kubernetes.

At its core, Design Thinking is Agile. Through rapid validated learning cycles, teams uncover and understand customer needs, test hypotheses and gain new insights. With each iteration, teams increase their confidence they are building the right thing and building it right.

The Customer is central to the Agile Manifesto. Yet in some organizations, the process of defining what to build and how to build it remains surprisingly removed from the very customers they are serving.

In this webinar, participants will learn about the value of Design Thinking, the Design Thinking cycle and mindset, see examples of how Design Thinking is used in various organizations and ideas for getting started.

1. What is Design Thinking? Why has it become so popular?
2. What is the business value of Design Thinking?
3. How does Design Thinking work?
4. How does Design Thinking connect to Agile Software development?
5. Where do we start?

Domain Driven Design (DDD) is the most useful approach for software development where the needs are complex as it helps connect the implementation to an evolving model of the core business concepts.

My talk is about introducing DDD – taking the audience through how DDD can be their best friend when it comes to designing products with the domain in primary focus – to create products which customers love!

Kubernetes has become the de facto Container orchestration platform over the last few years. For all the power and the scale that Kubernetes provides, it's still a complex platform to configure and manage. Managed Kubernetes service like GKE takes a lot of the pain out in managing Kubernetes. When we are using Kubernetes in production, it makes sense to follow the best practises around distributed system development targeted towards Kubernetes. In this session, I will talk about Kubernetes and GKE best practices around infrastructure, security and applications with specific focus on day-2 operations.