Book Image

The Professional ScrumMaster's Handbook

By : Stacia Viscardi
Book Image

The Professional ScrumMaster's Handbook

By: Stacia Viscardi

Overview of this book

A natural and difficult tension exists between a project team (supply) and its customer (demand); a professional ScrumMaster relaxes this tension using the Scrum framework so that the team arrives at the best possible outcome."The Professional ScrumMaster's Handbook" is a practical, no-nonsense guide to helping you become an inspiring and effective ScrumMaster known for getting results.This book goes into great detail about why it seems like you're fighting traditional management culture every step of the way. You will explore the three roles of Scrum and how, working in harmony, they can deliver a product in the leanest way possible. You'll understand that even though there is no room for a project manager in Scrum, there are certain “management” aspects you should be familiar with to help you along the way. Getting a team to manage itself and take responsibility is no easy feat; this book will show you how to earn trust by displaying it and inspiring courage in a team every day."The Professional ScrumMaster's Handbook" will challenge you to dig deep within yourself to improve your mindset, practices, and values in order to build and support the very best agile teams.
Table of Contents (22 chapters)
The Professional ScrumMaster's Handbook
Credits
Foreword
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
Index

When Scrum gets big—dysfunction or constraint?


While I still prefer an Agile method such as Scrum over a traditional methodology for large projects/programs, the fact of the matter is that any effort that has 20 or more people poses a significant communications challenge. In a program with 35 Scrum teams, all of which will use Scrum the same way, a program of this size of, say, 300 people, takes a tremendous amount of coordination, communication, and organization among teams and stakeholders.

As I mentioned in a previous chapter, I once worked with a company that was creating a new gadget. The program plan called for roughly 35 teams whose focus ran the gamut from firmware, software and tablet apps, integration with conferencing systems, and so on. It was a huge initiative and unfortunately ended up not being very successful in the consumer market.

I was one of the Agile mentors for the program and was limited to 10-15 hours per week to help guide the program. I worked with the ScrumMasters...