Scrum is an empirical process control framework.
Empirical means to runs experiments to improve the product.
Sprint is one timeboxed iteration of a continuous development cycle. The sprint supports the team’s ability to work using Agile processes and tools.
During the planning meeting, typically held on the first day of the sprint, the product owner works with the team to identify those stories or backlog items to complete in the sprint.
The sprint backlog should contain all the information the team needs to successfully plan and complete work within the time allotted without having to rush at the end.
Before start planning your sprint, you’ll want to have created, prioritized, and estimated the backlog and defined the sprints.
A sprint goal is an overarching objective to be accomplished during a sprint. The sprint goal is frequently elaborated through a specific set of product backlog items. A sprint goal is a short, one- or two-sentence, description of what the team plans to achieve during the sprint. It is written collaboratively by the team and the product owner.
A Product Backlog Item (PBI) is a single element of work that exists in the product backlog. PBIs can include user stories, epics, specifications, bugs, or change requirements. The Product Owner of an Agile team compiles and prioritizes the product backlog, putting the most urgent or important PBIs at the top.
A story point is a metric used in agile project management and development to estimate the difficulty of implementing a given user story, which is an abstract measure of effort required to implement it. In simple terms, a story point is a number that tells the team about the difficulty level of the story. Difficulty could be related to complexities, risks, and efforts involved.
Story points are a useful unit of measurement in agile, and an important part of the user story mapping process. A number is assigned to each story to estimate the total effort involved in bringing a feature or functionality to life.
Are you practicing Professional Scrum, or are you just going through the motions and only holding Scrum Events?
Learn more about Professional Scrum.
Estimating tasks will slow you down. Don't do it. We gave it up over 10 years ago.
As an activity, Product Backlog refinement has the following purposes in Scrum: