Xmas Edition: What NOT to do during Sprint Planning?

To rock as a Scrum Team, you need to have a meaningful Sprint Planning. However, many pitfalls may hold you back from thriving. The question is: what should you not do during the Sprint Planning?
- Never start a Sprint without a goal
- Don't accept segmented Sprints
- Don't come with an unprepared Product Backlog

The Sprint Planning can be either terrific or horrible. It's up to you how you want to get the best out of it.

Follow me on: 

[dandoyle]

One more question. at around time 7:24 you mention that developers will go to the backlog to pick items(stories I presume) that fit the goal and then developers will break the items down into workable chunks. What are these? Are these tasks? If stories are refined to fit in a sprint does that make a story a workable chunk?

[dandoyle]

Great video. I have several questions around sprint goal(s) and backlog. Does the product owner sort of have a goal already reflected in the backlog coming into planning? Or is the backlog like a menu of refined problems and developers fish for the stories that fit the goal? I make fun but I am just trying to pull the 2 together. Seems like it makes sense that product owners are always goal focused if they are keeping a backlog of approximately 2 sprints - goals must be near term if that is the case. Is it hacking a refinement session to talk about the goal to identify any missing stories to support it?

[aaliasultana]

I had a similar experience when refining backlog for a technical migration product. I usually relied on the developers to help refine the stories and this made me feel as a bad product owner!!