#Engineering-Excellence

Companies might fall into the trap to believe that developer experience is a nice-to-have luxury rather than a necessity. However, this is not the case. High developer productivity results from a great developer experience and thus, the companies' success ultimately relies on this.

Developer experience is a crucial topic which affects all development teams of a company. Therefore, it can be beneficial to introduce a team that has as their only mission to improve developer experience and productivity as these improvements multiply the impact of the other teams.

Whether a team works synchronous or asynchronous is not determined by whether it is co-located or not. Both teams have to make an effort, if they want their work to be synchronous.

Objectives and key results are a great tool for collaborative goal-setting and for aligned on a company-wide direction. Problems start, when teams start to rely on other teams OKRs to be finished in time.

Blameless post-mortems are an effective tool to facilitate learning from failures, to share knowledge and to significantly improve the entire system, including software, infrastructure, and processes.

Keeping people 100% busy will prevent them from innovating and improving. Therefore, teams should have slack that enables the to learn, adapt and improve.

In this article I will share details about our last focus week and how it led to a breakthrough on a difficult topic.

Focus weeks are a tool for cracking difficult or complex topics as a team while fostering team collaboration and improving team culture.

When moving towards a more continuous software delivery process, focus on evolving the culture instead of just automating the processes.

Walls in your deployment process block value-flow and slow-down feedback cycles. Here is how you can detect and remove them.