AGS_top100 进口机油 all 200G60 Cloud Drive Photos surfacepro4 surfacepro4 office lamy wacom haocai 亚马逊Fire平板电脑系列 美食黑五 mobile nav_3Mstore nav_3Mstore nav_3Mlvxin nav_3Mpromotion Kindle Family mobile game 乐视自行车 all 施华洛世奇满800减80 国际大牌腕表 满1999减1000 进口直采腕表 满2000减150 首饰清仓 1.3折起 首饰清仓 1.3折起
售价: ¥186.10 (7.8折)
  • 定价: ¥237.14
免运费且可货到付款 详情
前翻 后翻
正在播放... 已暂停   您正在聆听的 Audible 音频版本的样品。

Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure (英语) 精装 – 2011年3月1日

平均4.7 星
5 星
4 星
3 星
2 星
1 星
平均4.7 星 38条美国亚马逊评论 |
| 天天低价·正品质优
| 分享

显示所有 格式和版本 隐藏其他格式和版本
全新品最低价 非全新品最低价
促销信息: 满减 指定原版图书买300减160 共4个促销

全新品2 售价从 ¥186.10
退换承诺: 此商品支持30天免费退换 详情

活动期间内,在活动页领取优惠券后,购买亚马逊指定自营图书(不含礼品卡、电子书、第三方卖家、Z秒杀、Z实惠、海外购及Kindle设备),单笔订单满300元在结账时系统将自动扣减160元,单张订单减免金额不累加,最多减免160元。单品页面“商品促销和特殊优惠”栏中如有此促销信息则表示该商品参与此活动。每张优惠码只能使用一次。本活动开始时间:2015年11月2日09:00:00。结束时间:2015年11月29日23:59:59。 立刻领取优惠券>>

  • 满300元减160元:
  • 满99元减10元:
  • 满99元减10元:
  • 满99元减20元:


  • iPhone/iPad/Mac
  • Android手机或平板电脑



  • 出版社: Amacom (2011年3月1日)
  • 精装: 304页
  • 语种: 英语
  • ISBN: 0814416829
  • 条形码: 9780814416822
  • 商品尺寸: 2.5 x 15.2 x 24.1 cm
  • 商品重量: 544 g
  • ASIN: 0814416829
  • 亚马逊热销商品排名: 图书商品里排第1,532,567名 (查看图书商品销售排行榜)
  •  您想告诉我们您发现了更低的价格?



..". lays out an insightful process, based on real world examples, to identify, prevent and recover from project failure." -"-PM World Journal"


Todd C. Williams, PMP (Camas, WA) is a senior project audit and recovery specialist with over 25 years of international experience.


CONTENTS Acknowledgements xv Foreword by Tom Kendrick xvii Introduction xix PART I Understanding the Process and Realizing a Problem Exists 1 1 The Basics of the Recovery Process 3 2 Management's Responsibility in PART II Auditing the Project: Understanding the Issues 31 3 Assessing the Human Role in Project Failure 33 4 Auditing Scope on a Red Project 49 5 Determining Timeline Constraints 63 6 Examining Technology's Effect on the Project 73 PART III Analyzing the Data: Planning for Project Recovery 81 7 Determining and Initiating Remedial Action 83 8 Building an Extended Project Team 93 9 Considering Options for Realigning Technology 109 10 Assessing How Methodology Affects the Project 119 11 How Agile Methodology Can Assist in a Recovery 131 12 How Critical Chain Methodology Can Assist in a Recovery 157 13 Comparing the Relative Value of Methodologies PART IV Negotiating a Solution: Proposing Workable Resolutions 183 14 Proposing and Getting Agreement on a Recovery Plan 185 15 Dealing with "Unprojects" 205 PART V Executing the New Plan: Implementing the Solutions 213 16 Implementing Corrective Actions and Executing the Plan 215 PART VI Doing It Right the First Time: Avoiding Problems That Lead to Red Projects 221 17 Properly Defining a Project's Initiation 223 18 Assembling the Right Team 231 19 Properly Dealing with Risk 239 20 Implementing Effective Change Management 253 Appendix: Files on the Rescue the Problem Project Web Site 263 Endnotes 265 Recommended Reading 267 Index 269


5 星
4 星
3 星
2 星
1 星

此商品在美国亚马逊上最有用的商品评论 (beta)

