PVP ed. digital:	EUR 21,83
PVP ed. impresa:	EUR 45,08
Precio Kindle:	EUR 15,28 Ahorra EUR 29,80 (66%)
	IVA incluido (si corresponde)
Vendido por:	Amazon Media EU S.à r.l.

Balancing Agility and Discipline: A Guide for the Perplexed (English Edition) de [Barry Boehm, Richard N. Turner, Grady Booch, Alistair Cockburn, Arthur Pyster]

Sigue al autor

Barry W. Boehm

Balancing Agility and Discipline: A Guide for the Perplexed (English Edition) 1o Edición, Versión Kindle

Edición en Inglés de Barry Boehm (Autor), Richard N. Turner (Autor), Grady Booch (Prólogo), Formato: Versión Kindle

4,3 28 valoraciones

Ver todos los formatos y ediciones

Precio Amazon

Nuevo desde

Usado desde

Versión Kindle

"Vuelva a intentarlo"

15,28 €

—

Tapa blanda

"Vuelva a intentarlo"

45,08 €

12,00 €

Versión Kindle
15,28 € Leer con nuestra App gratuita
Tapa blanda
45,08 €

6 De 2ª mano desde 12,00 € 2 Nuevo desde 45,08 € 2 De coleccionista desde 64,95 €

Agility and discipline: These apparently opposite attributes are, in fact, complementary values in software development. Plan-driven developers must also be agile; nimble developers must also be disciplined. The key to success is finding the right balance between the two, which will vary from project to project according to the circumstances and risks involved. Developers, pulled toward opposite ends by impassioned arguments, ultimately must learn how to give each value its due in their particular situations.

Balancing Agility and Discipline sweeps aside the rhetoric, drills down to the operational core concepts, and presents a constructive approach to defining a balanced software development strategy. The authors expose the bureaucracy and stagnation that mark discipline without agility, and liken agility without discipline to unbridled and fruitless enthusiasm. Using a day in the life of two development teams and ground-breaking case studies, they illustrate the differences and similarities between agile and plan-driven methods, and show that the best development strategies have ways to combine both attributes. Their analysis is both objective and grounded, leading finally to clear and practical guidance for all software professionals--showing how to locate the sweet spot on the agility-discipline continuum for any given project.

ISBN-13

978-0321186126
Edición

N.º 1
Notas adhesivas

En Kindle Scribe
Editorial

Addison-Wesley Professional
Fecha de publicación

11 agosto 2003
Idioma

Inglés
Tamaño del archivo

5906 KB
Ver todos los detalles

Ver todos los dispositivos compatibles

Descripción del producto

Contraportada

"Being a certified bibliophile and a professional geek, I have more shelf space devoted to books on software methods than any reasonable human should possess.Balancing Agility and Disciplinehas a prominent place in that section of my library, because it has helped me sort through the noise and smoke of the current method wars."--From the Foreword by Grady Booch"This is an outstanding book on an emotionally complicated topic. I applaud the authors for the care with which they have handled the subject."--From the Foreword by Alistair Cockburn"The authors have done a commendable job of identifying five critical factors--personnel, criticality, size, culture, and dynamism--for creating the right balance of flexibility and structure. Their thoughtful analysis will help developers who must sort through the agile-disciplined debate, giving them guidance to create the right mix for their projects."--From the Foreword by Arthur Pyster

Agility and discipline: These apparently opposite attributes are, in fact, complementary values in software development. Plan-driven developers must also be agile; nimble developers must also be disciplined. The key to success is finding the right balance between the two, which will vary from project to project according to the circumstances and risks involved. Developers, pulled toward opposite ends by impassioned arguments, ultimately must learn how to give each value its due in their particular situations.

Balancing Agility and Disciplinesweeps aside the rhetoric, drills down to the operational core concepts, and presents a constructive approach to defining a balanced software development strategy. The authors expose the bureaucracy and stagnation that mark discipline without agility, and liken agility without discipline to unbridled and fruitless enthusiasm. Using a day in the life of two development teams and ground-breaking case studies, they illustrate the differences and similarities between agile and plan-driven methods, and show that the best development strategies have ways to combine both attributes. Their analysis is both objective and grounded, leading finally to clear and practical guidance for all software professionals--showing how to locate the sweet spot on the agility-discipline continuum for any given project.

