Sprint Planning in Scrum,

* Purpose of the Sprint Planning Event.
* The roles of the Product Owner, Scrum Master, and Scrum Development Team in Sprint Planning.
* Sprint Planning Meeting timebox (maximum duration) and Sprint execution timebox.
* Example Product Backlog Items (PBIs, or user stories), Sprint Goals, and Sprint Tasks. Difference between the Product Backlog and Sprint Backlog.
* Slack required for innovation.
* Two part Sprint Planning.
* Starting with a usable Product Backlog (thanks to continuous Backlog Refinement Meetings).
* Example schedule for a two-week Sprint.
* Definition of Done: Planning a Sprint that includes all activities needed to develop a potentially shippable product increment, particularly testing.
* The Lean principle of reducing work in progress (WIP).
* The self managing team's ownership of its Sprint Plan. Saying "no" when necessary.

[@romaro_c]

Great training Michael!

[@ChrisAthanas]

I’m wondering where the user fits in to all this, bc I don’t see them represented anywhere

[@MichaelJamesSeattle]

In this series, end users/customers participate in the Sprint Review. At the Sprint Review we learn from their feedback and adjust the Product Backlog based on what we learn together. Though not shown in the video, in LeSS the user also participates in Product Backlog Refinement, as described here: less.works/less/framework/product-backlog-refinement . The team is welcome to invite users to Sprint Planning, though it's not commonly practiced. I will make this more explicit in future versions.