Introduction

Sprint planning is at the heart of the Scrum process. This meeting of all product stakeholders establishes the development team's commitment for the next increment. That is which functionality will be delivered at the end of the sprint.

Learning Outcomes

• Describe the Product Owner's role in maintaining the Product Backlog for a project.
• Describe the flow of a Scrum sprint.
• Describe the milestones of a sprint board.
• Measure a team's velocity from past experience.

Study Resources

For your study of this topic, use some of these resources. All four videos are assigned as a pre-class exercise; start there. The articles and blogs provide additional context. Use the Wikipedia articles for reference and deeper exploration.

Video Lessons

• LinkedIn.com: Using relative estimation (3m 2s)
• LinkedIn.com: Playing planning poker (3m 14s)
• LinkedIn.com: Calculating your velocity (3m 57s)
• LinkedIn.com: Planning your sprints (3m 7s)

Web Articles and Blogs

• The Scrum Guide ™, by Ken Schwaber and Jeff Sutherland (PDF)
• Agile Alliance: Velocity

Wikipedia

• Scrum Sprint
• Sprint Backlog
• Velocity (software development)

Example Definition of Done (this is generally the same/similar for all stories):

• All acceptance criteria have been met and verified.
• Code has been reviewed and approved by at least one other team member.
• All unit tests for both frontend and backend components pass.
• Integration tests for the task creation feature pass.
• The feature has been tested on multiple browsers (Chrome, Firefox, Safari) and devices (desktop, tablet, mobile).
• The UI design has been reviewed and approved by the UX team.
• The API endpoint for task creation is documented in the API documentation.
• User guide has been updated with instructions on how to create a new task.
• The feature has been demonstrated to and accepted by the product owner.
• All code follows the team's coding standards and best practices.
• The feature has been deployed to a staging environment and passed QA testing.
• Any bugs or issues discovered during testing have been resolved.
• Performance tests show that the task creation process completes within acceptable time limits.
• The feature is accessible and complies with WCAG 2.1 AA standards.
• All related documentation (including this user story, acceptance criteria, and tasks) has been updated in the project management tool.

Class Lecture

• Sprint Planning