美国亚马逊: 38 条评论
6/6 人认为此评论有用
Be smart and learn from your mistakes. Be smarter and learn from other people's mistakes by reading this book 2012年3月2日
评论者 Dr. Thomas Juli - 已在美国亚马逊上发表
版本: 精装
Projects become more prevalent. Not surprisingly the art of project management becomes more popular. Unfortunately this does not imply that the more projects there are the more successful they are. As a matter of fact a significant percentage of projects fail or do not yield the desired results. While in recent years the number of successful projects are on the rise, it is scary how slow this process has been. Todd Williams' book "Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure" is a welcome and much needed aid to help rescue and re-align struggling and failing projects. It is a very valuable resource for anyone working in a project management. Regardless whether or not the own project is on its way to glory or doom.
Williams embraces a holistic approach to project management. He explains the need and value of existing project management tools that help rescue the project management. And he goes beyond the mere listing of tools. In the Introduction of the book he stresses four key factors that are critical in rescuing a problematic project: (1) The answers to a problem in or with a project are in the team. (2) A strong team can surmount most problems. (3) Stay involved with the team. (4) Objective data is your friend, providing the key way out of any situation. By emphasizing the value of the team Williams goes beyond a mechanical "Abhandlung" of a recipe book for project rescues. He explains in simple, plain and thus easy to understand language why most answers to problems in and with a project are rooted in the team. A project is not made up of resources but human beings interacting in a social environment, building communities and network. As complex and complicated this network is, it contains an endless number of potential traps and opportunities at the same time.
Having set up the foundation of his approach to rescuing projects Williams outlines 5 steps to recover struggling projects:
The first step is to realize that a problem exists. As simple as this sounds this may actually be the most difficult step of all. The key is that the awareness of a problem is not limited to the operational level of a project but that management has to acknowledge this fact and expresses an interest in resolving the issue, helping the team to become successful.
The second step to project recovery is an audit of the project. The term "audit" has a negative connotation to many project practitioners. This must not be the case if all audits would follow the guidelines Williams describes in his book. He starts analyzing the human role in a project, followed by reviewing the scope on a red project, determining timeline constraints and examining technology's effect on the project.
The insights gained from the audit analyzed in the third step. They are the ingredients for planning the actual project recovery. To me this part of the book is the most valuable one. Not because the author develops a clean and clear outline effective approaches to analyzing audit data but because he explains how they fit in with the core statement of the book, that a strong team is one of the critical success factors for project recovery. Doing so he stresses that project recovery is not a mechanical task, following a checklist and applying sane project management techniques. Instead he explains that it takes leadership and oversight, a deep understanding of the heart and soul of a project. Acknowledging the fact that more and more projects do not follow the traditional, sequential waterfall approach, Todd Williams gives an overview of other project management frameworks and methodologies, namely Agile and Critical Chain. He then compares them with respect change management needs, customer relationship, estimations, project constraints, subcontractor relations, and team structure.
The fourth step to project recovery is to propose workable resolutions. This is when the recovery manager presents the insights from the audit analysis and concluding mitigations and negotiates the next concrete steps with the project sponsor and stakeholders. Williams stresses the importance of staying focused on project recovery and not getting sidetracked by distractions such as maintenance and other conflicting projects.
Last but not least, the fifth step involves the actual execution of the recovery plan.
As hard, tedious, frustrating and rewarding project recoveries can be one of the key questions is what project managers can learn from past mistakes and successful recoveries. This is covered in the final part of the book entitled "Doing it Right the First Time: Avoiding Problems that Lead to Red Projects". It shows that project failure often starts at the very beginning of the project. It can be prevented by properly defining a project's initiations, assembling the right team, properly dealing with risk and implementing effective change management.
While the book may be most interesting to those who are facing or have faced problem projects I hope that novice project managers read this book, too. It will help them avoid common mistakes and set up a good and solid structure for project success. And in case troubles arise this book will help them guide projects to safer havens.
5/5 人认为此评论有用
Good Stuff 2011年4月23日
评论者 Holli Radmin - 已在美国亚马逊上发表
版本: 精装
This book offers sound advice and guidance in dealing with red projects or those heading in that direction.
Todd offers insightful and sometimes amusing explanations in his case studies. I particularly liked Case Study #3-1 The Stockholm Syndrome. But my favorite was Case Study #8-5 Name the One Thing the Customer Would Love. It never hurts to make me smile while reading something that could, in someone elses hand, be considered dry.
2/2 人认为此评论有用
Much to Learn from the Author's Experience! 2011年9月24日
评论者 Dennis Hull - 已在美国亚马逊上发表
版本: 精装
It is almost certain that an experienced Project Manager has, at one time or another, run up against a project that is over-budget, running late, or otherwise out of control...a project that is "in the red." Rescue the Problem Project by Todd Williams presents methods for recovering red projects, reminds us that recovery is itself a project and provides insights into keeping projects out of the red in the first place.

