| Description |
1 online resource (212 pages) |
|
text file |
|
34.95 |
| Summary |
"Earned value" is a project management technique that is emerging as a valuable tool in the management of all projects, including and, in particular, software projects. In its most simple form, earned value equates to fundamental project management. This is not a new book, but rather it is an updated book. Authors Quentin Fleming and Joel Koppelman have made some important additions. In many cases, there will be no changes to a given section. But in other sections, the authors have made substantial revisions to what they had described in the first edition. Fleming and Koppelman's goal remains the same with this update: describe earned value project management in its most fundamental form, for application to all projects, of any size or complexity. Writing in an easy-to-read, friendly, and humorous style characteristic of the best teachers, Fleming and Koppelman have identified the minimum requirements that they feel are necessary to use earned value as a simple tool for project managers. They have also witnessed the use of simple earned value on software projects, and find it particularly exciting. Realistically, a Cost Performance Index (CPI) is the same whether the project is a multibillion-dollar high-technology project, or a simple one hundred thousand-dollar software project. A CPI is a CPI ... period. It is a solid metric that reflects the health of the project. In every chapter, Fleming and Koppelman stick with using simple stories to define their central concept. Their project examples range from peeling potatoes to building a house. Examples are in round numbers, and most formulas get no more complicated than one number divided by another. Earned Value Project Management-Second Edition may be the best-written, most easily understood project management book on the market today. Project managers will welcome this fresh translation of jargon into ordinary English. The authors have mastered a unique "early-warning" signal of impending cost problems in time for the project manager to react. |
| Subject |
Program budgeting.
|
|
Production control.
|
|
Cost control.
|
|
Project management.
|
|
Rationalisation des choix budgétaires. |
|
Production -- Contrôle. |
|
Coût -- Contrôle. |
|
Gestion de projet. |
|
cost control. |
|
Cost control |
|
Production control |
|
Program budgeting |
|
Project management |
| Standard No. |
1880410273 |
|
More Resources