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

What's 'Norm'al for one team is not for another


Teams that move into a Norming phase establish game rules for behavior. They feel mutually accountable for the goals of the sprint because they have set the goals themselves. Game rules help the team keep its focus; norms are rules that the team follows and emerge from the team's history and experiences. You can imagine that a team's members are much more committed to the norms they've set for themselves rather than rules set for them by managers or others. It is imperative that a ScrumMaster is secure enough to create an environment in which team norms may emerge. And it's important to know that one team's norms will be very different than that of another's. One team I worked with had a rule that if a developer chose to pair with another developer on a user story, then the code did not have to go through a code review; the team found over time that pairing resulted in much better code quality as a result, allowing a formal code review bypass...