* No other writer on the popular topic of Agile methods and software development methods has identified project management’s best practices as a cause of software project failure. The analysis clearly shows how these best practices can create problems for software development projects. * The book assumes no technical knowledge, and is accessible to businesspeople―project managers, executives and customers―who may know nothing about software development. This book is geared towards a wide group of IT professionals and decision makers working in 2005. * This book is not just theoretical. The detailed case studies included make the material come to life. They illustrate how methodology choices influence the success or failure of software development projects.
ترجمه چندان روانی نداشت. اگر چه مسایل مطرح شده خیلی بدیهی بود . ضعف اصلی کتاب بیان نکردن مثالهای متنوع بود. موضوع پیچیده ای مثل مهندسی نرم افزار و انواع روشهای پیاده سازی نیاز به ذکر مثال دارد.
من نسخه این کتاب در نرم افزار طاقچه را مطالعه کردم، نسخه ای که من مطالعه کردم دارای اشتباه های تایپی زیادی بود که گاهی باعث دل زدگی خواننده می شد و همچنین نداشتن پانوشت مناسب برای واژه های تخصصی فهم موضوع را سخت تر می کرد. شاید بتوان گفت در ترجمه هم گاهی کم لطفی شده و آنچنان که باید ترجمه خوبی انجام نشده است.
A wonderful book about the better way in managing software projects. It introduces the difference between managing tangible projects such as (road projects, building projects ..etc) and intangible projects (i.e. software). If you are related to the IT field and have known PMI project processes for a long time, you have to read this book "Why Software Projects Fail?". You know, there is a better software development methodology than the waterfall model!
Started well, pinpointing how traditional project management contrasts with software development in many "Ah yes!!" ways. Unfortunately, the solutions in the second half don't live up to the outline of the issues in the first as they're really just a light introduction to agile methodologies.