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

Working in a sprint


Right after sprint planning, team members begin to work on the tasks they identified in the planning meeting. Usually, programmers begin to write code and unit tests. Testers begin to write test cases. Ideally, they're writing both on the same set of assumptions based on the conversation with the product owner, some parts of which are captured in the acceptance criteria of the story (see Chapter 7, Scrum Values Expose Fear, Dysfunction, and Waste). Keep in mind, however, that sprints were designed with a different way of working in mind. In the original Scrum literature, Ken refers to team members as development team members, regardless of what's on their business cards. In other words, everyone is supposed to jump in, no matter what their expertise, and work hard to fulfill the goals of the sprint committed in sprint planning. That means developers could pick up testing tasks, testers could write user documentation or perhaps make a schema change, if that's the way the...