Usado:
US$17.44
Entrega por US$8.20 entre el 11 - 24 de octubre. Ver detalles
Usado: Muy bueno | Detalles
Vendido por ThriftBooks-Atlanta
Condición: Usado: Muy bueno
Comentario: May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less
No se garantizan códigos de acceso ni suplementos con artículos usados.
Agregado a

Lo sentimos; hubo un problema.

Hubo un error al recuperar tus Listas de Deseos. Por favor inténtalo de nuevo.

Lo sentimos; hubo un problema.

Lista no disponible.
Otros vendedores en Amazon
Imagen del logotipo de la aplicación Kindle

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.

Código QR para descargar la App Kindle

Seguir al autor

Ocurrió un error. Intenta realizar tu solicitud de nuevo más tarde.

Practical Project Initiation: A Handbook with Tools (Best Practices) 1st Edición

4.3 4.3 de 5 estrellas 19 calificaciones

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

      Opiniones editoriales

      De The Publisher

      Key Book Benefits:

      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
      • Opiniones de clientes:
        4.3 4.3 de 5 estrellas 19 calificaciones

      Sobre el autor

      Sigue a los autores para recibir notificaciones de sus nuevas obras, así como recomendaciones mejoradas.
      Karl Wiegers
      Brief content visible, double tap to read full content.
      Full content visible, double tap to read brief content.

      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

      4.3 de 5 estrellas
      19 calificaciones globales

      Opiniones destacadas de los Estados Unidos

      Calificado en Estados Unidos el 7 de agosto de 2013
      Fantastic! It is a straightforward book. The book deliver what is promised in its title: You will find practical and objective hints. Don't expect to find theory or deeply discussions about Project Management.
      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.
      Calificado en Estados Unidos el 25 de mayo de 2010
      As with any book I have read by Karl Wiegers, this one was clearly written, and included a lot of practical advice. I can easily recommend it for anyone interested in improving project outcomes, which is really what the initiation phase of any project is really about.

      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").
      Calificado en Estados Unidos el 22 de septiembre de 2011
      This book is a very good quick reference and overview for looking at the tasks for particular parts of requirements gathering with customers. I've used this as a reference often to organize my todo lists before visiting with clients as well as assessing what I've missed or could have done better after a site visit.
      Calificado en Estados Unidos el 3 de abril de 2018
      I was going to write this book, but Karl Wiegers beat me to it, and did a great job. No other practice improves projects more than improved initiation. Highly recommended.
      Calificado en Estados Unidos el 16 de agosto de 2009
      Writer is awesome and right on. Book received in great shape and quickly. Recommend the seller.
      Calificado en Estados Unidos el 7 de octubre de 2007
      Approximately 200 concise pages of very good advice. Several useful tools. Another very good book from Karl.
      Calificado en Estados Unidos el 24 de marzo de 2008
      This book, while good didn't thrill me. It covers some software projects management fundamentals and best practices. It's short, simple and and easy to read, addressing a broad range of topics such as project preparation, project charting, risk management, principled negotiation, project metrics, project retrospectives. In my opinion it's too high-level and most of the topics are already well covered in other books, such as "Rapid Development" by Steve McConnell or "Competitive Engineering" by Tom Gilb (both excellent and quoted in this book). The landmark book by Karl Wiegers is still "Software Requirements".
      A 10 personas les resultó útil
      Reportar
      Calificado en Estados Unidos el 5 de septiembre de 2007
      There is one word that particularly comes to mind when I think of Karl Wiegers: solid. I've been reading Mr. Wiegers articles and books about software for at least a decade, and Practical Project Initiation is as solid as I've come to expect. I use the word "solid" specifically to describe the kind of advice that Wiegers offers, which is typically based on real world experience and research, never on conjecture, received tradition, or trends. Karl is all about doing software right and helping you do the same.

      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.
      A 17 personas les resultó útil
      Reportar