敏捷开发的艺术：实践与经验分享

下载需积分: 50 | PDF格式 | 9.53MB | 更新于2024-07-26 | 19 浏览量 | 举报

"《敏捷软件开发》是一本由O'Reilly出版的书籍，作者是Jim Shore和Shane Warden，该书深入探讨了敏捷开发的实践与益处，特别是聚焦于极限编程（Extreme Programming）的方法。书中包含了作者们在领导团队过程中积累的实际经验，为读者解答关于敏捷实践的问题，并指出可能的误用情况。此外，书中还提供了在实施实践时遇到障碍（如缺乏现场客户）的替代方案。除了技术实践，书里也讨论了与人相关的问题，如建立信任和团队凝聚力的策略，使内容更加全面。该书得到了Ken Pugh和Brian Marick等业界专家的高度评价，被认为是团队必备的参考书目。" 《敏捷软件开发》这本书深入介绍了敏捷开发的理念和方法，包括但不限于以下几个核心知识点： 1. 敏捷开发概述：敏捷开发是一种适应性、迭代和增量的软件开发方法论，强调快速响应变化，提高开发效率和软件质量。 2. 极限编程（XP）实践：极限编程是敏捷开发的一种具体实现，它包括计划游戏、小迭代、结对编程、持续集成、测试驱动开发（TDD）、简单设计、重构和顾客参与等关键实践。 3. 实践详解：书中详细解析了XP的各个实践，帮助读者理解如何在实际项目中实施，以及如何避免常见的陷阱和误用。 4. 团队管理：作者讨论了如何建立团队信任，提升团队凝聚力，这对于敏捷项目的成功至关重要。他们提供策略来改善团队协作，确保成员之间的有效沟通。 5. 遇到障碍的应对策略：在无法完全应用某些实践的情况下，如缺少现场客户，书中有建议的替代方案，帮助团队在受限条件下依然保持敏捷。 6. 相关资源：O'Reilly出版社提供了其他相关书籍，如《Beautiful Code》、《Extreme Programming Pocket Guide》、《Prefactoring》和《Applied Software Project Management》，这些书籍可以作为扩展阅读，帮助读者更全面地了解软件开发领域。通过学习《敏捷软件开发》，开发者和项目经理可以掌握敏捷开发的精髓，提升项目管理效率，更好地应对软件开发过程中的挑战。同时，这本书对于希望提升团队合作水平和适应快速变化需求的组织来说，是一份宝贵的参考资料。

If you just want to learn enough to do your job, you can focus primarily on Part II. Start with

Chapter 3 in Part I to get an overview, then read through the practices in Part II that apply to your work.

Each practice starts with a description of the audience it applies to, such as “Programmers,” “Customers,”

or “Testers.”

If you’re merely curious about agile development, start by reading Part I. Again, Chapter 3 provides a

good introduction. Afterwards, take a look at the practices in Part II. Start with the ones that look most

interesting; you can read them in any order.

About the Études

Have you ever heard a musician playing scales? That’s an étude (if a boring one). An étude teaches

mastery through precise and careful repetition. Eventually, the étude is abandoned, but the skills

remain.

Extreme Programming is our étude for software development. We hope that practicing Extreme

Programming week after week will help you master agile development. Eventually, you’ll change your

practices, but the underlying principles will remain.

Besides the overarching étude of Extreme Programming, we’ve included a mini-étude for each major

theme of agile development. Beginning agile teams can use the études to refine their practice of agile

development. As you gain experience, look deeper; use the études to help connect Part II’s detailed

practices to Part III’s general principles.

NOTE

These études are also useful for teams not currently practicing XP.

Either way, the études require thought to be effective. Each étude provides information, but it doesn’t

tell you how to act on that information. Think about it. What did you learn from the étude? What was

frustrating or exciting? How does that information affect your work? What will you do about it? Without

attention and reflection—that is, mindfulness—the études are just games.

NOTE

It’s no coincidence that you need mindfulness to master the art of agile development

as well. You have to think about more than XP’s practices for it to be effective.

Like musical études, our mini-études work best when you repeat them. We’ve designed them to take