The book presents suggestions and prescriptions based on the author's 25 year experience as a "Senior Audit and Recovery Specialist" and each chapter is peppered with very readable, brief case studies highlighting examples of his applying the techniques he describes. While there are a few examples that come off as a bit self-aggrandizing all are immensely helpful in understanding how and why the techniques work which provides a degree of credibility lacking in many business books.

A seasoned Project Manager will recognize their own experience as the author notes that poor scope definition, lack of executive leadership, and ineffective change management are barriers to project recovery (and most likely contributed to problems in the first place). And no PM should be surprised at the need to perform an audit and engage with stakeholders to collect data and understand the current and desired states. However the author follows his own prescriptions providing specificity in his examples of how each of these is often done wrong and how to do them right.

It may be unsettling to some PM's to read the suggestion that a specialized, external "Recovery Manager" rather than the Project Manager him or herself is the best person to perform the audit and analysis. The chief argument in favor of this approach is that "An objective view is critical to a proper audit and reducing any preconceptions of a solution." The book notes the potential for resistance to this notion but it seems a reasonable approach and calls to mind the frequently cited Einstein quote that "Problems cannot be solved by the same level of thinking that created them."

The audit is the second of the five steps in the recovery process with the first being the problem realized and the remaining three being analyze data, negotiate solutions, and execute the new plan. The "how to" of each step is well described and the book's companion website provides templates and spreadsheets to assist in rescuing your own projects should your organization decline to hire a recovery manager. Another of the recurring themes of the author's method is to start performing root-cause analysis early and to respond to the findings quickly, "This is a distinguishing feature of my approach; other approaches often omit root-cause analysis or leave it for the end of the process." The reason for this is straightforward...until the root causes are found and mitigated; they are still able to exert the same kind of pressure on the project that put it in the red in the first place.

Identifying and recovering from project failure are not the only goals of the book; prevention is an essential theme to which the last 40 pages are dedicated and again the author's experience proves valuable as he provides details for improvement in, and specific examples of the areas of leadership, team management, risk and handling change. Chapters 10 through 13 are not officially part of the section on prevention but clearly could be. These chapters provide some of the best primers on and comparisons of classical, agile and critical chain methodologies that I've read and I couldn't agree more that when it comes to methodology, "This philosophy--one size fits all--really fits no project." The idea is to treat methodologies as tools in the bag where the marrying of the right methodology to the particular project can go quite a long way toward avoiding problems.

While many of the 261 pages of Rescue the Problem Project present ideas with which an experienced Project Manager is likely familiar, there is much to gain in the detailed examples and the way in which the ideas are presented. New PM's (those who have some education or experience in the field) will certainly benefit as they learn from the author's advice and experience how to prevent projects from going into the red.
2/2 人认为此评论有用
Cleaning Up A Project Mess? Read This In Week One 2012年1月1日
评论者 Christopher Dennis - 已在美国亚马逊上发表
版本: 精装
Hurrah! We now have an insightful book about righting troubled projects from an experienced practitioner. As a fellow project rescuer, I've read a number of other works on this subject. Todd's is the best book in its genre.

It offers level-headed, immediately applicable approaches for anyone who finds themselves cleaning up a project mess. I think the book is especially valuable for people who are dealing with their first project recovery.

I required portions of this book in my Practical Project Management for Leadership course: twenty percent of the participants--folks from five continents--felt it was the most helpful of the assigned readings.
2/2 人认为此评论有用
Nice try 2013年1月23日
评论者 Holly Cooper - 已在美国亚马逊上发表
版本: Kindle电子书
The book was a great idea but fell short on delivery. Too little content and too much repetition. This was geared more toward outside recovery specialists, instead of how a project manager can turn their own project around to get it back on track.


话题 回复 最后发表