Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Professional ScrumMaster's Handbook

You're reading from   The Professional ScrumMaster's Handbook A collection of tips, tricks, and war stories to help the professional ScrumMaster break the chains of traditional organization and management

Arrow left icon
Product type Paperback
Published in Apr 2013
Publisher Packt
ISBN-13 9781849688024
Length 336 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Stacia Viscardi Stacia Viscardi
Author Profile Icon Stacia Viscardi
Stacia Viscardi
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

The Professional ScrumMaster's Handbook
Credits
Foreword
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
1. Scrum – A Brief Review of the Basics (and a Few Interesting Tidbits) 2. Release Planning – Tuning Product Development FREE CHAPTER 3. Sprint Planning – Fine-tune the Sprint Commitment 4. Sprint! Visible, Collaborative, and Meaningful Work 5. The End? Improving Product and Process One Bite at a Time 6. The Criticality of Real-time Information 7. Scrum Values Expose Fear, Dysfunction, and Waste 8. Everyday Leadership for the ScrumMaster and Team 9. Shaping the Agile Organization 10. Scrum – Large and Small 11. Scrum and the Future The ScrumMaster's Responsibilities ScrumMaster's Workshop 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...

You have been reading a chapter from
The Professional ScrumMaster's Handbook
Published in: Apr 2013
Publisher: Packt
ISBN-13: 9781849688024
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime