- Tapa blanda: 86 páginas
- Editor: Provoking Thoughts (1 de octubre de 2012)
- Idioma: Inglés
- ISBN-10: 0955683645
- ISBN-13: 978-0955683640
- Valoración media de los clientes: 3 opiniones de clientes
- Clasificación en los más vendidos de Amazon: nº50.488 en Libros en idiomas extranjeros (Ver el Top 100 en Libros en idiomas extranjeros)
Compara Precios en Amazon
+ Envío GRATIS
Impact Mapping: Making a Big Impact with Software Products and Projects (Inglés) Tapa blanda – 1 oct 2012
|Nuevo desde||Usado desde|
Comprados juntos habitualmente
Los clientes que compraron este producto también compraron
Descripción del producto
Reseña del editor
Software is everywhere today, but countless software products and projects die a slow death without ever making any impact. The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver! This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking. About the Author Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010.
No es necesario ningún dispositivo Kindle. Descárgate una de las apps de Kindle gratuitas para comenzar a leer libros Kindle en tu smartphone, tablet u ordenador.
Obtén la app gratuita:
Detalles del producto
Si eres el vendedor de este producto, ¿te gustaría sugerir ciertos cambios a través del servicio de atención al vendedor?
¿Qué otros productos compran los clientes tras ver este producto?
Opiniones de clientes
Principales opiniones de clientes
Ha surgido un problema al filtrar las opiniones justo en este momento. Vuelva a intentarlo en otro momento.
Se lee fácil, no se enrolla y aporta muchas referencias por si quieres leer más sobre conceptos que menciona. Aunque no llegues a poner en práctica la metodología que explica hay muchos conceptos y situaciones que resultan muy interesantes.
Es cierto que tiene pocos ejemplos, pero es un libro corto y bastante barato.
La única pega para mí es que la edición digital debería ser algo más barata (pero esto pasa con muchos libros).
Opiniones de clientes más útiles en Amazon.com
In this short book, Gojko describes the tool, why it works, how to use it, how not to use it, and then he kindly walks you through the entire agenda for an impact mapping meeting, explaining how to conduct the meeting and what to expect from each step.
There's no fluff here, just clear instructions on how to use this powerful tool for getting the best results from your product development effort.
I highly recommend it.
Impact maps serve to align teams to business objectives, test mutual understanding of goals and expected outcomes, focus teams toward the highest value features to deliver, and enable collaborative decision-making. As such, impact maps--succinctly and approachably described in Gojko's book--is a key tool for collaborative strategic planning.
This is a book you can reference with ease as you plan and facilitate workshops (collaborative meetings with clear purpose and outcomes) for example: release or iteration planning, product roadmapping, process improvement, product and team chartering. And don't forget: it's not just for software products. You will find impact mapping and Gojko's book, useful for strategic alignment needed for any product--software, systems, or services.
Gojko's book is useful, useable and desirable--all the characteristics we want in a great resource! It is useful for building a shared understanding of the big "why's" for our work that is visual, fast to use, and encourages product partners to collaborate. It is useable--easy to read, including engaging cartoons and color, examples, references, and tips. It's desirable to build product that provide impact--aligns to goals and objectives and provide evidence of their value.
Try impact mapping and use Gojko's marvelous book, Impact Mapping: Making a Big Impact with Software Products and Projects to guide you to do your best, most impactful work.
I gave it 4 stars only because the first 3/4ths of the book were all a bit fluffy, explaining the benefits and methodologies applied in great detail without explaining how or what you do in impact mapping. The last quarter really spelled out the info you needed.
I would have preferred the ratio reversed - there were many questions and more details I would like to learn without picking up another book. Luckily the writer cited plenty of material for me to begin exploring!
Glad I read this - I really needed a tool like this for my current project at work.
Good focus on keeping things simple and eliminating waste (well, forward by Tom Poppendieck, so I guess that makes sense!).
One thing that I really liked was the discussion of abstracting scope away until we are ready to do something. Instead of prioritizing among a list of stories, Gojko suggests prioritizing the business goals (prioritize between all the different impacts we want to achieve on the behavior of specific actors, and early on, don't focus as much on how we intend to achieve an impact). I think there is a lot of value in that -- lists of story cards are waste, and can change frequently, and he instead focuses on the big picture, which is the high-level business goals, and we prioritize based on that. (The stories live under the business goals, but Gojko argues that there's no point in talking about a story for anything other than our highest immediate goals.)
There is a section about how impact mapping is a very useful way to run a meeting, and it makes a lot of sense as to how this can help promote useful collaboration around a common goal.
I also really like that Gojko suggests not wasting time on estimating cost and time, and instead focus on value and return on investment. There is a good discussion on how budget and estimation should not be big-bang events.
And there's no fluff. The book is short, but very useful and to-the-point. Highly recommend!
I would recommend it to everyone interested in agile management practices. This should not be restricted to managers. Engineers might find the book useful as well because everyone should make good decisions on the scope of an agile product, especially in small teams.
I assume the technique should be usable in many areas, not just software. I don't see anything software-specific in the book. Any goal oriented business following agile management approach should find impact mapping useful.