
User Stories – Part 9
Sprint Planning
The first part of Sprint Planning is used to identify what to put into the Sprint Backlog. This is where the Product Owner identifies the Sprint goal, scopes what backlog items to include, and prioritizes the Sprint backlog from the most important to the least important. The Product Owner must be able to clarify what the functionality is and why they’re valuable. Acceptance criteria should also be discussed so that the team will know what to meet in finishing PBIs.
The second half of Sprint Planning is where the team discusses how to finish the Sprint’s product increment. Tasks for each PBI are identified, and because tasks are never assigned to a Scrum project, each team member picks tasks for themselves. More experienced team members can take the technically challenging tasks, while less experienced ones can choose simpler tasks or be mentored for the more difficult ones.
If not yet done during Product Backlog prioritization, the team also estimates the complexity or amount of time needed for each PBI. One way to estimate PBIs would be to use Poker Planning, where everyone votes for the agreed Story Point, a number relative to the complexity of the PBI at hand. The total Story Points in a Sprint indicates the total effort needed to be given. While the Product Owner may choose not to take part in this session, it’s beneficial to have him around in case the team needs to clarify or renegotiate the scope.
Sprint Review
The Sprint Review is the ceremony primarily used for inspecting the product increment of a Sprint. Each PBI is demonstrated to the Product Owner (along with other customers, if available) and feedback is taken for each PBI. If not done during the Sprint, PBIs are assessed if they meet the Definition of Done or if they still need to be worked on. The feedback gathered can also be used to come up with future PBIs, which, in turn, will create more tasks for the team.
59 Seconds Training Video
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team

What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: