This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.
At LaunchDarkly I have experienced similar intellectual honesty, one of the many facets of our outstanding engineeringculture. There are a few aspects of our company culture that I believe contribute to this, namely empowering employees’ voices and blamelessness. Sessions & Workshops.
You may find that other approaches work better for you, and in reality every workshop is different so you need to be flexible. The following steps are my baseline format for a series of discovery workshops. The scope of the workshop will influence how many levels is necessary. This is a tricky problem for facilitators.
DevOps represents a change in IT culture. Leaders need to be culture builders by carrying the mission and strategy into the team and creating goals. Build the core DevOps team : The core DevOps team must accelerate the culture transformation and support the Agile squads in their adoption. The case for DevOps leadership.
One of the challenges I see regularly is inertia following domain discovery workshops. Choosing where to focus is a balancing act: delivering new products, fixing legacy software, and improving engineeringculture. How do you go from event storm to product and organizational improvements?
Selecting better Open Space sessions. – Informing what type of session it is: workshop, presentation. This tries to set up a base understanding of characteristics that make up a healthy EngineeringCulture. It’s just an analogy to explain the difference with an open space. What I learnt. CQRS/ES in sync mode.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content