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

What's 'Norm'al for one team is not for another


Teams that move into a Norming phase establish game rules for behavior. They feel mutually accountable for the goals of the sprint because they have set the goals themselves. Game rules help the team keep its focus; norms are rules that the team follows and emerge from the team's history and experiences. You can imagine that a team's members are much more committed to the norms they've set for themselves rather than rules set for them by managers or others. It is imperative that a ScrumMaster is secure enough to create an environment in which team norms may emerge. And it's important to know that one team's norms will be very different than that of another's. One team I worked with had a rule that if a developer chose to pair with another developer on a user story, then the code did not have to go through a code review; the team found over time that pairing resulted in much better code quality as a result, allowing a formal code review bypass...

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 $19.99/month. Cancel anytime