Would you go hiking without a destination and without a backpack? So why would you start your Sprint without Sprint Planning?
Sprint Planning is the first event of the Sprint Scrum. It’s there to define what work will be done and how it will get done. The whole Scrum Team takes part in it. The timebox is 8 hours for a one-month Sprint. And the goal is to answer these 3 questions.
First, why does this Sprint matter?
This is where the Sprint Goal is defined, and where the Product Owner explains their idea and vision. It’s a bit like the destination of the Sprint.
Second, what can be accomplished?
This is where the Developers analyze and discuss with the Product Owner, trying to define the tasks and see what’s achievable or not in order to reach that goal.
Third, how will it get done?
Beyond defining what will be done, this is the moment, when the whole team is together, to define the action plan, whether it involves code, API work, or design. This is when the right conversations need to happen.
By the end of this meeting, the one thing that shouldn’t change is the Sprint Goal. If, as the Sprint progresses, the team learns things and realizes some changes are needed to reach the goal, the plan can absolutely be reworked.
In summary, Sprint Planning turns a vision into a list of tasks and steps to get there, and sets the direction for the next Sprint and the weeks of work ahead.
Sources: https://www.scrum.org/resources/what-is-sprint-planning