Descarga la app de Kindle gratis y comienza a leer libros Kindle al instante desde tu smartphone, tablet o computadora, sin necesidad de ningún dispositivo Kindle.
Lee al instante desde tu navegador con Kindle para la web.
Usando la cámara de tu celular escanea el siguiente código y descarga la aplicación Kindle.
Imagen no disponible
Color:
-
-
-
- Para ver la descarga de este video Flash Player
Seguir al autor
Aceptar
Practical Project Initiation: A Handbook with Tools (Best Practices) 1st Edición
Zero in on key project-initiation tasks—and build a solid foundation for successful software development. In this concise guide, critically-acclaimed author Karl E. Wiegers fills a void in project management literature by focusing on the activities that are essential—but often overlooked—for launching any project. Drawing on his extensive experience, Karl shares lessons learned, proven practices, and tools for getting your project off to the right start—and steering it to ultimate success.
Lay a foundation for project success—discover how to:
- Effectively charter a project
- Define meaningful criteria for project success and product releases
- Negotiate achievable commitments for project teams and stakeholders
- Identify and document potential barriers to success—and manage project risks
- Apply the Wideband Delphi method for more accurate estimation
- Measure project performance and avoid common metrics traps
- Systematically apply lessons learned to future projects
Companion Web site includes:- Worksheets from inside the book
- Project document templates
- Resources for project initiation and process improvement
- ISBN-100735625212
- ISBN-13978-0735625211
- Edición1er
- EditorialMicrosoft Press
- Fecha de publicación18 Agosto 2007
- IdiomaInglés
- Dimensiones7.25 x 0.75 x 8.75 pulgadas
- Número de páginas232 páginas
Los clientes que compraron este producto también compraron
More About Software Requirements: Thorny Issues and Practical AdviceTapa blandaUS$7.30 de envíoRecíbelo el miércoles, 2 de octubreSolo queda(n) 1 en stock (hay más unidades en camino).
Opiniones editoriales
De The Publisher
Delivers experience-based guidance about how to get a software development project off to a strong start
Provides metrics and tools to help organize priorities, track progress, and plan assignments
Features numerous useful templates and forms--in the book, and downloadable from the book's companion Web site
Biografía del autor
Karl E. Wiegers is a leading speaker, author, and consultant on requirements engineering, project management, and process improvement. As Principal Consultant with Process Impact, he conducts training seminars for corporate and government clients worldwide. Karl has twice won the Software Development Productivity Award, which honors excellence in productivity-enhancing products and books.
Detalles del producto
- Editorial : Microsoft Press; 1er edición (18 Agosto 2007)
- Idioma : Inglés
- Tapa blanda : 232 páginas
- ISBN-10 : 0735625212
- ISBN-13 : 978-0735625211
- Dimensiones : 7.25 x 0.75 x 8.75 pulgadas
- Clasificación en los más vendidos de Amazon: nº2,428,807 en Libros (Ver el Top 100 en Libros)
- nº726 en Diseño de Software y Ingeniería
- nº2,138 en Lenguajes de Programación (Libros)
- nº2,510 en Gestión de Proyectos de Negocios
- Opiniones de clientes:
Sobre el autor

Karl Wiegers has provided training and consulting services worldwide on many aspects of software engineering. He has a PhD in organic chemistry. Karl is the author of 13 books and many articles on software development, product design, project management, self-help, chemistry, and military history, plus a forensic mystery novel titled "The Reconstruction."
Karl's latest book is "Software Requirements Essentials," coauthored with Candase Hokanson. This concise book describes 20 practices every software team should perform to understand the business problem, engage the right participants, articulate effective solutions, communicate information among stakeholders, implement the right functionality in the right sequence, and adapt to change. Each practice ends with several "Next Steps" to help you begin applying its content immediately.
When not at the keyboard, Karl enjoys reading military history, wine, playing guitar, and writing and recording music. Check out his songs --if you dare -- at karlwiegers.com.
Opiniones de clientes
- 5 estrellas4 estrellas3 estrellas2 estrellas1 estrella5 estrellas63%20%4%13%0%63%
- 5 estrellas4 estrellas3 estrellas2 estrellas1 estrella4 estrellas63%20%4%13%0%20%
- 5 estrellas4 estrellas3 estrellas2 estrellas1 estrella3 estrellas63%20%4%13%0%4%
- 5 estrellas4 estrellas3 estrellas2 estrellas1 estrella2 estrellas63%20%4%13%0%13%
- 5 estrellas4 estrellas3 estrellas2 estrellas1 estrella1 estrella63%20%4%13%0%0%
Las opiniones de clientes, incluidas las valoraciones de productos ayudan a que los clientes conozcan más acerca del producto y decidan si es el producto adecuado para ellos.
Para calcular la valoración global y el desglose porcentual por estrella, no utilizamos un promedio simple. En cambio, nuestro sistema considera cosas como la actualidad de la opinión y si el revisor compró el producto en Amazon. También analiza las opiniones para verificar la confiabilidad.
Más información sobre cómo funcionan las opiniones de clientes en Amazon-
Opiniones principales
Opiniones destacadas de los Estados Unidos
Ha surgido un problema al filtrar las opiniones justo en este momento. Vuelva a intentarlo en otro momento.
It is easy to read (In fact, all Wiegers' books are!), this book may be used by both juniors and seniors project managers. Of course, a senior PM will notice details not usually realized by freshers PMs.
In addition to project initiation, this book includes helpful advice on tool adoption, estimation and measurement practices, and project retrospectives (analyzing projects for "lessons learned").
There are several things I like about this book. First and foremost, I like that it is short and narrowly focused on the topic of starting new software projects--a neglected area to be sure. Much like Robert Galen's recent book Software Endgames focuses on getting a troubled project over the finish line, Practical Project Initiation focuses on the start of the process, with the idea of helping you keep your project from getting into trouble in the first place.
At 200 pages, the book is short (by software book standards anyway) not only because the focus is narrow but also because Wiegers is concise; there is almost no fluff here. I think Wiegers knows that when you need a book like this, you need immediate help getting your project off on the right foot, not three months worth of study material. I was able to read it all the way through pretty quickly, and much of the material is designed so that you can come back to it later for reference purposes.
The ironic part of what I've said about the book's narrow focus is that the first 25 pages of the book may actually be one of the best short introductions out there to the broad topic of project management.
Another thing I really like about Practical Project Initiation is that Wiegers does not steer you in the direction of a particular process, or try to propose Yet Another Great Methodology, or try to convince you of the One Right Way to develop software. (In fact, I seem to remember an essay by Wiegers from a few years ago called "No New Models!") Weigers makes room for whatever methodology/process you are using, and if you're really not sure what methodology you are using or should be using, don't worry--just follow the foundation advice in this book, and you'll be okay. Another way of saying this is that, while the book overall does have a strategic scope, the focus of the material is very tactical. The tactics Wiegers suggests can be used on the most agile Agile project or the most formal "heavyweight" project.
Before this review gets too long, I want to highlight the wealth of "tools" that come with this book. Many of these are tools in the literal sense, in the form of worksheets, checklists, and templates that are printed in the book and that can be downloaded for free. But the whole book is full of tools in the figurative sense also--things like the wideband delphi method for estimation, a feature triage process for figuring out what to include in the project when there's just too much scope, and techniques for identifying and managing risks.
If you, like me, just like to geek out on software books and pick up new techniques and insights, I recommend this book for reading and loaning out. If you are more squarely in the target audience of the book--being a person who is tasked with getting a software project off the ground--this book is a must-have. Get it fast, read it fast, and put Wiegers practical advice into action right away.


