9780321579362

Succeeding with Agile Software Development Using Scrum

by
  • ISBN13:

    9780321579362

  • ISBN10:

    0321579364

  • Edition: 1st
  • Format: Paperback
  • Copyright: 10/26/2009
  • Publisher: Addison-Wesley Professional
  • Purchase Benefits
  • Free Shipping On Orders Over $59!
    Your order must be $59 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • Get Rewarded for Ordering Your Textbooks! Enroll Now
List Price: $51.99 Save up to $7.80
  • Buy New
    $44.19

    CURRENTLY AVAILABLE, USUALLY SHIPS IN 24-48 HOURS

Supplemental Materials

What is included with this book?

  • The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
  • The eBook copy of this book is not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Summary

Agile guru Mike Cohn delivers the most practical guide to starting fast with Agile, and succeeding for the long haul--Presents detailed, step-by-step guidance for 60+ tasks that can help software organizations become more agile. Thoroughly covers people, process, and product: everything from scaling Agile and using it in outsourced/offshored environments to overcoming resistance. Helps organizations improve Agile processes they've already implemented, to build better software and drive more value. Agile methods have crossed the chasm to mainstream acceptance, but that doesn't mean all organizations are succeeding with Agile. In this book, one of the world's leading Agile experts draws on his immense experience to help readers anticipate the obstacles to success, and systematically overcome them. Mike Cohn has packed this book with 100% practical and actionable transition advice, real-world case studies, and tips drawn from hard-won experience - everything needed to make Agile work in virtually any environment. Coverage includes: *Why transitioning to Agile is hard - and a transition plan that makes it easier *Managing the process aspects of Agile, from handling backlogs through implementing iteration *Helping people understand their new roles in Agile environments, and work successfully in Agile teams *Building an effective Agile culture and overcoming resistance *Implementing practices that promote higher-quality software *How to scale Agile to large enterprise projects *Using Agile in outsourced and offshored environments *Assessing progress and planning where to go next . This book is designed for every participant in the Agile process, from software leaders to developers: it offers a common language that everyone can use to make Agile work, together with more than 60 specific tasks software organizations can work on to improve their agility.

Author Biography

Mike Coh, founder of Mountain Goat Software, provides training and consulting on Scrum and agile software development to help companies build extremely high-performance development organizations. He authored two of the agile movement's most respected books, User Stories Applied for Agile Software Development and Agile Estimating and Planning. Cohn has been a technology executive in companies ranging from start-ups to the Fortune 40 and has served clients including the BBC, Capital One, Electronic Arts, Experian, Google, Intuit, Lexis Nexis, Lockheed Martin, Microsoft, Nokia, Philips, Sabre, Salesforce.com, Siemens, Sony, Time Warner, Yahoo!, and many more. He cofounded the Agile Alliance, Agile Project Leadership network, and Scrum Alliance.

Table of Contents