half an hour, so you can (and should) practice them every day for a week or more. Unlike musical

études, these agile exercises work best when you include your whole team. The more you all understand

about the process and where everyone fits in, the better you will work together.

To start, you need a quiet work area capable of holding everyone in your team comfortably. There

should be a whiteboard or wall where you can hang or post index cards between meetings. There must

also be sufficient space to break into groups of two or three people and to talk softly without disturbing

other groups.

We’ve found it valuable to use a timer, whether a stopwatch or a kitchen timer, to keep the session

moving. Each étude has a few parts of 5 to 10 minutes. Although that time will seem to flow quickly

P RE FA CE XV

on your first day, respect the time limits. You’ll perform the étude again tomorrow, so it’s OK if you

don’t finish everything.

Choose one member of your team to facilitate the étude by watching the time (perhaps calling out “one

minute remaining” when appropriate) and promoting discussion. Again, the first session may be hard,

but a good facilitator can encourage everyone to continue.

At the end of each étude, we recommend spending a few minutes debriefing. What did you learn? Are

there questions and ideas you can follow up on during your regular work? If you’ve been trying this

exercise for more than a week, are you still getting valuable results?

If you’re new to XP and agile development, we strongly recommend that you perform each étude while

you study the related chapter as a team. Besides exploring one particular theme in agile development,

each étude can illuminate an aspect of how your team works together on your agile project.

About Pronouns

We speak in first-person singular rather than first-person plural in the rest of this book. (We say “I,”

not “we.”) We include a lot of personal anecdotes and experiences, and the singular form works better

as a result. However, this book is unquestionably the result of a partnership between two authors and

our use of the word “I” is merely a convenience.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your

programs and documentation. You do not need to contact us for permission unless you’re reproducing

a significant portion of the code. For example, writing a program that uses several chunks of code from

this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly

books does require permission. Answering a question by citing this book and quoting example code

does not require permission. Incorporating a significant amount of example code from this book into

your product’s documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author,

publisher, and ISBN. For example: “The Art of Agile Development by James Shore and Shane Warden.

If you feel your use of code examples falls outside fair use or the permission given above, feel free to

Safari® Enabled

When you see a Safari® Enabled icon on the cover of your favorite technology book, that means the

book is available online through the O’Reilly Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you easily search

thousands of top tech books, cut and paste code samples, download chapters, and find quick answers

when you need the most accurate, current information. Try it for free at http://safari.oreilly.com.

XVI P RE FA CE

How to Contact Us

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707 829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional information. You

can access this page at:

http://www.oreilly.com/catalog/9780596527679

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about our books, conferences, Resource Centers, and the O’Reilly Network, see

our web site at:

http://www.oreilly.com

Acknowledgments

We owe a debt of gratitude to Elisabeth Hendrickson for her contribution of the “Exploratory Testing”

section. Her expertise and writing skill made the material sparkle. For more of Elisabeth’s writing, visit

http://www.testobsessed.com/.

We stole good ideas wherever we could find them. Kent Beck, Ron Jeffries, and Ward Cunningham

each had a hand in the ideas that led to XP, and we stole liberally from those. In addition to XP itself,

Kent Beck introduced us to the idea of XP practices as études. Ward Cunningham introduced us to the

notion of technical debt, a concept we use heavily. Brian Marick’s series of essays, “Agile Testing

Directions,”

influenced our thoughts on agile testing and the role of testers on agile teams.

James had the opportunity to work with Joshua Kerievsky on an Industrial XP (IXP)

†

project for half a

year. He learned a lot from that project; the Vision practice in particular was inspired by IXP’s Project

Chartering practice. David Schwartz and Amy Schwab of True North pgs, Inc.,

‡

provided the specific

vision format that we use, as well as the term project community. Their Mastering Projects workshop is

excellent; take it when you have the opportunity.

Thank you to our editor, Mary Treseler O’Brien, for providing vision (where necessary), trust (where

appropriate), and deadlines (where frightening). This book would not be what it is without you gently

nudging us in directions different from our original ideas.

Thanks also to our army of reviewers, who provided over one thousand comments and suggestions on