0321186125B10212003

Biografía del autor

Barry Boehm has been trying to balance agility and discipline in software development since 1955. The TRW professor of software engineering and director of the USC Center for Software Engineering, he earlier served as director of the DARPA Information Science and Technology Office and as a chief scientist at TRW. Dr. Boehm's contributions to the field include the Constructive Cost Model (COCOMO), the Spiral Model of the software process, the Theory W (win-win) approach to software management and requirements determination, and his classic book, Software Engineering Economics (Prentice Hall, 1981). Richard Turner, a research professor in engineering management and systems engineering at the George Washington University, approaches balanced software development and acquisition with broad industry and government experience and a skeptical attitude toward best practices. In support of the U.S. Department of Defense, he is responsible for identifying and transitioning new software technology into the development and acquisition of complex, software-intensive defense systems. Dr. Turner was on the original author team for Capability Maturity Model Integration (CMMI) and is coauthor off CMMI Distilled, Second Edition (Addison-Wesley, 2004).

Detalles del producto

ASIN ‏ : ‎ B003XDU8BC
Editorial ‏ : ‎ Addison-Wesley Professional; N.º 1 edición (11 agosto 2003)
Idioma ‏ : ‎ Inglés
Tamaño del archivo ‏ : ‎ 5906 KB
Uso simultáneo de dispositivos ‏ : ‎ Hasta 5 dispositivos simultáneos según los límites del editor
Texto a voz ‏ : ‎ Activado
Lector de pantalla ‏ : ‎ Compatibles
Tipografía mejorada ‏ : ‎ Activado
X-Ray ‏ : ‎ No activado
Word Wise ‏ : ‎ No activado
Notas adhesivas ‏ : ‎ En Kindle Scribe
Longitud de impresión ‏ : ‎ 325 páginas

Clasificación en los más vendidos de Amazon: nº754,880 en Tienda Kindle (Ver el Top 100 en Tienda Kindle)
- nº4,603 en Programación y desarrollo de software en inglés
- nº5,489 en Diseño de software, testing e ingeniería
- nº11,758 en Informática, internet y medios digitales en idiomas extranjeros

Opiniones de los clientes:
4,3 28 valoraciones

Acerca del autor

Sigue a autores para recibir actualizaciones de nuevas publicaciones, además de recomendaciones mejoradas.

Barry W. Boehm

Brief content visible, double tap to read full content.

Full content visible, double tap to read brief content.

Descubre más libros del autor, mira autores similares, lee blogs de autores y más

Opiniones de clientes

4,3 de 5

28 valoraciones globales

5 estrellas		58%
4 estrellas		25%
3 estrellas		4%
2 estrellas		14%
1 estrella 0% (0%)		0%

Cómo funcionan las opiniones y las valoraciones de los clientes

Reseñas más importantes de otros países

Traducir todas las opiniones al español

A. J. Gauld

Good comparison if already familiar with the background

Revisado en el Reino Unido 🇬🇧 el 31 de julio de 2004

Compra verificada

This is a good comparison of the best practice of Agile versus "traditional" software engineering. It does however assume you have already read the books on both sides and understand the basic tenets of each approach. Don't buy this expecting it to cover the two methodologies it simply compares and gives guidance about where each method fits best. As such its an excellent guide for the bewildered project manager or team lead.

A 6 personas les ha parecido esto útil

Traducir reseña a Español

Paul Oldfield

Generally good, with a few weaknesses

Revisado en el Reino Unido 🇬🇧 el 24 de octubre de 2003

Compra verificada

As a devil's advocate for both Agile and Plan-driven approaches this book is excellent, pulling together a lot of useful information and providing a good commentary on it. It is marred slightly by evaluating agile techniques such as YAGNI in isolation and thus giving them a poor write-up. These techniques were never intended to be used in isolation; that message seems to be missing. But don't let that put you off.

A 4 personas les ha parecido esto útil

Traducir reseña a Español

Gandalf

Gut zu lesen

Revisado en Alemania 🇩🇪 el 17 de noviembre de 2019

Compra verificada

Sehr gut!

Traducir reseña a Español

Rogerio Prado Manso

... manage large projects when you need to find the best methodology to

