Mark Levison recently wrote a blog on “Scrum Alone is Not Enough”, which is the first blog of a series to uncover various Agile patterns. Till now he has published blogs on Kanban Portfolio View and Portfolio Management in the series.
This article features highlights from interviews with release engineers on the state of the practice and challenges in release engineering space. The interview questions cover topics like release engineering metrics, continuous delivery's benefits and limitations.
Sriram Narayan’s book – Agile IT Organization Design, provides a basis for reviewing and reshaping the IT organization to equip it better for the digital age.
The book Devops in Practice: Reliable and automated software delivery by Danilo Sato provides a hands-on approach for implementing continuous delivery and DevOps practices.
This article contains an extensive interview on the microservices adoption process, the benefits and difficulties of implementing microservices, with representatives from Gilt, Hailo and nearForm. 5
Book author Paul Swartout shares his view on cultural challenges to DevOps adoption and how the rise of mobile and microservices impacts Continuous Delivery approaches, among other topics.
Dean Leffingwell’s “Leading SAFe LiveLessons” - training videos are based on Lean-Agile transformation concepts at enterprise level.
An interview with Craig Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility.
Finding ways to eliminate root causes of delays can improve flow. This article discusses clustering blockers and provides ways to prioritize blockers that have most impact or are the quickest wins.
How do you get good flow? A common scenario in a software company is that too much is going on at once. We need a shift in mindset, to go from focus on resource efficiency to focus on flow efficiency.
With talented developers, quality advocates and user-experience designers, teams know how to deliver valuable software. But as we improve service delivery using kanban, who manages flow?
There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We need to change our mindset, and focus on the principles that people follow and values they share.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Blog Series: A skeptic's guide to Continuous Delivery