Pulse en una miniatura para ir a Google Books.
Cargando... Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects (Pragmatic Programmers) (edición 2009)por Johanna Rothman (Autor)
Información de la obraManage Your Project Portfolio: Increase Your Capacity and Finish More Projects por Johanna Rothman
Ninguno Cargando...
Inscríbete en LibraryThing para averiguar si este libro te gustará. Actualmente no hay Conversaciones sobre este libro. sin reseñas | añadir una reseña
Pertenece a las series editoriales
You have too many projects, and firefighting and multitasking are keeping you from finishing any of them. You need to manage your project portfolio. This fully updated and expanded bestseller arms you with agile and lean ways to collect all your work and decide which projects you should do first, second, and never. See how to tie your work to your organization's mission and show your managers, your board, and your staff what you can accomplish and when. Picture the work you have, and make those difficult decisions, ensuring that all your strength is focused where it needs to be. No se han encontrado descripciones de biblioteca. |
Debates activosNingunoCubiertas populares
Google Books — Cargando... GénerosSistema Decimal Melvil (DDC)658.4Technology Management and auxiliary services Management ExecutiveClasificación de la Biblioteca del CongresoValoraciónPromedio:
¿Eres tú?Conviértete en un Autor de LibraryThing. |
It was repetitive. It had a large amount of internal cross-referencing, which is good, but each reference was "Section X.Y, Full Section Name, on page N" which got annoying after awhile. There were a number of editing errors, and there were some sections where I doubted editing had been done at all. E.g., the chapter on measurement, which I was really looking forward to, had a bunch of graphs with some description, but no actual explanation of what where the values on the graph came from.
The biggest flaw, however, is that this book set itself up to be a book about project portfolio management for any project life cycle, but it felt like every other section had a "but that won't really work well if you're not using agile" caveat.
Overall, I don't regret having read this, but I cannot recommend it. ( )