Sprint planning makes use of various consensus and estimation techniques in an effort to define a measurable sprint goal for the product owner, team, and stakeholders. The sprint goal should define what is going to be completed during the course of the current sprint.

This course presents the concepts associated with setting sprint goals and planning for the sprint. You'll learn about the Definition of Done, how to define the increment, how to estimate the sprint backlog, and how to avoid common mistakes. Commonly used tools and techniques, and ways to conduct effective sprint meetings are also covered.

The user story is a central part of Scrum, as it represents product requirements from the perspective of the user and provides a common language for the scrum team to communicate with stakeholders.

This course presents the concepts associated with creating user stories and using them to identify product requirements. You'll learn about the user story structure, the criteria that a user story should meet, how to split a story, and how user stories can be used to establish a shared product vision.

As a product evolves from a high level vision to more detailed requirements, the team will establish a Definition of Done. This ensures transparency and a shared product vision, as well as that the team understands the work and can set realistic goals as features are about to be developed.

In this course, you'll learn the concepts associated with defining done, determining the appropriate amount of detail for the level of planning, and the relationship between definition of done and quality, empiricism, and the sprint goal.