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

Chapter 2: Release Planning – Tuning Product Development


  1. Congratulations! Last weekend, you and your significant other decided to get married and agreed upon a date two years from now, which gives you plenty of time to plan (and save some money!). What level of planning would you engage in today? Conceptual, like maybe a Star Wars theme or which venue should we visit, or detailed, like the bride should wear pink toenail polish and her hair in braids. Consider your initial planning approach, followed by more detailed levels of planning that you'd engage in as the wedding approaches. What information emerges through time? How does this affect your plan? Is the word "plan" more usefully thought of as a noun or a verb? Why?

  2. Think back to a recent surprise on a project that you were involved with. Was it preventable? Would thinking longer and harder about the problem have unearthed the issue sooner? Are all surprises avoidable? How does Agile say that teams should deal with surprises, via avoidance or embracement?

  3. Your senior architect is not very fond of moving to an Agile way of working. He balks and verbally resists Scrum in every meeting. He is concerned that attention to good architecture will be traded in for cowboy coding and hacks. How do you involve him in the team's discussions, yet not let his all-or-nothing approach hinder progress?

  4. How do story points and hours differ? How would you explain using both to a reluctant team? (This will happen, so please don't skip this question!)

  5. General tip: For all meetings, create scripts and agendas that keep things moving, ideally with as much team involvement as possible. Prior to the meeting, construct a storyboard of the meeting and identify what the actors will do in each scene, along with the necessary inputs and expected outcomes of each action. These scenes in your meeting storyboard provide an excellent start to your agenda and help you visualize your meeting as a movie ahead of time; this is a great use of your imagination to help you create a tangible, workable agenda!

lock icon The rest of the chapter is locked
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 £16.99/month. Cancel anytime