97 Things Every Scrum Practitioner Should Know
by Gunther Verheyen
97 Things Every Scrum Practitioner Should Know
- Preface
- I. Start, Adopt, Repeat
- 1. Five Things Nobody Tells You About Scrum
- 2. Mindset Matters Much More Than Practices
- 3. Actually, It’s Not Really About Scrum
- 4. Scrum Is Simple. Just Use It As Is.
- 5. Start with the Why of Your Scrum
- 6. Adopt Before You Adapt
- 7. Regularly Revert to the Simplest Thing That Might Work
- 8. Will Scrum Work for Multi-Location Development?
- 9. Know the Difference Between Multiple Scrum Teams and Multi-Team Scrum
- 10. What Will You Define as “Done”?
- 11. How I Learned to Stop Worrying and Start Using Scrum
- II. Products Deliver Value
- 12. Successful Projects That...Fail
- 13. Answer This Question: “What Is Your Product?”
- 14. Scrum: Giving the Steering Wheel Back to Business
- 15. Beware the Product Management Vacuum
- 16. Scaling Scrum to the Entire Organization with the Flow Framework
- 17. Put Business Value Front and Center
- 18. Product Owner, Not an Information Barrier
- 19. Mastering the Art of “No” to Maximize Value
- 20. Communicating Prioritized Requirements Through the Product Backlog
- 21. Why There Are No User Stories at the Top of Your Product Backlog
- 22. Mind Your Outcomes. Pay Attention to Value.
- III. Collaboration Is Key
- 23. Is There Anything to Learn from Football Hooligans?
- 24. And Then a Miracle Occurs
- 25. Put Customer Focus at the Top of Your Decision-Making Stack
- 26. Is Your Team Working as a Team?
- 27. “That’s Not My Job!”
- 28. Specialization Is for Insects
- 29. Digital Tools Considered Harmful: Sprint Backlog
- 30. Digital Tools Considered Harmful: Jira
- 31. The Vicious Effects of Managing for Utilization
- 32. Becoming a Radiating Team
- IV. Development Is Multifaceted Work
- 33. Agile Is More Than Sprinting
- 34. Patricia’s Product Management Predicament
- 35. The Five Stages of Product Backlog Item Sizing
- 36. Three Common Misconceptions About User Stories
- 37. Introducing Abuser Stories
- 38. What’s in Your Sprint Plan?
- 39. Sprint Backlogs Deserve a Life Beyond Your Electronic Tool
- 40. Testing Is a Team Sport
- 41. Rethinking Bugs
- 42. Product Backlog Refinement Is an Important Team Activity
- 43. Automating Agility
- 44. The Evergreen Tree
- V. Events, Not Meetings
- 45. Sprints Are for Progress, Not to Become the New Treadmill
- 46. How to Have an Effective Sprint Planning
- 47. Sprint Goals Provide Purpose (Beyond Merely Completing Work Lists)
- 48. Sprint Goals: The Forgotten Keys of Scrum
- 49. The Daily Scrum Is the Developers’ Agile Heartbeat
- 50. The Sprint Review Is Not a Phase-Gate
- 51. The Purpose of Sprint Review Is to Gather Feedback—Period
- 52. A Demo Is Not Enough—Go and Deploy for Better Feedback
- 53. Have Sprint Retrospectives and Structure Them
- 54. The Most Important Thing Isn’t What You Think It Is
- VI. Mastery Does Matter
- 55. Understanding the Scrum Master Role
- 56. How I Learned That It’s Not About Me, the Scrum Master
- 57. Servant-Leadership Starts from Within
- 58. The Court Jester at the Touchline
- 59. The Scrum Master as Coach
- 60. The Scrum Master as a Technical Coach
- 61. Scrum Master, Not Impediment Hunter
- 62. Anatomy of an Impediment
- 63. The Scrum Master’s Most Important Tool
- 64. When in Trouble...Break Glass!
- 65. Actively Doing Nothing (Is Actually Hard Work)
- 66. Guiding Scrum Masters on Their Never-Ending Journey with the #ScrumMasterWay Concept
- VII. People, All Too Human
- 67. Teams Are More Than Collections of Technical Skills
- 68. Are People Impediments?
- 69. How Human Nature Overcomplicates What Is Already Complex
- 70. How to Design Your Scrum for A-ha! Moments
- 71. Use Brain Science to Make Your Scrum Events Stick
- 72. The Power of Standing Up
- 73. The Effects of Working from Home
- 74. The Gentle Way of Change
- VIII. Values Drive Behavior
- 75. Scrum Is More About Behavior Than It Is About Process
- 76. What It Means to Self-Organize
- 77. Treating Defects as Treasures (the Value of Openness)
- 78. “That Won’t Work Here!”
- 79. Five Sublime Aspects for Being a More Humane Scrum Master
- 80. The Sixth Scrum Value
- IX. Organizational Design
- 81. Agile Leadership and Culture Design
- 82. Scrum Is “Agile Leadership”
- 83. Scrum Is Also About Improving the Organization
- 84. Networks and Respect
- 85. The Power of Play in a Safe (but Not Too Safe) Environment
- 86. The Trinity of Agile Leadership
- 87. The “MetaScrum” Pattern to Drive Agile Transformation
- 88. Scrum and Organizational Design in Practice
- 89. Thinking Big
- X. Scrum Off Script
- 90. The Origins of Scrum Might Not Be What You Think They Are
- 91. The “Standing Meeting”
- 92. Scrum: Problem-Solving and the Scientific Method in Practice
- 93. Scrum Events Are Rituals to Ensure Good Harvest
- 94. How We Used Scrum to Work with an External Agency
- 95. Scrum Applied in Police Work
- 96. Born to Be Agile: A Case for Scrum in the Classroom
- 97. Agile in Education with eduScrum
- Contributors
- Scrum Glossary
- Index
97 Things Every Scrum Practitioner Should Know
Collective Wisdom from the Experts
Gunther Verheyen
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.