The One-Page Project Manager: Communicate and Manage Any Project With a Single Sheet of Paper |
|
|
|
| Title: | The One-Page Project Manager: Communicate and Manage Any Project With a Single Sheet of Paper |
| Author: | Clark A. Campbell |
| Publisher: | Wiley [Website] |
| Type: | Book / Paperback |
| Publication Date: | 03 November, 2006 |
| ISBN / ISBN-13: | 0470052376 / 9780470052372 |
| List Price: | $19.95 |
| You Save: | $6.38 |
| Amazon Price: | $13.57 |
|
This book is also available, brand-new, from 3rd-party marketplace sellers at Amazon.com, from $10.50.
|
The HTML code below can be pasted onto your web-site, your MySpace page, or blog - or any number of similar places - to create a link to this page:
If, instead of a text link, you'd like to create a link to this page which will display the book cover, if it's available, then the code below will do exactly that:
Check for the same book at these other US book sites:
• [ Abebooks ]
• [ Alibris ]
• [ Barnes & Noble ]
• [ Half.com ]
• [ Powells ]
… or check UK bookstores
|
Editorial Review / Publisher's Information:
Product Description
The One-Page Project Manager shows you how to boil down any project into a simple, one-page document that can be used to communicate all essential details to upper management, other departments, suppliers, and audiences. This practical guide will save time and effort, helping you identify the vital parts of a project and communicate those parts and duties to other team members.
|
Other Items You May Enjoy:
Browse Books From These Related Subjects:
Customer Reviews:
• One-page Project Manager And Prince2
03 February, 2010
Just finished reading the One-Page Project Manager from Clark Campbell. Definitely a book I like. It explains very thoroughly how to set-up and use a single page to communicate progress and issues to senior management (up), your project team (down) and your peers (out). The philosophy behind this book is the fact that senior managers usually only have time to read the highlights. They just cannot read all of a multi-page report; instead, they look for key indicators and the most vital information. And guess what, this is exactly the same I am using in my book `PRINCE2 in Practice, A practical approach to create project management documents (how to avoid bulky, inaccessible, standalone, and illegible documents). The One-Page Project Manager consists of five essential parts: Tasks (the how), Objectives (the what and the why), Timeline: the when, Cost (the how much) and the Owners (the who). The book guides you through twelve steps to construct the One-Page Project Manager including examples for every individual step. Very easy to follow and the book give you several key concepts and tips for project management related to the steps you have to take to fill in the One-Page Project Manager. For those who are using PRINCE2 some remarks to make their life easier. In this book Tasks are key. I would replace this with products or key deliverables. If you communicate to your executive that tangible products are reviewed on behalf of senior user or senior supplier and they approved that these products are according to agreed quality criteria you have a great story. Also the use of owners can be confusing. In this book the project manager (sometimes called executive or lead manager) and those who are responsible for specific tasks are called owner. I would propose to use project manager and team manager for these roles en leave the owner for the executive or project owner (he/she who is judging if it's still worthwhile to finish the project). If the project is too big you can use the concept of multiple layers of the One-Page Project Manager by using a task breakdown. Here I would go for the PRINCE2 product breakdown, but the use of multiple layers will definitely work. If I look at the one-page highlight I described in `PRINCE2 in Practice' I have the possibility to have KPIs on project and on deliverable level. In the One-Page Project Manager it's a little bit difficult to show an early warning or problem with your project end-date when a specific deliverable, on the critical path, has a delay. In the example a subjective task was introduced: `Go live on time'. For me it was also not clear what to do when you can't met the project deadline and the only solution is to postpone this deadline.
To summarize, this is definitely a book that I can recommend and I am going to use some of these ideas to improve the one-page highlight I am using. Connection of objectives to specific deliverables and team managers to specific deliverables is something I am going to add.Prince2 in Practice: A Practical Approach to Creating Project Management Documents : How to Avoid Bulky, Inaccessible, Stand Alone, Illegible Documents
- Amazon Customer Review
• Oppm ++++
28 January, 2010
I found this a very helpful addition to the OPPM book wrtten earlier. It helped to add perspective and depth to how OPPM could be used in conjunction with other quality tools and corprate strategy implementation.
- Amazon Customer Review
• Interesting Ideas
15 May, 2009
I bought this book as a somewhat novice project manager. Being a few years out of college, I needed some new frameworks to help keep everything in order. This book was an interesting read, but light on the content. You can take most of the ideas from just reading his website alone, and downloading the template. There isn't much description or education behind the template, other than how to fill it out and how the author used it back in the 90's to build an automated warehouse.
I'd probably skip this one.
- Amazon Customer Review
• Useful Template And Comprehensive Description Of Its Purpose
24 August, 2009
It's not a bad book which is my way in this instance of evaluating this book as good but not great.
The template is useful. It's accompanied by a comprehensive description of its purpose and how to use it.
The book's tale is a first person account of the development of the template. It goes on to share how useful it proved to be for the author's employer and, of course, the author's career.
Like the other reviewer, Mr. Nathan Carpenter, I had a visceral reaction to the book's typeface. Mr. Carpenter wrote:
<>
I also agree with the degree of redundancy in the book. It read like an infomercial (almost). The book could have been condensed from 160 to about 50 pages. I would have devoted one chapter to the background story of the template's development and two chapters to the manner in which it should be used.
My bottom line: The template is a useful tool. The book is a bit too self-promoting.
- Amazon Customer Review
• Good For Simple Projects
17 October, 2009
I'm an experienced Project Manager and would recommend this approach for project status reporting for moderately complex projects only. After reading the book the one page status report becomes very intuitive, but your status report readers will need a quick walk through of the status report in order for them to understand it. For tips on successful project management please see my blog at: [...]
- Amazon Customer Review
|
