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

Release planning – when will you set your features free?


So now we have a product backlog. What next? Well, if you're not required to forecast a set of functionality for a future point in time, then the team should simply start working by pulling items from the top of the backlog to implement. When an organization requires a team to forecast a set of scope for a set period of time, they will, however need to do release planning.

Timing of releases and release planning

Releases themselves should occur at a point in time designated by the product owner when he has evaluated the return on investment and determined that a set of features should be made available to customers or users. The product owner, likely, will have an idea of release timeframes before any work has begun (I needed it yesterday!). There is a frequency at which customers or users would like to see new features, and it is the product owner's responsibility to determine this cadence. For example, in the map application on my...