Antoineonline.com : Extreme programming explained: embracing change (9780321278654) : Kent Beck, Cynthia Andres : Books
  Login | Register En  |  Fr
Antoine Online

Extreme Programming Explained: Embracing Change

by Kent Beck, Cynthia Andres
Our price: LBP 70,200Unavailable
*Contact us to request a special order. Price may vary.
I Add to my wishlist
|

Product Details

  • Publisher: Addison-Wesley Professional
  • Publishing date: 26/11/2004
  • Language: English
  • ISBN-13: 9780321278654
  • ISBN: 0321278658

Synopsis

“In this second edition of Extreme Programming Explained, Kent Beck organizes and presents five years’ worth of experiences, growth, and change revolving around XP. If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book.”

Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L.
“The first edition of this book told us what XP was—it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the ‘why’ of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the ‘what’ and the ‘why,’ we can now all set out to confidently work on the ‘how’: how to run our projects better, and how to get agile techniques adopted in our organizations.”

Dave Thomas, The Pragmatic Programmers LLC
“This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there’s an excellent chapter on ‘primary practices,’ but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck’s book: ‘XP is about social change.’ You should do whatever it takes to ensure that every IT professional and every IT manager—all the way up to the CIO—has a copy of Extreme Programming Explained on his or her desk.”

Ed Yourdon, author and consultant
“XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline.”

Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software
Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled ‘extreme.’...”

Lou Mazzucchelli, Fellow, Cutter Business Technology Council
“If your organization is ready for a change in the way it develops software, there’s the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years.”

Philippe Kruchten, UBC, Vancouver, British Columbia
“Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity.”

Mary Poppendieck, author of Lean Software Development: An Agile Toolkit
“Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both easy and hard: It can be started with fewer practices, and yet it challenges teams to go farther than ever.”

William Wake, independent consultant
“With new insights, wisdom from experience, and clearer explanations of the art of Extreme Programming, this edition of Beck’s classic will help many realize the dream of outstanding software development.”

Joshua Kerievsky, author of Refactoring to Patterns and Founder, Industrial Logic, Inc.
“XP has changed the way our industry thinks about software development. Its brilliant simplicity, focused execution, and insistence on fact-based planning over speculation have set a new standard for software delivery.”

David Trowbridge, Architect, Microsoft Corporation

Accountability. Transparency. Responsibility. These are not words that are often applied to software development.

In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process.

The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years. This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a program of continuous improvement based on:

  • Five core values consistent with excellence in software development
  • Eleven principles for putting those values into action
  • Thirteen primary and eleven corollary practices to help you push development past its current business and technical limitations

Whether you have a small team that is already closely aligned with your customers or a large team in a gigantic or multinational organization, you will find in these pages a wealth of ideas to challenge, inspire, and encourage you and your team members to substantially improve your software development.

You will discover how to:

  • Involve the whole team—XP style
  • Increase technical collaboration through pair programming and continuous integration
  • Reduce defects through developer testing
  • Align business and technical decisions through weekly and quarterly planning
  • Improve teamwork by setting up an informative, shared workspace

You will also find many other concrete ideas for improvement, all based on a philosophy that emphasizes simultaneously increasing the humanity and effectiveness of software development.

Every team can improve. Every team can begin improving today. Improvement is possible—beyond what we can currently imagine. Extreme Programming Explained, Second Edition, offers ideas to fuel your improvement for years to come.




In just a few easy steps below, you can become an online reviewer.
You'll be able to make changes before you submit your review.

  • perfect to start applying XP in a team!
    From Amazon

    excellent book! and easy to read, very focus on people! I bought it for the team leader after reading it and she is loving it. we were already in the first steps of applying XP practices, but now she is in the right track

  • Thorough Overview of Extreme Programming (XP)
    From Amazon

    "Extreme Programming Explained" offers a thorough and good overview of the Extreme Programming (XP) approach to software development. This book covers the fundamentals of XP and describes some of the benefits of this approach to developing software. While this approach may not suit all developers, project managers or companies, this book offers an interesting overview of XP.

  • A must read for any developer
    From Amazon

    I believe the basis in software development for business is in this book. You can have the technique, the skills, and the money, but you will need the human side for any agile way of working. This is not the silver bullet, but you NEED to read this book.

  • Nice intro to XP
    From Amazon

    This book is a good introduction to different aspects involved in extreme programming. The author is the initial proponent of XP. First part of the book explains the present day software development realities(like deadlines etc) and the pitfalls that take place due to these time sensitive expectations. Author moves onto explain the necessity for XP and what are the basic guidelines of XP. The author should be commened for covering where XP is impractical and should not be used. The book explains the life cycle of a XP project and different roles that are part of this radical process. XP is not suitable for many present day organizations(due to age old approaches that are already implanted in the system); but should be considered for time sensitive deliverables. This book will definitely give a headsup on how to approach XP. Small negative: The book takes too much time on what is wrong in other traditional approached to software development(for the size of the title:about 200 pages)

  • XP needs a better name
    From Amazon

    When I read the first edition several years ago, my first thought was how XP needs a name change. It seems as if Beck said, "Lets take a bunch of common 'best practices', develop a methodology around performing them consistently, and then give it a name that will scare away managers". XP is not a silver bullet, not is it 'evil'. If you develop software and you work in an environment where you always seem to struggle with issues that prevent your team from operating effectively, then this book is for you. Extreme Programming is about taking several core 'practices' and 'values', and turning that into a methodology - perhaps even a philosophy - of software development, team interaction, and process improvement. I don't care if you end up falling in love with XP or if you end up following RUP, CMMi or some other improvement framework, reading this book is an excellent first start to pull yourself out of the doldrums that most software development shops operate in. Yes, I am a fan of XP and this book. I think the first edition was better. This book seems to digress a lot into touchy-feely subjects, rather than staying on the subject of software development (for example, there are a few pages about personal relationships in the workplace, including dealing with issues that cross the line into HR management - not appropriate for a book that is supposed to be about XP). Beck also seems to flip-flop between describing XP as a solid methodology and a loose collection of his own ideas. I think that XP would greatly improve if it grew up and formalized itself a little better... XP should not be defined with the primary author's telling of anecdotal stories, as appear in this book. Read it with a pragmatic eye, and figure out what is relevant to your situation. Trying to apply these (or any) ideas dogmatically will probably solve some issues while creating far worse ones.

Close
Working on your request