on Orders of $25 or more*
|Get your books quickly and easily... and pay nothing for shipping. Just order $25 or more and standard shipping is on us (excludes Marketplace and Rental offerings).|
|$3.99 flat rate|
|UPS 2nd Day Air*||$11.99 flat rate|
|UPS Next Day Air*||$19.98 flat rate|
* Not available for PO boxes and APO/FPO
** Saturday delivery is only available in certain areas. UPS standard rates apply.
*** Separate shipping rates apply for bulk orders
Summary: Nowadays, there are many methodologies you can introduce your to students. On the one hand, there are the more agile methods that focus on individual projects, and how to get them done fast-the camp represented by Beck and Cockburn. On the other hand, there are the more disciplined methods, focused on setting up organizational processes for getting projects done with predictable high quality-the camp best represented by the SEI, the CMMI, and Humphrey. Although these ...show more methods are often presented as mutually exclusive, they actually lie on a continuum. The authors of Balancing Agility and Discipline have worked out clear guidelines for determining where on that continuum a particular software development project is located-and therefore, how agile or disciplined a chosen methodology can or has to be. ...show lessEdition/Copyright: 04
Why We Wrote This Book
True believers represent software development alternatives
In the last few years, two ostensibly conflicting approaches to software development have competed for hegemony. Agile method supporters released a manifesto that shifts the focus from traditional plan-driven, process-based methods to lighter, more adaptive paradigms. Traditional methods have reasserted the need for strong process discipline and rigorous practices. True believers on both sides have raised strident, often antagonistic, voices.
This book is for the rest of us
We wrote this book for the rest of us?those caught in the middle of the method wars simply trying to get our projects completed and accepted within too-tight schedules and budgets. We hope to clarify the perplexity about the roles of discipline, agility, and process in software development. We objectively compare and contrast the traditional, plan-driven approaches to the newer, agile approaches and present an overview of their home grounds, strengths, and weaknesses. We then describe a risk-based approach to aid in balancing agility and discipline within a software development project.
Our goal is to help you in your business environment
We hope that this is a practical book. It is intended to be neither academic nor exhaustive, but pragmatic. It is based on our own development experiences, current and past literature, long conversations with proponents of agile and plan-driven approaches, teaching students how to balance discipline and agility, and years of observing and measuring software development in industry, government, and academia. We discuss the subject matter absent a need to choose sides. Our goal is to help you gain the understanding and information you need to integrate the approaches in a manner that best fits your business environment.
Who Should Read This Book
The perplexed--or just curious
This book is for perplexed software and management professionals who have heard the buzz about agile methods and want to separate the chaff from the wheat. Perhaps you have a CMM- or ISO-certified organization and want to know if and how agile methods can help you. Or perhaps some part of your organization has adopted agile methods and you are unsure of how they should fit in. Fundamentally, if you need to understand how the latest software development approaches can help meet business goals, this book is for you.
Software project managers and mid-level executives should read this book to understand the agility/plan-driven controversy and learn how best to apply the new approaches in your organizations.
Software developers should read this book to better understand how your field is evolving and what it means for your career.
Computer science and software engineering students should read this book to better understand how to make choices about your own level of discipline, both in school and at work.
Academicians should read this book to understand some of what your students are asking about, and how to help them make informed decisions.
Proponents of both agile and plan-driven methods should read this book to dispassionately look at your opponent?s ideas.
CIOs and CEOs should read this book to help you understand what?s going on in the software world and what implications it may have for your company.
How To Read This Book
Several ways to read the book
Most of you are busy people, and "must-read" material attacks you from all sides, 24/7. Some of you want to quickly assess the material for later reflection. Others want to know how to implement the concepts we present. For that reason, we?ve tried to make this book easy to read quickly but with pointers to more in-depth material.
In a hurry? Use the fast track for a quick overview
If time is short, use the fast track summaries to scan the total content of the book, stopping to read things you find interesting or particularly applicable to your needs, and following the icons for specific technical information. If you find you need even more detailed material, there are references as well as a list of additional resources in Appendix F.
First and last chapters are key
You can also tailor your reading through chapter selection. Reading the first and last chapters gives a pretty good idea of the material at a familiarization level. You can read the chapters in any order. Here is a quick summary:
The first chapter sets the stage for what follows. It introduces the main points and provides an executive summary of the book.
Chapter 2 compares the agile and plan-driven approaches and provides insight into the type of projects where each has been most successful--their home grounds.
Chapter 3 provides an experiential introduction to the approaches by describing how both a typical and not-so-typical day might be spent using each.
Chapter 4 presents two project case studies that illustrate the limits of pure agile and pure plan-driven implementations and the benefits of integrating the approaches.
Chapter 5 describes a risk-based approach for making methodology decisions that integrate agile and plan-driven practices, and illustrates it with representative examples.
Chapter 6 summarizes the material and offers some final observations.
Appendix A provides top-level descriptions of the major agile and plan-driven methods, highlighting their primary distinguishing factors, and a summary of those factors for comparison.
Appendices B-E provide technical and background information to support our analyses and speak to specific technical topics.
Appendix F supplies references and the endnotes are listed by chapter in Appendix G.
Boehm, Barry : University of Southern California
Barry Boehm is among the most respected names in the software world. A 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. His 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, 1982).
Turner, Richard : George Washington University
Richard Turner is broadly experienced in software development and acquisition. He currently is a research professor in engineering management and systems engineering at George Washington University, and, in support of the U.S. Department of Defense, is responsible for identifying and transitioning new software technology into the development and acquisition of complex, software-intensive defense systems. He was on the original author team for Capability Maturity Model Integration (CMMI) and is a co-author of CMMI® Distilled (Addison-Wesley, 2001).
Foreword by Grady Booch.
Foreword by Alistair Cockburn.
Foreword by Arthur Pyster.
1. Discipline, Agility, and Perplexity.
The Sources of Perplexity.
Distinguishing Method Use from Method Misuse.
Overgeneralization Based on the Most Visible Instances.
Claims of Universality.
Early Success Stories.
The Two Approaches.
Finding Middle Ground.
2. Contrasts and Home Grounds.
Planning and Control.
Five Critical Factors.
3. A Day in the Life.
A Typical Day Using PSP/TSP.
A Typical Day Using Extreme Programming.
A Crisis Day with TSP/PSP.
A Crisis Day with XP.
4. Expanding the Home Grounds: Two Case Studies.
Using Plans to Scale Up Agile Methods: Lease Management Example.
Assumption 1: The Effort to Develop or Modify a Story Does Not Increase with Time and Story Number.
Assumption 2: Trusting People to Get Everything Done on Time Is Compatible with Fixed Schedules and Diseconomies of Scale.
Assumption 3: Simple Design and YAGNI Scale Up Easily to Large Projects.
Agile Methods Scaleup: Summing Up.
Using Agility to Streamline Plan-Driven Methods: USAF/TRW CCPDS-R Example.
Individuals and Interactions over Processes and Tools: CCPDS-R.
Working Software over Comprehensive Documentation: CCPDS-R.
Customer Collaboration over Contract Negotiation: CCPDS-R.
Responding to Change over Following a Plan: CCPDS-R.
5. Using Risk to Balance Agility and Discipline.
An Overview of the Method.
An Example Family of Applications: Agent-Based Planning Systems.
An Intermediate Application: Supply Chain Management.
Step 1: SupplyChain.com Project Risk Ratings.
Step 2: Compare the Agile and Plan-Driven Risks.
Step 4a: Individual Risk Resolution Strategies.
Step 4b: Risk-Based Strategy for SupplyChain.com System Development.
Small Application: Event Planning.
Step 1: Event Planning Project Risk Ratings.
Step 2: Compare the Agile and Plan-Driven Risks.
Steps 4a, 4b: Risk-Based Strategy for Event Planning System Development.
Very Large Application: National Information System for Crisis Management (NISCM).
Step1: NISCM Project Risk Ratings.
Step 2: Compare the Agile and Plan-Driven Risks.
Steps 3 and 4: Risk-Based Strategy for NISCM System Development.
The Top Six Conclusions.
No Agile or Plan-Driven Method Silver Bullet.
Agile and Plan-Driven Method Home Grounds.
Future Applications Will Need Both Agility and Discipline.
Balanced Agility-Discipline Methods Are Emerging.
Build Your Method Up Don't Tailor It Down.
Focus Less on Methods More on People, Values, Communication, and Expectations Management.
What Can You Do Next about Balancing Agility and Discipline?
Steps toward Balancing Software Development Agility and Discipline.
Appendix A. Comparing the Methods.
Adaptive Software Development (ASD).
Lean Development (LD).
eXtreme Programming (XP).
Dynamic Systems Development Method (DSDM).
Rational Unified Process (RUP).
Team Software Process (TSP).
Feature-Driven Development (FDD).
Capability Maturity Model Integration (CMMI).
Capability Maturity Model for Software (SW-CMM).
Personal Software Process (PSP).
Method Comparison Table.
Appendix B. Manifesto for Agile Software Development.
Principles behind the Agile Manifesto.
Appendix C. Capability Maturity Models.
A Short History of CMMs.
Using Models to Improve Processes.
Appendix D. Tools for Balancing.
D1. The Spiral Model Anchor Point Milestones.
D2. Benefits Realization Analysis and the DMR Results Chain.
D3. Schedule as an Independent Variable.
Shared Vision and Expectations Management.
Schedule Range Estimation.
Architecture and Core Capability Determination.
Change and Progress Monitoring and Control.
Appendix E. Empirical Information.
E1. The Cost of Change: Empirical Findings.
E2. How Much Architecting Is Enough? A COCOMO II Analysis.
E3. Experiments and Studies of Agile and Plan-Driven Methods.
Overall Distribution of Project Size.
Team Software Process and Agile Methods.
Hybrid Agile/Plan-Driven Methods.
More prices and sellers below.
Get Free Shipping on orders over $25 (not including Rental and Marketplace). Order arrives in 5-10 business days.
Need it faster?
We offer fast, flat-rate expedited shipping options.
|Sell it back by:|
|Guaranteed cash back:|
|Cost of this book|
after cash back:
Take advantage of Guaranteed Cash Back. Send your book to us in good condition before the end of the buyback period, we'll send YOU a check, and you'll pay less for your textbooks!
When you're done with this book, sell it back to Textbooks.com. In addition to the the best possible buyback price, you'll get an extra 10% cash back just for being a customer.
We buy good-condition used textbooks year 'round, 24/7. No matter where you bought it, Textbooks.com will buy your textbooks for the most cash.
Being online is not required for reading an eTextbook after successfully downloading it. You must only be connected to the Internet during the download process.
What is the Marketplace?
It's another way for you to get the right price on the books you need. We approved every Marketplace vendor to sell their books on Textbooks.com, so you know they're all reliable.
What are Marketplace shipping options?
Marketplace items do not qualify for free shipping. When ordering from the Marketplace, please specify whether you want the seller to send your book Standard ($3.99/item) or Express ($6.99/item). To get free shipping over $25, just order directly from Textbooks.com instead of through the Marketplace.
FREE UPS 2nd Day Air TermsRental and Marketplace items are excluded. Offer is valid from 1/21/2013 12:00PM to 1/23/2013 11:59AM CST. Your order must be placed by 12 Noon CST to be processed on the same day. Minimum order value is $100.00 excluding Rental and Marketplace items. To redeem this offer, select "FREE UPS 2ND DAY AIR" at checkout. Offer not is not valid on previous orders.