Agile and Iterative Development: A Manager's Guide et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
EUR 51,03
  • Tous les prix incluent la TVA.
Il ne reste plus que 3 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon.
Emballage cadeau disponible.
Quantité :1
Agile and Iterative Devel... a été ajouté à votre Panier
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

Agile and Iterative Development: A Manager's Guide (Anglais) Broché – 11 août 2003


Voir les 2 formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
Broché
"Veuillez réessayer"
EUR 51,03
EUR 39,55 EUR 5,76

Descriptions du produit

Quatrième de couverture

Agile/iterative methods: From business case to successful implementation

This is the definitive guide for managers and students to agile and iterative development methods: what they are, how they work, how to implement them—and why you should.

Using statistically significant research and large-scale case studies, noted methods expert Craig Larman presents the most convincing case ever made for iterative development. Larman offers a concise, information-packed summary of the key ideas that drive all agile and iterative processes, with the details of four noteworthy iterative methods: Scrum, XP, RUP, and Evo. Coverage includes:

  • Compelling evidence that iterative methods reduce project risk
  • Frequently asked questions
  • Agile and iterative values and practices
  • Dozens of useful iterative and agile practice tips
  • New management skills for agile/iterative project leaders
  • Key practices of Scrum, XP, RUP, and Evo

Whether you're an IT executive, project manager, student of software engineering, or developer, Craig Larman will help you understand the promise of agile/iterative development, sell it throughout your organizationaeand transform the promise into reality.

Biographie de l'auteur

CRAIG LARMAN is known throughout the international software community as an expert and passionate advocate for object-oriented technologies and development, and iterative and agile development methods. He serves as Chief Scientist at Valtech, a global consulting and skills transfer company, where he has led the adoption of iterative and agile methods. Larman also authored Applying UML and Patterns, the world's best-selling text on object-oriented analysis and design, and iterative development.



Détails sur le produit


