So far, we’ve worked on git individually
For the next two weeks, you’ll work in pairs
When working with others, we review one anothers’ code and merge it into the main branch
Learn by reading others’ code
Developers generally spend more of their time reading code than writing it
On the apprenticeship programme, you’ll review another team’s code each week
On the pre-apprenticeship, you’ll review each others’ pull requests
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. During the full-time programme, each week we are going to do a single two-day sprint. For your final project, you will be doing one-week sprints.
An action that a user wants to perform
“As a… I want… So that…”
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
Stop, go, continue
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.