Revisado en Canadá 🇨🇦 el 11 de agosto de 2015

Compra verificada

A different way to manage large projects when you need to find the best methodology to adopt

Traducir reseña a Español

Maurice

Flawed But Helpful

Revisado en los Estados Unidos 🇺🇸 el 5 de julio de 2008

Compra verificada

I like the pragmatic tone of the book, its structure, "day in the life" pictures, case studies, and conclusions. Yet the authors indulge some Agile misconceptions and their case is riddled with straw man argumentation.

Right from the start they set up a false dichotomy between agility and discipline, as if Agile is not a discipline or not disciplined--the authors define discipline as "process mastery, preparation, and courage." Agile done right is all this. And who hasn't seen undisciplined "discipline" (process-heavy approaches is what the authors intend here).

The key to success, they argue, is balancing agility and discipline--what Agilist wouldn't agree?--by using their "risk-driven approach" as a "pragmatic means of reconciling the strengths and weaknesses of disciplined and agile methods." This requires assessing project personnel, criticality, size, culture, and dynamism to customize an agile-discipline hybrid that minimizes risks.

Most Agilists I know are pragmatists, not purists, and do, in fact, use hybrids as needed. The "risk-driven approach" advocated here is a helpful way to quantify the risks and work towards a hybrid. But one caution: "Balancing agile and plan-driven methods requires exceptional people." Agreed, and the authors admit that because you need, and therefore find, more exceptional people in an Agile environment, you're more likely to find success by scaling Agile up than by paring plan-driven methods down.

Other helpful points of clarification for "the perplexed:"

- Agile is an "adaptive rather than predictive mind set."
- "Agile is `planning driven,' rather than `plan-driven.'"
- Agile defines quality as customer satisfaction vs. "specification and process compliance."
- Agile's rapid growth and adoption is due to today's dynamic business environment and to "the resurgence of the philosophy that programming is a craft rather than an industrial process"
- "Personnel turnover is a project's number one risk."

Examples of straw man argumentation:

- "The approaches have become adversarial." I've seen some healthy debate but most practitioners are looking for common ground.
- "The primary difference between agile and plan-driven development practices deal with the design and architecture of the software. Agile methods advocate simple design, one that emerges as functionality is implemented." The authors spill a lot of ink demonstrating that simple may not be sufficient. Yet just a few pages earlier they point out: "Agilists speak of a `mentality of sufficiency'--doing only what is necessary." "Simple," then, actually means "sufficient" to the experienced Agilist.
- The authors point out that Agile refactoring risks turning into costly redesign. And a plan-driven approach, where quality is defined as compliance to outdated specs and rework is common, improves on this how? Later they admit that Agile done right looks at each user story in context of the big picture.
- They complain that getting all the stories done and integrated--particularly "tasks that fall between story cards"--often requires "police" action that "conflicts with agile philosophies." What they call "police" action I call "management" action and, yes, I admit it is often required.

All in all, this book is recommended as it adds to the conversation and moves it in the right direction: whatever works! We've got too much work to do for infighting.

A 6 personas les ha parecido esto útil

Traducir reseña a Español

Ver todas las reseñas

Informar de un problema

¿Este producto tiene contenido inapropiado?

Informe

¿Crees que este producto infringe derechos de autor?

Informe

¿Este producto tiene problemas de calidad o formato?

Informe

Amazon Music Transmite millones de canciones	IberLibro Libros, arte & artículos de colección	Amazon Web Services Servicios Cloud Computing de Amazon	Book Depository Libros con entrega gratis en todo el mundo	Kindle Direct Publishing Publica tu libro en papel y digital de manera independiente

Amazon Segunda mano Productos devueltos y como nuevos	Shopbop Marcas de moda de diseño	Amazon Business Servicio para clientes de empresa	Audible Disfruta de miles de audiolibros y podcasts originales

Comprar para otros

Comprar y enviar eBooks a otras personas

Sigue al autor

Balancing Agility and Discipline: A Guide for the Perplexed (English Edition) 1o Edición, Versión Kindle

Descripción del producto

Contraportada

Biografía del autor

Detalles del producto

Acerca del autor

Barry W. Boehm

Opiniones de clientes

Principales reseñas de España

Reseñas más importantes de otros países