Agile software sprint – plan, build, test, release
Computer ScienceCareers in ComputingAges 17–18
Loading…
Sign in to playA 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.
Lesson: Software development careers: the Agile development process and team roles
What it shows
This simulation shows how a real software team works through one Agile sprint. The product owner has ordered user stories for a school club app by value; the team commits to the stories that fit its capacity, estimated as developers × days × 0.8 points. Each day, developers build stories, bugs appear in new code, and testing or code review catches some of them. Skipping tests speeds up building, but more bugs escape to users. A burndown chart tracks progress, and the sprint review scores customer satisfaction. All coefficients are illustrative assumptions, not industry data.
How to use
Choose a Sprint planning option or tick stories yourself, then set Developers, Testers, Days and Time on tests, and switch Code review on or off. Press Run 1 day to step through the sprint or Run whole sprint to animate it, and watch the board, the burndown line and the bug counter. Compare the sprint review after changing one setting, and use New scenario to see random variation.
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
Questions to explore
- How much faster does the team build with no time on tests, and how many more bugs reach users?
- Why does taking the whole backlog usually lower customer satisfaction?
- What does each role (product owner, developer, tester) contribute to a successful sprint?
