Kick off your book project in 3 hours! Live workshop on Zoom. You’ll leave with a real book project, progress on your first chapter, and a clear plan to keep going. Saturday, June 6, 2026. Learn more…

Leanpub Header

Skip to main content
Leanpub Launch Videos Cover Art

Leanpub Launch Videos

Authors launch their books on the Leanpub YouTube channel.

About

Every Leanpub Book Launch video celebrates a newly published book. Watch the launch announcements and discover your next read — straight from the authors.

Watch

Fixing Software Delivery

Max Guernsey, III

Description

Fixing Software Delivery

About the Book

Fix Software Delivery Problems without Wasting Time This book presents common software delivery failures and how to resolve them. No filler, anecdotes, or unnecessary theory. Each topic is a short, standalone executive brief (1-2 pages). Start with the introduction, then go directly to the problem you're facing. Read what you need. Skip what you don't.

About the Author

Max Guernsey, III Max has over three decades of experience as a software engineer, architect, and consultant. For more than a decade, he has helped leaders diagnose and remove the root causes of software delivery problems. --- Luniel de Beer Luniel de Beer is a software product and delivery systems architect focused on the structural causes of failure in modern software development. His work centers on how software is defined, validated, and made ready for execution before it is built. He is the author of *Ready: Why Most Software Projects Fail and How to Fix It*, and the creator of the Requirements Maturation Flow (RMF), PKB-Driven Development (PKBDD), and Producore’s Capability Management system—an integrated body of work designed to replace informal requirements and fragmented collaboration with structured, persistent product knowledge, enforced readiness, and end-to-end traceability. Luniel works at the intersection of product, engineering, and delivery, helping organizations establish clarity, accountability, and control across teams and systems. His work challenges conventional approaches to Agile and requirements by addressing the missing foundations that prevent software from being consistently understood before execution begins.