Evangelizing DevOps and Continuous Delivery in your organization
Did you ever hear about these new things called Continuous Delivery and DevOps? In theory, all sounds so easy and meaningful. In practice, it's often hard to get started, both technically and non-technically, or to extend an existing solution to be robust and sustainable, and to span departments in the best possible way. This session shapes the core aspects of Continuous Delivery and DevOps. We talk about NoOps and deployment artifacts, including gradual log-benchmarked releases and pull-deployment/elastic-scalabillity zero downtime deployments. The main part of this session is the interactively set up example delivery pipeline pointing to good practices, proven in many big and complex project structures. After attending this session, you'll know the difference and interfaces of Continuous Delivery and DevOps, you'll be able to directly apply many recipes, know how to integrate lightweight best-of-breed tools as well as know about common pitfalls to look out for. You'll also be able to decide about what tool to choose, e.g. favor Chef over Puppet, or the other way round, and what's important about binary artifacts and how to make them cloud-enabled.
Outline/Structure of the Talk
What is DevOps
What is Continuous Delivery
How we adopted it and evangelized across the organization
Will be able to understand organizational benefits of DevOps.
How they can go about implementing DevOps in their organization.
People who looking to adopt Dev-Ops and Continuous Delivery
schedule Submitted 4 years ago
People who liked this proposal, also liked:
Richard Sheridan - Build a Workplace People Love – Just add JoyRichard SheridanCEOMenlo Innovations
schedule 4 years agoSold Out!
The CIO invited me into his office and closed the door. Before he took me for a tour of his operation, he had a few stories to share. Important stories. Last year’s project was a disaster. Late, lots of quality issues, in short, a failure in every dimension. His boss, the CEO, had just presented him with a very personal ultimatum: deliver the next project by April 4th, "or else".
"Or else what," I asked?
His team was burned out and scared. They were a hard-working and dedicated group, but fear and demoralization had set in and he didn't know what to do next. That’s why he wanted to talk to me, he had heard things about my company, things that seemed too good to be true, but he had to hear them firsthand. He wanted hope, inspiration, and a practical way to get there.
I told him about my own journey from joy to fear to disillusionment back to joy. It was simple, but, of course, simple isn’t easy. I wasn’t sure he and his organization were ready; "manufactured fear" is a powerful drug.
In this talk, I will share with you what I shared with him. I will explore what an intentionally joyful culture must choose as its focus. I will discuss what joy looks like, feels like, how it is organized. Along the way, you will be confronted by paradoxical approaches of how workplace noise increases productivity, how two people at one computer outperforms hero-based organizations 10-to-1, how rigor and discipline emanate from a shared-belief system, how transparency conquers fear, how all of the disciplines you study including agile, lean, and six sigma when done well are really about building human relationships at the intersections of business and technology, between project management and software development, between development and design and how quality can be a natural result of a team built on trust. This is not a theoretical talk, but rather a talk built from well over a decade of experience of leading a team focused on “the business value of joy”. There will be lots of room for discussion with the audience. The audience will begin to understand why thousands of people make the journey to Ann Arbor, Michigan every year to see The Menlo Software Factory firsthand, and why so many more are reading about it in Joy, Inc. – How We Built A Workplace People Love.
Krzysztof Czajka - How fudge candies catalysed feedback and engagement? Case study of successful experiment.Krzysztof CzajkaAgile CoachAllegro Group Sp. z o.o.
schedule 4 years agoSold Out!
What is it about?
This is a story about building appreciation and feedforward culture in the organization.
I am going to talk about a bottom-up experiment based on Jurgen Appelo's Merit Money, conduced in the biggest e-commerce company in Poland - Allegro Group. It is a story about learning throughout an Agile experiment to get the most out of it. Primarily the experiment was intended to challenge the existing bonus system based on forced ranking. It turned into appreciation and feedback system with some sweets involved.
This feedback system has grown to more that 230 people involved from 3 different physical locations and still grows virally. We made a structure in which there is a coordinator in each location. If at least part of scrum team plays the game, SM is the first line contact. He distributes credits and exchanges them for sweets. Also cooperates with coordinator who is responsible for making sure system works well in his location.
Iterations are now 2 weeks. We introduced a requirement that credit has to be filled in with short description what you thank for, in order to be exchanged. This was to promote written thank you’s and avoid situations where people hand over credits just to get sweets.
Also every quarter we change credits appearance so that the previous credits cannot be exchanged for sweets. This is to set a time box and “flush the system”.
Is it for me?
Do you feel your team could be more engaged in their work? Trying to get rid of silos in your organization? Then this is for you.
Get inspired by this simple game, in which there are several instant feedback loops, fun, gambling and sweet prizes.
Oh, I forgot... and you'll find an answer on why we call it Fudge Candies.
Kamlesh Ravlani - System Optimization by attacking Lean WasteKamlesh RavlaniAgile Coach and TrainerAgile For Growth LLC
schedule 4 years agoSold Out!
Most large scale organizations are designed on the overarching theme of local efficiency and local optimization. Local optimization focus can be seen at all levels and areas in such organizations right from hiring, approach to funding new initiatives, the way people are promoted to higher ranks, etc. Effects of such behavior is visible through organizational silos, hand-offs of partly finished work products among groups of SMEs, single function roles (such as Analyst, QA, etc.), everyone being busy, and communication barriers and distance from real user/customer challenges.
In this workshop, we'll focus on the Software Product Development area of the organizations, identify local optimization, expose the underlying lean wastes and list approaches to optimize the whole system and improve organizational agility.
Kamlesh Ravlani will help attendees see the prevailing local optimization by dissecting planning, analysis and design, and programming areas and will facilitate activities where the participants expose the underlying lean wastes.
Equipped with the knowledge of prevailing lean wastes and resulting local optimization, attendees will learn couple of approaches based on Systems Thinking that solely focus on customer value and remove lean wastes resulting in System Optimization. Attendees will also learn that System optimization also triggers and necessitates re-designing the organization to move away from local optimization in the benefit of the whole system optimization and allowing the organization to be more responsive and agile.
PS: As a reference, Kamlesh Ravlani will bring additional reference material and books for attendees to become aware and later refer to - if interested to learn further on this topic.