- ホーム
- > 洋書
- > 英文書
- > Computer / General
Full Description
Succeed with Scrum in Even the Largest, Most Complex Distributed Development ProjectsForewords by Ken Schwaber, Scott Ambler, Roman Pichler, and Matthew WangThis is the first comprehensive, practical guide for Scrum practitioners working in large-scale distributed environments. Written by three of IBM's leading Scrum practitioners--in close collaboration with the IBM QSE Scrum Community of more than 1000 members worldwide--this book offers specific, actionable guidance for everyone who wants to succeed with Scrum in the enterprise.Readers will follow a journey through the lifecycle of a distributed Scrum project, from envisioning products and setting up teams to preparing for Sprint planning and running retrospectives. Each chapter presents a baseline drawn from "conventional" Scrum, then discusses additional issues faced by distributed teams, and presents specific best-practice solutions, alternatives, and tips the authors have identified through hard, empirical experience.Using real-world examples, the book demonstrates how to apply key Scrum practices, such as look-ahead planning in geographically distributed environments. Readers will also gain valuable new insights into the agile management of complex problem and technical domains.Coverage includes* Developing user stories and working with Product Owners as a distributed team* Recognizing and fixing the flaws Scrum may reveal in existing processes* Engaging in more efficient Release and Sprint planning* Conducting intense, brief daily Scrum meetings in distributed environments* Managing cultural and language differences* Resolving dependencies, performing frequent integration, and maintaining transparency in geographically distributed environments* Successfully running remote software reviews and demos* Brainstorming what worked and what didn't, to improve future SprintsThis book will be an indispensable resource for every team leader, member, product owner, or manager working with Scrum or other agile methods in any distributed software development organization.
Contents
Foreword by Ken Schwaber xviiForeword by Scott Ambler xixForeword by Roman Pichler xxiiiForeword by Matthew Wang xxvPreface xxviiChapter 1 The Evolution of Scrum 1Core Principles of Scrum 2An Agile Project Management Framework 2Scrum Roles 2Scrum Artifacts 3The Sprint 4The Shift to Distributed Development Teams 5Globally Distributed Teams to Reduce Costs 6Reaching Market More Quickly with the "Follow the Sun" Model 6Distributed Teams Expand Access to New Markets 6Acquisitions 7Expanding for Innovation and Thought Leadership 7Telecommuting 7Improvements in Distributed Collaboration Tools 7Types of Distributed Teams That Have Emerged 8Collocated 8Collocated Part-Time 9Distributed with Overlapping Work Hours 10Distributed with No Overlapping Work Hours 11Ways of Handling Distributed Teams 12Isolated Scrums 12Distributed Scrum of Scrums 12Totally Integrated Scrums 13IBM's Experience in Distributed Scrum 14History of Agile in IBM 15Summary 17Chapter 2 Challenges Faced by Distributed Teams 19Communicating with Distributed Team Members 20Time Zones and Working Hours 20Cultural Differences 21Language Differences 23Keeping Language Simple 23Giving Everyone a Chance to Speak 24Using Group Chat During Meetings 24Providing a Translator 25Confirming What Team Members Understand 25Tools 26File Sharing 26Software Engineering Practices 27Schedule Differences 27Team Dynamics 28Telephone Dynamics 29Providing Access to the Call 29Working with Telephones in a Meeting Room 30Identifying the Speaker 31Handling Visual Cues 31Encouraging Participation 32Limiting Side Conversations 33Muting the Lines 33Checking for Agreement and Disagreement 34Identifying an Advocate to Represent Remote Team Members 34When Nothing Else Works, Everyone Dials In 34Reminders 34Impact of Communication Problems 35How Does Scrum Help? 36Summary 37Chapter 3 Starting a Scrum Project 39How to Identify the Problems Your Product Will Solve 40Who Are Your Stakeholders? 40What Problems Will the Project Address? 42What Are Your Solutions to the Problems? 46What Is the Return on Investment? 47Define the Vision 49Create the Product Roadmap 50Organize the Scrum Teams 50Create and Prioritize the Backlog 51Estimating the Stories as a Team 52Prioritizing the Backlog 52Single Backlog for Multiple Scrum Teams 53Single Backlog with Sections for Multiple Teams 53Separate Backlogs for Multiple Scrum Teams 54Single Backlog Populated by Multiple Other Teams 56Create the Release Plan 56What Is the Sprint Length? 58What Is the Estimated Team Velocity? 59What Are the Dependencies? 61What Are the Risks? 63Coordinate Multiple Product Owners 63Use Agile Project Management Tools 64Invest in Smarter Development 65Coordinating Agile and Non-Agile Teams 66Reporting on Release Status 66Ongoing Updates to Release Plan and Vision 66Important Note about Meeting Face-to-Face 66Summary 67Chapter 4 Preparing for Sprint Planning 69Sprint Preplanning Activities 70Clarification of the User Stories 71Breaking Down User Stories 72Estimating User Stories 72Dealing with Dependencies 75Cleanup of the Product Backlog 78Approaches for the Sprint Preplanning Meeting 78The Full-Team Approach 80The Preplanning Team Approach 81The Balanced Team Approach 82Considerations for Distributed Teams 82Summary 83Chapter 5 Sprint Planning 85Adequately Preparing for the Sprint Planning Meeting 87Sprint Planning Meeting Logistics 87Sprint Planning Meeting Logistics for Scaled Teams 87Sprint Planning Meeting Logistics for Distributed Teams 88The First Half of Sprint Planning: Deciding What to Do 88Reviewing Product Vision and Sprint Goal 89Reviewing the Product Backlog 89Engaging Stakeholders 91The Second Half of Sprint Planning: Deciding How to Get the Work Done 91Creating the Sprint Backlog 92Gaining Commitment 94Updating the Release Plan 94Summary 94Chapter 6 Distributed Daily Scrum Meetings 97Using the Three Questions Effectively 98Answering the Three Questions 99Coordinating the Team on a Daily Basis 99Committing to the Team 100Verifying Progress 100Resolving Blockers 101Daily Scrum Logistics 102Ways of Communicating During the Daily Scrum 102Face-to-Face Meeting 102Teleconference Meeting 103Videoconference Meeting 104Group Instant Messaging Approach 105Approaches to Handling Time Zone Issues 106Daily Scrums Through Documentation 107The Liaison Approach 108Alternating Meeting Times 110Sharing the Pain 112Tips for Distributed Daily Scrums 114Removing Side Conversations 114Keeping the Team Engaged 114Facilitating the Meeting 115Taking Daily Scrum Notes 116Dealing with Language Barriers 117Tools to Help with Distributed Daily Scrum 117Scrum of Scrums 118Summary 118Chapter 7 Effective Collaboration During a Sprint 121Communicating During the Sprint 122Documentation to Overcome Distance 123Using the Right Tools 123Valuing the Whole Team 124Transparency 124Handling New Requests in the Middle of a Sprint 125Single Point of Entry 125Value of the Well-Groomed Backlog 126Shortening the Sprint 127Dealing with Defects 127Disruptions at the Team Member Level 128Handling Stories the Team Cannot Complete During the Sprint 128Handling Blockers During the Sprint 129Responding to Questions During the Sprint 130Sustainable Pace 131Sharing Time Zone Challenges 132Avoiding Double Workdays 132Continuous Integration 133Reports Any Build Failures to the Team 133Reduces the Risk of Integrating Code 133Establishes Greater Confidence in the Product 135Reduces the Time to Find Integration Issues 135Improves the Efficiency of the Team 136Builds Can Run at Different Frequencies 136Test Automation 137Dedicated Automation Teams 137Identify High-Value Automated Tests 138Automate What Is Stable 138Automated Tests Can Run at Any Time 139Automation Helps Improve Software Quality 139Test-Driven Development 139Provides Documentation and Working Examples of Code 140Helps Reduce the Time to Fix Defects 140Helps Improve Code Quality and Provides a Safety Net for Changes 141Helps Team Members Work Together and Collaborate 141Helps Teams Move Away from Big Upfront Designs 142Unit Tests and Continuous Integration 142Handling Infrastructure Projects 143Summary 144Chapter 8 End of Sprint Reviews 147Who Participates in the Reviews 148Enterprise Stakeholders 148Who Should Present 149Preparing Stakeholders 150Reviewing the Strategic Vision of the Product 151Approaches to Help Focus the Review 151Using Themes and a Script 152Having the Product Owner Introduce Each Presentation 152Scheduling for Teams with Overlapping Work Hours 153Scheduling for Teams with No Overlapping Work Hours 154Alternating Meeting Times 154Multiple Sprint Review Meetings 155Sharing the Pain 156Feeling the Pain 156Recording the Entire Sprint Review Meeting 157Challenges Teams Face 157Not Keeping Track of the Stakeholder Comments 157Demos May Provide a False Sense of Completion 158The Team Has Nothing to Present 158Added Challenges of Distributed Teams 159Neglecting to Demo the Work of Part of the Team 159Coordinate with Teams on Different Sprint Lengths 160Remote Demonstrations 160Network Delays and Poor Performance 160Services May Vary by Location 161Demos Outside of Office Hours 161Summary 162Chapter 9 Retrospectives 163Sprint Retrospectives 163What Should Come Out of a Retrospective? 165Retrospective Timing 166Hold Joint Retrospective as Needed 166Hold Regular Joint Retrospectives 166Joint Retrospectives for Teams on Different Sprint Lengths 167Retrospectives for Teams in the Same Product Family 167Conducting Retrospectives After Reviews 167Larger Retrospectives 168Building Trust 168Effects of Distance 169Preparing for the Retrospective 169Setting Expectations 169Understanding the Team Members' Personalities 170Respecting Cultural Differences 171Offering Anonymity 171Asking for Comments Before the Retrospective Meeting 171What Went Well and What Can We Improve? 171Providing Questions to Focus the Discussion 172Consolidating Comments Is Extra Work 172Conducting the Retrospective 173Discussing Reported Issues 173Giving Everyone a Chance to Engage 174Using Common Terminology 175State the Obvious 175Keep the Conversation on Track 175Managing Time Effectively 175Release Retrospectives 176Summary 177Chapter 10 Closing Thoughts 179Index 181
