Member-only story
How do the Scrum Events complement each other?
Connecting the dots of Scrum
Originally published in GoRetro
I often stumble upon the same questions. Maybe you’ve faced something similar too. Here are some intriguing questions I get:
- Is the Sprint Retrospective optional?
- Do we really need a Sprint Goal?
- Can we combine the Sprint Planning with the refinement session?
- Do developers need to attend the Sprint Review?
- Can we extend the Sprint in case we haven’t finished the tasks?
Whenever I get one of the above, I know misunderstandings around Scrum dominate the team. Although Scrum aims to be simple, its interpretation of it has endless variants.
Let me take a few minutes to help you understand how to connect the dots of Scrum. This will enable you to benefit more from the framework.
The core of Scrum
Something sad happens with Scrum. People focus excessively on Scrum events while forgetting the framework’s core, which is its power.
The core of Scrum is empiricism. That means we embrace the unknown and continuously uncover new opportunities. One of the best definitions of Scrum in one sentence comes from…