Project Myopia: Why Projects Damage Software #NoProjects
$0.99
Price: $0.99
(as of Nov 04, 2024 06:59:53 UTC – Details)
Projects fail. Some say 40 percent of all IT projects fail, some say 70 percent. And it has been that way for years.
Each project fails for its own reasons but they all share one thing in common: the project model. Could it be the project model itself which creates failure?
In this tour de force Allan Kelly explains why the project model is a poor fit for managing software development. Working from industry-recognized definitions of projects, he describes how the model deviates from reality then goes on to discuss:
Why focusing on time, scope, and cost damages software, creates goal displacement, and reduces quality How projects miss the bigger picture Why maximizing value demands work across projects When debt is good and how projects increase technical debt to the detriment of value delivery The false projects and conflicts that arise when companies apply the language of projects to continuing work
Projects end. Successful software continues. Twenty-first-century digital businesses want to continue and grow.
11 reviews for Project Myopia: Why Projects Damage Software #NoProjects
Add a review
You must be logged in to post a review.
Thorbjorn Sigberg –
A compelling argument for moving your organization away from projects and towards agile
Allan Kelly has been a valuable contributor to the agile community for a very long time. In this book he is dissecting the use of projects as a carrier for software development. It is written as a critique, and Kelly presents compelling and indisputable arguments for why delivering software through projects spawn a range of dysfunctions and unintended side effects.As I am currently part of an ongoing agile transformation, reading this book was good timing. It has helped me articulate why we should move away from projects and towards stable, long-lived teams in a clear and believable way.
Amazon Customer –
Good one
Good point of view on why projects are dangerous. Good samples and rationale behind it. Every engineer manager should read it.
Gwendal TANGUY –
This book identify many invisible problems with visible consequences…
I work for 20 years now in the software+banking industry.There, we are used to get satisfaction when “we deliver project success within deadlines”and in consequence we deserve some amazing “project celebration party”/rewards!Satisfaction, in case of success……otherwise shame, dishonor and sometimes good reason to change company because you felt that project failure was not your fault.Well, if you read this book, be ready to put a step back and consider the overall situation with different eyes.In fact you will be convinced that (software) industry is moving faster than the (often agile) work organization culture around you.What is excellent with this book is that you will have clear answers to some questions like : – Projects have deadline, not your products : where is the problem? – Diseconomies of scale : are you kidding? – Capture value : of course, but how?and a lot more…This book will help you to identify the invisible barriers around you, so be ready to start a cultural change to tackle them.Few months ago, I also had the chance to see how enthusiast Allan is to discuss specific company organizations to enrich his own catalog of problems / situations.For me, value of this book comes from Allan “patterns recognition” capacities, he is definitely a master in that field.I warmly recommend this book, it provides the excellent feeling to be less nearsighted about projects.
Woody Zuill –
I heartily recommend this book for everyone involved in software development
I heartily recommend this book.Allan has done a great job of gathering together his thinking on managing software development. In a nutshell: the prevalent approach to creating software as a “project” with a beginning and end is a poor match to the nature of software development. He supports this theory on a number of fronts, and provides examples comparing and contrasting “project” thinking with the reality of software creation.Project Myopia forms a foundation that can help us better understand why so much of what we currently do isn’t working well for us and is often destroying our chance at success. This thinking is important to everyone involved in software development.In this book Allan lays out the reasons we need a better way. He neatly takes us from the current state of project based software development, shows us why this isn’t working, brings us into the space where we can consider alternatives, and prepares us for moving into the future of software development he calls “Continuous Digital” (which he covers in a follow on book called “Continuous Digital, an Agile Alternative to Projects”.)I’ve been reading and following Allan’s work through his other books, on-line recordings of his conference talks, blog posts and articles, and from live conference presentations. I appreciate his clear and practical thinking as well has his willingness to question the status quo. This book is a bargain and should be read by everyone involved in software development.
Jeremy Jarrell –
Great book to introduce you to challenges of projects
This is a great book for understanding the limitations of projects and how those limitations most often manifest in a digital age.Cutting through the oft-cited #NoProjects hashtag, Allan Kelly provides an honest appraisal of the project model and the challenges that it poses to today’s projects. Understanding these challenges, and how they can be addressed, begins to paint a picture of what solutions might already be at our fingertips, even when those solutions may be surprising.If you’re interested in better understanding the limitations of a project model and what alternatives might exist, then this is a great place to start.
Evan Leybourn – Author of #noprojects; a Culture of Continuous Value –
Projects are a 20th century invention that has outlived it’s usefulness
Project Myopia is a must-read for anyone involved in planning or running digital projects. Allan puts forward clear and compelling reasons why the project model has outlived its usefulness in the creation of software products; from the history of project failure over the last 30 years to the rise of agile and continuous delivery. This book is a critique, yet one argued with logic and passion.Allan Kelly’s work has been an inspiration to me and many others. Make sure you also read Continuous Digital, the second part of this series, to discover the alternatives.
Victor González –
Si eres PRoject Manager trabajando en entornos agiles lo tienes que leer. Tiene algunas partes aburridas. Se preocupa más por aclarar porque no funciona la gestión tradicional qué a comentar la transición entre cambio de mentalidad de proyecto a producto.
Carlo –
I did not like the book.I found it confusing and in some cases I didn’t agree with some thesis.However there are some good ideas so I saved to three stars
Ewan Milne –
The project model does not fit the reality of managing software development. In this bracingly short book Allan provides an eloquent critique, landing his points well without waffle.Read this then the companion volume, Continuous Digital, which provides practical solutions to the problems uncovered here.
sonila das –
New concepts elaborated in simple manner. Have not completed the whole book. Will able to post review once I complete.
Bronek Kozicki –
If you are managing programmers, working with them directly or indirectly, or recently joined the profession, it is a must read. It explains how the maximise the value of the programmers work in the enterprise large or small, and how to avoid the trap of long-term planning in a world where the only constant is change.