our mailing list. In particular, thanks to Adrian Howard, Adrian Sutton, Ann Barcomb, Andy Lester,

http://www.testing.com/cgi-bin/blog/2004/05/26

†

http://www.industrialxp.org/

‡

http://www.projectcommunity.com/

P RE FA CE XVII

Anthony Williams, Bas Vodde, Bill Caputo, Bob Corrick, Brad Appleton, Chris Wheeler, Clarke Ching,

Daði Ingólfsson, Diana Larsen, Erik Petersen, George Dinwiddie, Ilja Preuß, Jason Yip, Jeff Olfert, Jeffery

Palermo, Jonathan Clarke, Keith Ray, Kevin Rutherford, Kim Gräsman, Lisa Crispin, Mark Waite,

Nicholas Evans, Philippe Antras, Randy Coulman, Robert Schmitt, Ron Jeffries, Shane Duan, Tim

Haughton, and Tony Byrne for their extensive comments. Special thanks to Brian Marick, Ken Pugh,

and Mark Streibeck for their comments on the completed draft.

James Shore

Every work builds on what came before. I was fortunate to have not just one, but many giants to stand

on. Without the inspired work of Kent Beck, Alistair Cockburn,Ward Cunningham, Tom DeMarco,

Martin Fowler, Ron Jeffries, Timothy Lister, Steve McConnell, and Gerald Weinberg, I wouldn’t have

anything close to the understanding of software development I have today. It’s thanks to their example

that this book exists. In particular, thanks to Alistair Cockburn for generously inviting me to his

roundtable and introducing me to the agile community.

If giants enabled me to contribute to this book, then Kim Eaves and the Denali team brought the

stepladder. Without their enthusiastic support, I never would have been able to try that crazy XP thing.

Thanks also to Rob Myers for his ever-friendly consideration of my rants.

I also gratefully acknowledge my coauthor and friend, Shane Warden. This project morphed from a

little 100-page second edition into a 400-page monster. You didn’t complain once. Thanks for putting

up with me. (And hey! Nice book.)

Finally, thank you, Neeru, my loving and patient wife. I used to think authors thanking their families

was cliché. Now I understand. I couldn’t have finished this book without your support.

Shane Warden

Thanks to Jim for arguing with me while writing the first version of this book (it’s better for it) and for

convincing me that the second edition was worth doing.

Thanks to Allison and Andrew for the tools we used to write this book.

Thanks to my family for supporting me (and not grumbling too much while I sat upstairs and wrote

very slowly), and to my friends for dragging me out of my house once in a while.

Thanks also to the other contributors to Parrot and Perl 6 for being unwitting collaborators, examples,

and victims of some of the ideas in this book. The work we do continually amazes me.

XVIII P RE FA CE

剩余431页未读，继续阅读

身份认证购VIP最低享 7 折!

30元优惠券

leo_dong

粉丝: 0

敏捷开发的艺术：实践与经验分享

《Scrum敏捷软件开发概述及原则》

"敏捷软件开发的历史背景与发展：从软件危机到时代变革

构建中国敏捷软件开发实践指南：知识体系与成功案例

"敏捷软件开发：Scrum方法与实践

敏捷软件开发：理念、挑战与实践

算法_Java转C_红宝书重要程序_学习参考_1741862469.zip

人脸识别_活体检测_眨眼检测_自动捕捉服务名Face_Liv_1741771519.zip

视觉处理_自动裁剪_显著区检测_OpenCV_图像优化用途_1741779446.zip

基于pringboot框架的图书进销存管理系统的设计与实现（Java项目编程实战+完整源码+毕设文档+sql文件+学习练手好项目）.zip

基于动态规划和模型预测控制的并联混合电动汽车最佳控制 简介：利用动态规划，使用模型预测控制，实现对并联混合动力电动汽车的最佳控制，并降低总体成本函数 使用动态规划可以实现混合动力电动汽车的优化控制

最新资源

基于动态规划和模型预测控制的并联混合电动汽车最佳控制简介：利用动态规划，使用模型预测控制，实现对并联混合动力电动汽车的最佳控制，并降低总体成本函数使用动态规划可以实现混合动力电动汽车的优化控制