Forwordp. XVII
Acknowledgementsp. XIX
About the Authorp. XXIII
Introductionp. XXV
Getting Startedp. 1
Why Becoming Agile Is Hard (But Worth It)p. 3
Why Transitioning Is Hardp. 5
Why It's Worth the Effortp. 10
Looking Forwardp. 17
Additional Readingp. 18
ADAPTing to Scrump. 21
Awarenessp. 23
Desirep. 26
Abilityp. 31
Promotionp. 34
Transferp. 37
Putting It All Togetherp. 40
Additional Readingp. 41
Patterns for Adopting Scrump. 43
Start Small or Go All Inp. 43
Public Display of Agility or Stealthp. 47
Patterns for Spreading Scrump. 50
Introducing New Technical Practicesp. 55
One Final Considerationp. 57
Additional Readingp. 58
Iterating Toward Agilityp. 61
The Improvement Backlogp. 62
The Enterprise Transition Communityp. 63
Improvement Communitiesp. 70
One Size Does Not Fit Allp. 79
Looking Forwardp. 79
Additional Readingp. 80
Your First Projectsp. 81
Selecting a Pilot Projectp. 81
Choosing the Right Time to Startp. 84
Selecting a Pilot Teamp. 86
Setting and Managing Expectationsp. 88
It's Just a Pilotp. 92
Additional Readingp. 92
Individualsp. 95
Overcoming Resistancep. 97
Anticipating Resistancep. 97
Communicating About the Changep. 101
The Hows and Whys of Individual Resistancep. 104
Resistance as a Useful Red Flagp. 114
Additional Readingp. 115
New Rolesp. 117
The Role of the ScrumMasterp. 117
The Product Ownerp. 125
New Roles, Old Responsibilitiesp. 134
Additional Readingp. 135
Changed Rolesp. 137
Analystsp. 137
Project Managersp. 139
Architectsp. 142
Functional Managersp. 144
Programmersp. 146
Database Administratorsp. 148
Testersp. 148
User Experience Designersp. 151
Three Common Themesp. 153
Additional Readingp. 153
Technical Practicesp. 155
Strive for Technical Excellencep. 155
Design: Intentional yet Emergentp. 166
Improving Technical Practices Is Not Optionalp. 171
Additional Readingp. 172
Teamsp. 175
Team Structurep. 177
Feed Them Two Pizzasp. 177
Favor Feature Teamsp. 182
Self-Organizing Doesn't Mean Randomly Assembledp. 189
Put People on One Projectp. 191
Guidelines for Good Team Structurep. 197
Onwardp. 199
Additional Readingp. 199
Teamworkp. 201
Embrace Whole-Team Resposibilityp. 201
Rely On Specialists but Sparinglyp. 204
Do a Little Bit of Everything All the Timep. 206
Foster Team Learningp. 209
Encourage Collaboration Through Commitmentp. 215
All Together Nowp. 217
Additional Readingp. 218
Leading a Self-Organizing Teamp. 219
Influencing Self-Organizationp. 220
Influencing Evolutionp. 227
There's More to Leadership Than Buying Pizzap. 232
Additional Readingp. 233
The Product Backlogp. 235
Shift from Documents to Discussionsp. 236
Progressively Refine Requirementsp. 242
Learn to Start Without a Specificationp. 249
Make the Product Backlog DEEPp. 253
Don't Forget to Talkp. 254
Additional Readingp. 254
Sprintsp. 257
Deliver Working Software Each Sprintp. 258
Deliver Something Valuable Each Sprintp. 262
Prepare in This Sprint for the Nextp. 266
Work Together Throughout the Sprintp. 268
Keep Timeboxes Regular and Strictp. 276
Don't Change the Goalp. 279
Get Feedback, Learn, and Adaptp. 283
Additional Readingp. 284
Planningp. 285
Progressively Refine Plansp. 286
Don't Plan on Overtime to Salvage a Planp. 287
Favor Scope Changes When Possiblep. 292
Separate Estimating from Committingp. 296
Summaryp. 305
Additional Readingp. 305
Qualityp. 307
Integrate Testing into the Processp. 308
Automate at Different Levelsp. 311
Do Acceptance Test-Driven Developmentp. 317
Pay Off Technical Debtp. 320
Quality Is a Team Effortp. 323
Additional Readingp. 323
The Organizationp. 325
Scaling Scrump. 327
Scaling the Product Ownerp. 327
Working with a Large Product Backlogp. 330
Proactively Manage Dependenciesp. 333
Coordinate Work Among Teamsp. 340
Scaling the Sprint Planning Meetingp. 345
Cultivate Communities of Practicep. 347
Scrum Does Scalep. 352
Additional Readingp. 353
Distributed Teamsp. 355
Decide How to Distribute Multiple Teamsp. 356
Create Coherencep. 359
Get Together in Personp. 367
Change How You Communicatep. 372
Meetingsp. 375
Proceed with Cautionp. 386
Additional Readingp. 387
Coexisting with Other Approachesp. 389
Mixing Scrum and Sequential Developmentp. 383
Governancep. 394
Compliancep. 396
Onwardp. 402
Additional Readingp. 402
Human Resources, Facilities, and the PMOp. 405
Human Resourcesp. 406
Facilitiesp. 412
The Project Management Officep. 420
The Bottom Linep. 424
Additional Readingp. 424
Next Stepsp. 427
Seeing How Far You've Comep. 429
The Purpose of Measuringp. 429
General-Purpose Agility Assessmentsp. 430
Creating Your Own Assessmentp. 437
A Balanced Scorecard for Scrum Teamsp. 438
Should We Really Bother with This?p. 443
Additional Readingp. 444
You're Not Done Yetp. 447
Reference Listp. 449
Indexp. 465
Table of Contents provided by Ingram. All Rights Reserved.

Rewards Program

Write a Review