How is it possible not only to develop software efficiently, but also to create real added value for the customer?

And the endless number of so-called “silver bullets” that have been touted over the years: new languages, new process models, none of them able to guarantee successful software solutions alone. Additionally, many miscon- ceptions have accompanied software development over the years, like giving re-use absolute priority. Or forgetting time and budget in the quest for “flexibility”.

This book discusses implementing and using DevOps which is just about the opposite of a “silver bullet”. The DevOps mindset tears down organiza- tional and mental silos to provide an end-to-end view of software delivery. The author shows that DevOps significantly improves software delivery, and he does this in a pragmatic way by giving many real-life examples from his 40-years of software development. These examples include not only technical and process know-how, but they let us understand the social and business context and the constraints we face when delivering software. And according to the author, we can do so even in complex multi-party and multi-contract situations, where the social components of DevOps really show their value.

An important trait of a more professional attitude is the constant reflection about how we can improve our way of working in such a way, that we are not only in a reactive mode anymore. We rather strive to achieve a mode of working, where we are better prepared, not only for bad things we already know will happen sooner or later. But we also like to be in better shape for the “unknown unknowns”, i.e., events we do not expect. The journeyman is always alert to recognize an unexpected situation. We look at a few ideas how to be better prepared for whatever may come our way.

I have been working in software development for around 20 years – initially in development itself and, for the last few years, in project management.

In his book “DevOps Mindset in Software Development, From Apprentice to Journeyman,” Bernhard Scheffold describes everyday situations in software development in his charming way. In addition to many excellent practical examples, you also get lots of very good approaches such as “feature toggles” or why you need a “power user” in every project.

However, the book is by no means a manual on how certain processes should/must be mapped. Rather, it is a very successful attempt to sharpen the participants' focus on the topic of “DevOps” so that we can all work better together and not past each other or even against each other.

I often found myself nodding in agreement when a particular situation was described. I had already experienced this in a very similar form myself, and the conclusions drawn are very helpful and understandable. This book is therefore the perfect travel companion on the journey “From Apprentice to Journeyman.”

And as always, “a statement ‘it does not work’ does not count!”

This subject matter book fully deserves the 5 stars, and it will be my pleasure to explain my opinion on this.

Dr Scheffold did not just create a braindump but provided a clear and easy-to-follow structure. Still, you can literally feel the raw, pure experience contained in every sentence. This book is not fiction; this book takes an unapologetic look at the development process, dissects it piece by piece and then draws a graphic picture, which should be understandable even at the apprentice level.

After explaining the nature of the beast, the many ways in which the DevOps methodologies can be used to tame it are very well explained.

It should be noted that the clear focus of the book is on personal development, and this leads my review to one of the parts which I love most about DevOps: you can do it just by yourself!

Yes, of course, the outcomes to gain if a company-wide culture change takes place and the benefits you get when combining Agile with DevOps are undeniable.

But while you cannot really work Agile just on your own, with DevOps you have tools that you can easily start implementing even in isolation.

It goes without saying that any and all mentions of books, tools and methodologies are referenced and can be looked up to deepen the knowledge in any of the mentioned topics.

Even if non-developers might not be the main target group, this book should be able to provide everyone who is interested in DevOps with precious gems of insight.

After that much well-deserved praise, let me finish this review with a battle cry stolen out of the book: "Resist Muda!"

As a senior software developer, I am increasingly recognizing how crucial it is to understand all phases in their interplay—from development to deployment to operation. I already had some initial exposure to DevOps, but wanted to deepen my knowledge.

The book clearly describes the path from an attitude of “software operation is not my problem” to a mindset of “I am prepared for anything.” On a technical, personal, and organizational level, the book offers an impressive collection of starting points – practical, compact, and with many well-placed cross-references. The chapters are mostly quick to read, as they are not too deep without appearing superficial. Those who want to delve deeper will find numerous excellent sources for further reading via the references.

I particularly liked the strong practical relevance and numerous examples – offering insights and advice that usually only emerge after many years of real-world practice.

The book is written from the perspective of a developer in the e-commerce project business with external customers. This certainly makes it particularly instructive for this target group – but I also learned a lot from other perspectives.

