A widely-used software development method, that uses some of the terms below
A fixed period of development time during which the team will not respond to new change requests
Two weeks is typical in the industry.
During the pre-apprenticeship we will work in one-week sprints.
All uncompleted user stories
A prioritised backlog of all the user stories that we estimate will be completed in the next sprint, given each user story estimate and the team’s velocity
Where the team reprioritises user stories and agrees the next sprint backlog
Where the team compares their points estimate of each user story with their actual points and adjusts their estimated velocity for the next sprint
The team capacity, expressed in points, for each sprint
The difficulty level of a user story, expressed in points
Some people prefer to estimate in absolute time, expressed in hours or half-days, but in order to develop a good sense of relative time, we will estimate our user stories in points
E1 - Short story, estimatedE2 - Story, estimatedE3 - Long story, estimatedE5 - Extra long story, estimatedA1 - Short story, actualA2 - Story, actualA3 - Long story, actualA5 - Extra long story, actualstorychorebugrefactorspike“Kanban” which you are going to use to track your project
Not all issues raised in the project board contribute to the velocity estimate. Chores, bugs, refactors and spikes are all zero-point issues, even though they will (seriously) impact your sprint velocity.
Some people prefer to estimate chores, bugs, refactors and spikes just like user stories, however they might better be thought of as non-negotiable and therefore outside the scope of the sprint planning process.
With your partner, work out your actuals for the previous sprint.
Use this to calculate your velocity for the next sprint.
Review and prune your backlog, what are the highest priority issues leftover from last week.
Each team has 3 minutes to give us a quick demo of the site they built
Talk us through the key functionality
It’s completely normal to find public speaking and giving presentations daunting.
See it as an opportunity to practise - and before you know it, giving presentations will be second nature.