0%

Book Description

A Scrum Master's work is never done. The Development team needs your support, the Product Owner is often lost in the complexities of agile product management, and your managers and stakeholders need to know what will be done, by when, and for how much. Learn how experienced Scrum Masters balance the demands of these three levels of servant leadership while removing organizational impediments and helping Scrum Teams deliver real world value. Discover how to visualize your work, resolve impediments, and empower your teams to self-organize and deliver using the Scrum Values, Agile Principles, and advanced coaching and facilitation techniques.

A Scrum Master needs to know when their team is in trouble and understand how to help them get back on the path to delivery. Become a better Scrum master so you can find the problems holding your teams back. Has your Daily Scrum turned in to a meeting? Does your team struggle with creating user stories? Are stakeholders disengaged during Sprint Review? These issues are common. Learn to use empiricism as your guide and help your teams create great products.

Scrum is so much more than a checklist of practices to follow, yet that's exactly how many organizations practice it. Bring life back to your Scrum events by using advanced facilitation techniques to leverage the full intelligence of your team. Improve your retrospectives with new formats and exercises. Ask powerful questions that spark introspection and improvement. Get support and buy-in from management. Use Scrum as a competitive advantage for your organization. Create a definition of done that improves quality and fix failing sprints.

Take the next step on your journey as a Scrum master. Transform your Scrum practices to help your teams enjoy their work again as they deliver high quality products that bring value to the world.

What You Need:

A moderate level of experience using the Scrum Framework.

Table of Contents

  1.  Foreword
  2.  Acknowledgements
  3.  Preface
    1. Who This Book Is For
    2. What’s in this Book
    3. How to Read This Book
    4. Online Resources
  4. 1. A Brief Introduction to Scrum
    1. A Quick Overview
  5. 2. Why Scrum Goes Bad
    1. Turning Scrum into Best Practices
    2. Lacking Goals
    3. Taylorism Creeping Back in
    4. Trust is Missing
    5. Coach’s Corner
  6. 3. Breaking Bad Scrum with a Value-Driven ApproachBreaking Bad Scrum with a Value-Driven Approach
    1. Reviewing the Scrum Values
    2. Using the Scrum Values Every Step of the Way
    3. The Scrum Values in Action
    4. Coach’s Corner
  7. 4. The Product Owner
    1. Many Product Owners, One Product
    2. The Part-time Product Owner
    3. The Proxy Product Owner
    4. The Commander in Chief
    5. The Scrum Master + Product Owner
    6. Not Having a Clear Vision
    7. Coach’s Corner
  8. 5. The Product Backlog
    1. One Product, Many Product Backlogs
    2. Too Many (or Too Few) PBIs
    3. Inconsistent PBI Formats
    4. The Static Product Backlog
    5. Today’s Forecast: Frustrated Stakeholders
    6. The Unordered Product Backlog
    7. Coach’s Corner
  9. 6. The Development Team
    1. Lacking Necessary Skills
    2. That’s Not My Job
    3. Cutting Corners
    4. Everyone for Themselves
    5. Wait Your Turn
    6. The Team Is Too Big
    7. Not Taking the Initiative
    8. Coach’s Corner
  10. 7. Embracing the Scrum Master Role
    1. No One on My Team Knows Scrum
    2. Help! I’m the Impediment
    3. The Superhero Scrum Master
    4. The Rotating Scrum Master
    5. So Many Impediments, So Little Time
    6. The Dreaded Scrum Lord
    7. Turning into a Scrum Secretary
    8. Acting as the Janitor
    9. Coach’s Corner
  11. 8. Management
    1. Unprepared for Conversations
    2. Expecting Too Much From One Conversation
    3. Not Being Curious about Management’s Needs
    4. Coach’s Corner
  12. 9. Thinking in Sprints
    1. We Need a Special Sprint
    2. Let’s Change the Sprint Length
    3. Scrum Has Too Many Meetings
    4. Using Sprint Cancellations to Change Scope
    5. Follow the Requirements or Else
    6. Coach’s Corner
  13. 10. Sprint Planning
    1. Marathon Planning Events
    2. Leaving Sprint Planning without a Sprint Goal
    3. Maxing Out the Team
    4. Letting Debt Build Up
    5. Coach’s Corner
  14. 11. The Sprint Backlog
    1. Caution: Developers Burning Down
    2. Committing to the Sprint Backlog
    3. Update the Board!
    4. The Daily Projector Update
    5. Waiting on a Miracle
    6. Coach’s Corner
  15. 12. Reclaiming the Daily Scrum
    1. The Daily Scrum as Status Meeting
    2. The Twice-a-Week Scrum
    3. Not All Voices Are Heard
    4. The Team Isn’t Making Progress
    5. Punishing Tardiness
    6. The 45-Minute Scrum
    7. The Team is Raising False Impediments
    8. Coach’s Corner
  16. 13. Deconstructing the Done Product IncrementDeconstructing the Done Product Increment
    1. We Haven’t Defined “Done”
    2. Cutting Quality to Hit a Release Date
    3. We’ll Finish That Later
    4. Coach’s Corner
  17. 14. The Sprint Review
    1. Stakeholders Aren’t Involved
    2. The Product Owner as Judge
    3. Presenting Undone Work
    4. Treating Sprint Reviews like Demos
    5. There’s an ‘I’ in Team
    6. The Stagnant Sprint Review
    7. Skipping It
    8. The Standing Ovation
    9. Coach’s Corner
  18. 15. The Sprint Retrospective
    1. Few Bother to Attend
    2. Superficial Commitments
    3. Meaningless Improvements
    4. 50% Participation
    5. Skipping It
    6. The Complaint Session
    7. Coach’s Corner
18.117.72.224