Wednesday Week 6

Glossary Recap


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

Sprint length

Two weeks is typical in the industry.

During the pre-apprenticeship we will work in one-week sprints.


All uncompleted user stories

Sprint backlog

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

Sprint planning

Where the team reprioritises user stories and agrees the next sprint backlog

Sprint review

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

Issue labels


  • E1 - Short story, estimated
  • E2 - Story, estimated
  • E3 - Long story, estimated
  • E5 - Extra long story, estimated


  • A1 - Short story, actual
  • A2 - Story, actual
  • A3 - Long story, actual
  • A5 - Extra long story, actual

Issue types

  • story
  • chore
  • bug
  • refactor
  • spike

Project board

“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.

Zero-point issues

  • Chore Something that needs to be done, not directly related to a user story
  • Bug Something broken
  • Refactor An improvement to the code that delivers no change to user experience
  • Spike Researching a potential solution to a problem by creating the simplest possible implementation of it


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.


  • Scrum™
  • Sprint
  • Estimate
  • Velocity
  • Backlog, sprint backlog
  • Sprint planning and review
  • Project board (Kanban)


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.

DOM Challenge

The challenge


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.