Conclusion: A well-thought-out reference book that shows in a practical and structured way how the DevOps evolution can take place on a technical, organizational, cultural, and personal level. Through many small impulses, it invites reflection on one's own way of working. A clear recommendation for everyone – not just developers – who wants to understand why software development is more successful when it is thought of holistically and implemented with more responsibility.

This book will not teach you how to implement DevOps in your company, nor will it provide you with a step-by-step guide. Instead, it focuses on something more fundamental: understanding how to create real value for your customers using software.

As someone at the beginning of my journey to becoming a better software developer, I learnt a lot from this book. The author shares many personal experiences and shows how a change in mindset can positively influence a project.

The book is written in a very accessible way, making it easy to read and follow. I believe it is valuable not only for beginners like me, but also for experienced developers who want to reflect on how they approach building software. Beyond that, I think project managers can also benefit from the ideas presented here, since it provides a broader perspective on what really drives successful projects.

In short: an inspiring and insightful read that I can wholeheartedly recommend to developers and project managers alike.

I am in software development for 25 years, and I really enjoyed this read. "DevOps Mindset" is one of the few books that gets it right and, undistracted by industry trends, focuses on what actually works.

The book correctly frames the entire challenge of DevOps delivery as a shift in an individual's mindset and the broader culture, not just a change of your toolbelt. It's built on a clear foundation: improving your personal workflow, shortening feedback loops, and committing to constant refinement.

I best like the metaphor of the "journeyman" as a practical model for a person's professional growth: from a junior developer reacting to problems to a senior leader who "architects" and values preparedness.

There is nothing hyped or fluffy here. It's a pragmatic guide for any serious engineer looking to advance their thinking. I highly recommend.

This book clearly deserves five stars. While reading, you very quickly realize that Dr. Scheffold is not a theorist, but a man of practice with vast experience. The examples given don’t get lost in technical details; instead, they show that DevOps is far more than just developing, delivering, and running software. Reading it feels like having a conversation with a good friend over a coffee or a glass of wine, philosophizing about DevOps. Absolutely worth reading!

I can only recommend it!

Scheffold doesn't beat around the bush, and for once it was necessary for someone to hit the table. Much of what is popular with inexperienced coders is, on closer inspection, rubbish. Software must run reliably as a top priority. If it also runs in a resource-saving way, that's the icing on the cake. Does it also have to be sexy? No! At least not if it costs even one mu in security.

I had to read through a few bookshops just to come to this conclusion - so thank you!

DevOps Mindset in Software Development by Dr. Bernhard Scheffold is one of those rare books that blends deep professional experience with clear, relatable storytelling. The book doesn’t just lecture you about the DevOps principles — it is a journey from “apprentice” to “journeyman,” illustrating each concept with real-world examples from decades in the field.

The book stands out because it treats DevOps not as a job title or a toolset, but as an organizational culture and personal mindset shift. Scheffold emphasizes that successful software delivery is as much about communication, responsibility, and customer value as it is about automation pipelines and infrastructure as code.

What I especially appreciated was:

• The Three Pillars of DevOps (Flow, Feedback, Continuous Improvement) explained with practical steps and pitfalls to avoid.
• The “journey” structure—from ignorance, to awareness, to reactivity, to preparedness—makes the lessons easy to absorb and apply.
• Numerous case studies and anecdotes that show how DevOps plays out in real organizations, including the social and business challenges.
• A balanced view on AI in development—neither overly hyped nor dismissive, but realistic about its strengths and limitations.
• Concrete techniques for testing, monitoring, and improving both systems and team collaboration.

Unlike many technical books, this one speaks to developers, managers, and operations professionals alike. Its tone is pragmatic, engaging, and refreshingly free of jargon for jargon’s sake. By the end, you feel motivated to not just adopt DevOps tools, but to live the DevOps mindset—building bridges across teams, focusing on delivering real value, and continually learning.

I personally like this quote "don't try to make it cool" - because usually a developer who tries to make it cool, makes it worse and less stable.

So, if you’re serious about improving how software gets delivered in your organization—or in your own career—this book is a must-read. It’s the perfect mix of practical guidance, cultural insight, and long-term vision.