| |||||
• polskie
• Zamów informacje o nowościach z wybranego tematu • kontakt |
PROJECT MANAGEMENT ADVISORPACELLI L.wydawnictwo: PEARSON, 2005, wydanie Icena netto: Any of these sound familiar??? A critical project task that quickly gets to 90%complete and takes forever to get the last 10% done You Are about to release your product and a stakeholderthat wasn't involved in the design jumps up and down and causes significantproduct rework Your project team spends more time fighting andfinger-pointing than working together to get the project done. As an experienced project manager,chances are you've experienced some of the above situations at least once and canprobably add several of your own bullets to the list. If so, then I think you'll enjoy The Project ManagementAdvisor. In my 20 years experience inrunning projects as a consultant, project manager and business owner, I'm proudto say that I've experienced many project successes. But strangely enough, it's the failures that stick at the forefront of my mind and it's those projectsthat I think about whenever I'm starting up a new project. I'm bound and determined not to repeatmistakes that I've made on prior projects. I so clearly remember that touching a hot stove hurts justas much the second time as it did the first time. Nonetheless, I've been back to that stove numerous timesover the yearsÉand have the scars to prove it! As a fellow project managementpractitioner, I wanted to write a book specifically for the experienced projectmanager that understands the fundamentals of project management but wouldbenefit from tips on how to make projects more successful. In writing this book, I wanted todesign it to be something that a project manager doesn't just read once and puton a shelf to forever gather dust. I wanted to design it so that you could refer back to it time and timeagain depending on the specific challenges that you will be facing on yourparticular project. Each chapter of the book centersaround a common project failure to help you avoid some of the wasted time,pain, and expense that comes with a failed project. Each chapter is organized with icons to help you navigate thechapter and find things quickly. An <<<insert question icon here>>> icon is usedwherever I explain why the failure occurs. An <<<insert warning sign icon here>>> isused wherever I explain the warning signs that you should be looking for whichsignal that failure is approaching. An <<<insert U-turn icon here>>> is used wherever Iexplain what you could do to turn the situation around if you start seeingwarning signs. In addition to being an experiencedpractitioner, I am also an eager student of the art of project management andhave found that I've been able to learn something from every project that I've participated in or lead. I'd loveto hear what you have to say about the tips in this book, where they havehelped you, what war stories youŐve been through, and also where you disagreewith me. Tell me what you think bygoing to my website at www.projectmanagementadvisor.comand telling me your story. I sincerely hope that you enjoy TheProject Management Advisor as much as Ienjoyed writing it. Surely some ofthe project failures will resonate with you and I hope that you are able totake away some helpful nuggets that you are able to use in your projects. Table of Contents Preface. Acknowledgements. 1. We Weren't Addressing the Right Problem. 2. We Designed the Wrong Thing. 3. We Used the Wrong Technology. 4. We Didn't Do a Good Project Schedule. 5. We Didn't Have the Right Sponsorship. 6. The Team Didn't Gel. 7. We Didn't Involve the Right People. 8. We Didn't Communicate What We Were Doing. 9. We Didn't Pay Attention to Project Risks and Management Issues. 10. The Project Cost Much More Than Expected. 11. We Didn't Understand and Report Progress against the Plan. 12. We Tried to Do Too Much. 13. We Didn't Do Enough Testing. 14. We Weren't Effective at Training the Customer. 15. We Didn't Pull the Plug on the Project When We Should Have. 16. We Tripped at the Finish Line. 17. The Vendor Didn't Deliver. 18. We Had No Fallback Position in Case the Product Failed. Wrapping It Up 167 pages
Po otrzymaniu zamówienia poinformujemy pocztą e-mail lub telefonicznie, |
