Projects fail. Some say 40% of all IT projects fail, some say 70%. And it has been that way for years.Each project fails for its own reasons but they all share one thing in 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 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. and “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. and ” Bronek Kozicki and “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. and ” Ewan MilneAn excellent book which thoughtfully critiques the and “project and ” construct that we have all been conditioned to accept as and “normal and “. This book is thought provoking, explaining Allan’s views and experiences on how and why projects are harming the development of software. This book links in to Allan’s other book and “Continuous Digital and ” (This book provides the critique and rationale, which I believe Continuous Digital builds on).If you work on change projects the that involve, or are driven by, software.. then this book will be for you! It challenges thinking and provokes thought. and ” Adrian Reed and “This book is an excellent exploration of the short-sightedness of the project model for software, and should be essential reading for anyone involved in managing software development, delivery, or operations. and ” Matthew Skelton and “A short, but enjoyable read. Allan covers, categorically, the thinking behind moving away from projects (as per the #noprojects conversation): where it’s appropriate, why it works, and what we can do to move away from it. He defines what he means by a project (or rather uses the definitions defined by PMI and PRINCE2), and categorically dismantles the reasons behind using them in most modern contexts. From arguments of quality to economy, you’ll be left with a solid understanding of why you probably don’t want to use projects, and move towards continuous digital delivery. and ” and “Well-structured, well-argued, and entertaining. A very worthwhile read. and ” Gary F

Project Myopia: Why projects damage software #NoProjects PDF

The list of books you might like