EVERYDAY FREE SHIPPING on $25 & up  Excludes Marketplace items
EVERYDAY FREE SHIPPING
on $25 & up
 Excludes Marketplace
Balancing Agility and Discipline : A Guide for the Perplexed

Balancing Agility and Discipline : A Guide for the Perplexed - 04 edition

ISBN13: 978-0321186126

Cover of Balancing Agility and Discipline : A Guide for the Perplexed 04 (ISBN 978-0321186126)
ISBN13: 978-0321186126
ISBN10: 0321186125

Cover type: Paperback
Edition: 04
Copyright: 2004
Publisher: Addison-Wesley Longman, Inc.
Published: 2004
International: No

List price: $49.99

More Shipping Options

Balancing Agility and Discipline : A Guide for the Perplexed - 04 edition

ISBN13: 978-0321186126

Barry Boeham and Richard Turner

ISBN13: 978-0321186126
ISBN10: 0321186125

Cover type: Paperback
Edition: 04
Copyright: 2004
Publisher: Addison-Wesley Longman, Inc.
Published: 2004
International: No
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 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.

Author Bio

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).

Table of Contents

Foreword by Grady Booch.


Foreword by Alistair Cockburn.
Foreword by Arthur Pyster.
Preface.
Acknowledgments.
Prelude.

1. Discipline, Agility, and Perplexity.

The Sources of Perplexity.
Multiple Definitions.
Distinguishing Method Use from Method Misuse.
Overgeneralization Based on the Most Visible Instances.
Claims of Universality.
Early Success Stories.
Purist Interpretations.
Clarifying Perplexity.
The Two Approaches.
Plan-Driven Methods.
Agile Methods.
Finding Middle Ground.

2. Contrasts and Home Grounds.

Application Characteristics.
Primary Goals.
Size.
Environment.
Management Characteristics.
Customer Relations.
Planning and Control.
Project Communication.
Technical Characteristics.
Requirements.
Development.
Testing.
Personnel Characteristics.
Customers.
Developers.
Culture.
Summary.
Home Grounds.
Misconceptions.
Five Critical Factors.

3. A Day in the Life.

Typical Days.
A Typical Day Using PSP/TSP.
A Typical Day Using Extreme Programming.
Crisis Days.
A Crisis Day with TSP/PSP.
A Crisis Day with XP.
Summary.
Differences.
Similarities.
Observations.

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.
Summary.

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.
Summary.

6. Conclusions.

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.
Afterword.
Appendix A. Comparing the Methods.
Scrum.
Thumbnail Sketch.
Comments.
References.
Adaptive Software Development (ASD).
Thumbnail Sketch.
Comments.
References.
Lean Development (LD).
Thumbnail Sketch.
Comments.
References.
Crystal.
Thumbnail Sketch.
Comments.
References.
eXtreme Programming (XP).
Thumbnail Sketch.
Comments.
Reference.
Dynamic Systems Development Method (DSDM).
Thumbnail Sketch.
Comments.
References.
Rational Unified Process (RUP).
Thumbnail Sketch.
Comments.
References.
Team Software Process (TSP).
Thumbnail Sketch.
Comments.
References.
Feature-Driven Development (FDD).
Thumbnail Sketch.
Comments.
References.
Capability Maturity Model Integration (CMMI).
Thumbnail Sketch.
Comments.
References.
Capability Maturity Model for Software (SW-CMM).
Thumbnail Sketch.
Comments.
References.
Personal Software Process (PSP).
Thumbnail Sketch.
Comments.
References.
Cleanroom.
Thumbnail Sketch.
Comments.
References.
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.
CMM Concepts.
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.
Benefits Realized.
Results Chain.
D3. Schedule as an Independent Variable.
Shared Vision and Expectations Management.
Feature Prioritization.
Schedule Range Estimation.
Architecture and Core Capability Determination.
Incremental Development.
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.
Process Improvement.
Team Software Process and Agile Methods.
Pair Programming.
Hybrid Agile/Plan-Driven Methods.

Notes.
References.
Index.

Digital Rights

eBook Requirements
VitalSource Bookshelf Reader
Minimum System Requirements:
  • Windows 7/8, or Mac OS X 10.6 or above
Software Requirements:

eTextbooks and eChapters can be viewed by using the free reader listed below.

Be sure to check the format of the eTextbook/eChapter you purchase to know which reader you will need. After purchasing your eTextbook or eChapter, you will be emailed instructions on where and how to download your free reader.

Download Requirements:

Due to the size of eTextbooks, a high-speed Internet connection (cable modem, DSL, LAN) is required for download stability and speed. Your connection can be wired or wireless.

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.

User Help:

Click Here to access the VitalSource Bookshelf FAQ

Digital Rights
VitalSource Bookshelf
Copying: Allowed, 2 selections may be copied every 365 days
Printing: Allowed, 2 prints for 365 days
Expires: Yes, may be used for 365 days after activation
Reading Aloud: Allowed
Sharing: Not Allowed
Min. Software Version: VitalSource Bookshelf
Suitable Devices: PCs, Tablet PCs, Macs, Laptops


Digital Rights Management (DRM) Key


Copying - Books that cannot be copied will show "Not Allowed." Otherwise, this will detail the number of times it can be copied, or "Allowed with no limits."

Printing - Books that cannot be printed will show "Not Allowed." Otherwise, this will detail the number of times it can be printed, or "Allowed with no limits."

Expires - Books that have no expiration (the date upon which you will no longer be able to access your eBook) will read "No Expiration." Otherwise it will state the number of days from activation (the first time you actually read it).

Reading Aloud - Books enabled with the "text-to-speech" feature so that they can be read aloud will show "Allowed."

Sharing - Books that cannot be shared with other computers will show "Not Allowed."

Min. Software Version - This is the minimum software version needed to read this book.

Suitable Devices - Hardware known to be compatible with this book. Note: Reader software still needs to be installed.

More Shipping Options