Agile software sprint – plan, build, test, release

Computer ScienceCareers in ComputingAges 17–18

Use with my class

A small software team runs an Agile sprint to build a school club app: pick user stories from the backlog that fit the team's capacity, then simulate the sprint day by day. Cards move across the To do, In progress, Testing and Done columns, a burndown chart tracks the points left, and bugs created while coding are either caught by testing or escape to users. The sprint ends with a review that scores customer satisfaction. A second screen runs several sprints with or without pair programming and lets a user panel add or reprioritise stories between sprints.

Lesson: Software development careers: the Agile development process and team roles

What it shows

This simulation shows how a software team works through Agile sprints on a school club app. The product owner orders user stories by value, and the team commits to what fits its capacity, about developers × days × 0.8 points. Each day developers build stories, bugs appear in new code, and testing or code review catches some of them. A burndown chart tracks progress and the review scores customer satisfaction. A second screen runs several sprints with or without pair programming, using published ranges (Williams et al. 2000; Arisholm et al. 2007), while a panel of different users adds or reprioritises stories. All coefficients are illustrative.

How to use

Choose a Sprint planning option or tick stories, set Developers, Testers, Days and Time on tests, and switch Code review on or off. Press Run 1 day or Run whole sprint and watch the board, the burndown line and the bug counter. Press Pairs › next to the sliders to compare Solo and Pair programming over several sprints: tick users for the panel, press Run sprint, and press Ask the user panel between sprints.

Parameters you can change

  • Sprint planning Fit team capacity, Take the whole backlog, Choose yourself
  • Number of developers 2–6 people
  • Number of testers 0–2 people
  • Sprint length 5–15 days
  • Developer time spent writing tests 0–40 %
  • Peer code review
  • Screen One sprint, Pairs and user feedback
  • Way of working Solo, Pair programming
  • Evidence for pairs Williams et al. 2000 (students), Arisholm et al. 2007 (professionals)

Questions to explore

  1. How much faster does the team build with no time on tests, and how many more bugs reach users?
  2. Why does taking the whole backlog usually lower customer satisfaction?
  3. What does each role (product owner, developer, tester) contribute to a successful sprint?