En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Dans ce livre (En savoir plus)
Première phrase
What value will you get from studying this book, an introduction to iterative and agile methods? Lire la première page
En découvrir plus
Concordance
Parcourir les pages échantillon
Couverture | Copyright | Table des matières | Extrait | Index | Quatrième de couverture
Rechercher dans ce livre:

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 53 commentaires
46 internautes sur 51 ont trouvé ce commentaire utile 
Exhaustive look at proven methods 8 juillet 2004
Par Mike Tarrani - Publié sur Amazon.com
Format: Broché
If ever there is a book that should be part of a college-level software engineering curriculum as well as carefully read by software engineering development and project managers this is it. Every major iterative development methodology is covered in complete detail, with an emphasis on Agile methods, and a solid business and technical case is provided for the general approach.
Why make a case for? As difficult as it may be to believe, the waterfall method is still prevalent despite the large body of literature on rapid, iterative development SDLCs. Indeed, I have worked in environments that claimed to embrace the RUP as the enterprise methodology in principle, yet in practice projects were planned and managed using the waterfall SDLC. Why the disconnect? Managers were set in their ways and had no true understanding of the mechanics or value of Agile and iterative development methods.
This book can change that because each major approach is carefully described using the following format for easy comparison and to clearly show strengths and weaknesses:
Method Overview
Lifecycle
Workproducts, Roles, and Practices
Values
Common Mistakes and Misunderstandings
Sample Projects
Process Mixtures
Adoption Strategies
Fact versus Fantasy
Strengths versus "Other"
More importantly, these approaches are placed in the context of the benefits of incremental delivery, with clearly presented evidence of the benefits, which is provided in Chapter 6.
Regardless of biases or preferences, any objective reader will come away with a clear sense of the meaning of 'Agile' and the power and value of iterative development. You will also come away with a good frame of reference with which to compare your own organization's approach to development and delivery, and how to improve it.
16 internautes sur 16 ont trouvé ce commentaire utile 
Finally. Evidence. 29 octobre 2003
Par Lasse Koskela - Publié sur Amazon.com
Format: Broché
I was expecting a lot from this book, having read and enjoyed Larman's prior work. On the other hand, I expected it to be somewhat simplistic as the title implied the target group being managers, which I am not. One of these expectations was correct.
Larman's latest presents a wonderful introduction into what iterative and evolutionary development is about. The word "agile" in the title seems a bit displaced as the text mostly discusses about "iterative" and "evolutionary" rather than "agile", but that really is no big deal because what's inside the covers is pure gold for any one.
After a thorough introduction to the theory, Larman drops a bomb on the table; the chapter titled "Evidence" is worth the salt alone. Larman has collected an impressive list of references to early, large projects employing iterative and evolutionary development. He also reminds us how the creators of predictive planning based methods have themselves preferred an iterative approach from day one.
The book also packs nice descriptions of four iterative and evolutionary processes, namely XP, Scrum, UP, and Evo. The descriptions are clear but, to some degree, repetitive.
Although the chapter on evidence is definitely the gold chip, the last 70 pages proved to be a very pleasant surprise. Larman presents a list of practical tips and tricks for adopting and running iterative processes, as well as answers the toughest questions in a Q/A section.
Highly recommended. Have your boss read it as well.
11 internautes sur 11 ont trouvé ce commentaire utile 
Adios Waterfall 25 novembre 2003
Par Patrick Welsh - Publié sur Amazon.com
Format: Broché Achat vérifié
Yes, indeed, Finally. Abundant proof in one book that the traditional waterfall approach is a terrible way to manage software projects, and is therefore slowly being displaced by agile and iterative approaches. Larman does a devastatingly thorough job of debunking waterfall once and for all.
The book cogently and painstakingly explains how several of waterfall's practices have been conclusively linked to project failures, and how, on the other hand, the practices of Agile and iterative methods like Scrum and XP reduce project risk. Larman summarizes research findings encompassing thousands of projects, and quotes the supporting opinions of standards bodies and industry thought-leaders. The net effect is compelling, to say the least.
If you are an Agile skeptic, this book may rattle your conviction. If you are fence-sitter, it may convince you. And if you already have Agile fire in the belly, then certainly this book will stoke that fire. After reading it, I am left wondering how intelligent, experienced software development management can justify the continued use of a process that has wasted so much money and caused so much pain.
10 internautes sur 10 ont trouvé ce commentaire utile 
Clear, well-written and valuable 18 novembre 2003
Par Sanjiv Augustine - Publié sur Amazon.com
Format: Broché
Craig's book begins with an excellent presentation of the fundamental concepts behind agile development and follows with a strong "Evidence" chapter.
Next is the clear, easy-to-read comparison between the leading agile methodologies (XP, Scrum and UP) and Evo that illustrates their commonalities and differences.
The 'icing on the cake' is the "Practice Tips" chapter that contains many practical insights that I learned the hard way. I think it will be especially useful for project managers new to agile.
As a manager with over 3 years experience managing XP projects, my opinion is that this book is a must-have for any manager interested in agile and iterative development.
9 internautes sur 9 ont trouvé ce commentaire utile 
Thorough and poigniant 22 août 2004
Par Robert C. Martin - Publié sur Amazon.com
Format: Broché
The following is a letter I wrote to someone about this book:

Carlton, You should get hold of Craig Larman's book "Iterative and Agile Management". It has some of the best information about the failings of up-front requirements that I have seen. He quotes from dozens of different peer-reviewed research studies that date back to the 70's and 80's showing that the vast majority of software project failure can be traced to up-front requirements and waterfall mentality.

This information is so significant that I can't believe it's not more widely known. These research studies were done by some of the best people in the industry, including people like Fred Brooks, Capers Jones, and Tom Gilb.

There are 50 pages of such information, all very easy to read. Show it to your managers. Show them the report that the U.S. Department of Defense lost nearly half their major software projects in the 70's and 80's because of up-front requirements analysis.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?