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

Individual influences to the work of the sprint


It is important for ScrumMasters to understand personality and learning frameworks so that he/she may more readily recognize what's really going on when a team's members move from the "Forming" stage into the "Storming" stage. One such framework is called the Five Factor Model (FFM); basically, five dimensions that describe the human personality (refer to http://en.wikipedia.org/wiki/Big_Five_personality_traits for more information). These certainly come into play when a team's members get to know each other.

Factor 1 – Openness

How open-minded and curious are the people on your team? Do some want to explore different ways of designing or coding a feature, while others have already made up their minds about how to proceed? For the latter, are they set in their approach, not wanting to listen to the ideas of others? One example that readily comes to mind is the architect and the developer. The architect wants to figure it out all up front, think...