Siemens Healthineers engaged Philipp and Vlad due to growing challenges with their platform. As more users started using the platform, the availability requirements increased, and they wanted to reduce downtime. However, their current operations capabilities did not allow them to achieve the uptime and availability needed, and there was also a problem with the time it took to recover from failures. To address these challenges, Siemens Healthineers decided to adopt SRE as a solution to improve their operations and increase reliability. The adoption of SRE was added to the list of big initiatives, and Vlad and Philipp worked through the organization to get buy-in and support for the change.
For some, it might seem hard enough to release once per month (12 times a year). However, this particular company is releasing every week of the year (52) and some extra releases when necessary, taking them up to 68 unique releases in a year.
They can do this (mostly) transparently to the end customers, but also release major features that their organization uses in promoting the product.
Listen in to learn how Charles Oppermann has helped his organization reach that level of frequent deliveries, even with multiple hard dependencies and a team that can go up to 60+ people involved in the development and release process.
About Charles Oppermann
Charles Oppermann is a 30-year veteran of the software industry. He prides himself on shipping high-quality software that helps humanity; from the JAWS screen reader and making the internet accessible to people with disabilities while at Microsoft, and for the past decade; protecting people from online threats at Malwarebytes.
This is a BONUS episode on the topic of #NoEstimates. The Agile Wire podcast hosts Jeff Bubolz and Jeff Maleski interview Vasco Duarte.
Some of you might have heard about #NoEstimates, and want to know more, and for others, it might be the first time you hear about it. Either way, in this episode we talk about the origins of #NoEstimates and why you may want to consider it when helping your teams.
This is a shared episode with a fellow Agile podcast The Agile Wire, where hosts Jeff Maleski and Jeff Bubolz interview Agile practitioners. Both Jeff Maleski and Jeff Bubolz have been guests here on the Scrum Master Toolbox podcast.
About Jeff Bubolz and Jeff Maleski
Jeff Bubolz is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.
Jeff Maleski is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.
You can link with Jeff Maleski on LinkedIn.
From her early start with Extreme Programming to learning how to integrate testing with Continous Delivery, we explore Leena’s story and describe some of the most important lessons she collected about adopting CD/CI.
Read on to learn what were Leena’s main lessons, as well as the main challenges teams face when adopting CD/CI.
Wouter started his Continuous Delivery journey as an Extreme Programmer in his first years of engineering experience. He shares the story of how, as a team, they sat together with the operations department to learn how they developed their software. Thanks to that, they radically changed their build system to export the kind of packages that operations needed. A brilliant story that also illustrates the adage: “Your first customer is the next step in the process!”
Read more to learn why testing is such a key skill and technical area when adopting Continuous Delivery.