Plan the next app update — Software Developer · Pretender

The fictional library app gets an update every two weeks. The team has 10 points of work this time. Users asked for many things, and one bug makes some books show the wrong return date. Choose work that fits, keeps the must-haves, and survives a surprise.

Sprint board · ~4 min

Your role

You're the lead developer planning the update (in this game).

Your goal

Choose work that fits, keeps the must-haves, and survives a surprise.

What you know

Bugs that give users wrong information usually come before new features.

Limits

Work that doesn't fit waits for the next update — it isn't lost.

Success looks like

Fits the time — You didn't overload the team.
Must-haves first — The wrong-date bug and the musts are in.
Handles change — You re-planned calmly when the surprise came.

Skills you used

Prioritising — Doing the most important thing first.
Planning — Turning a goal into steps.

In real life

Many software teams work in short cycles (often called sprints) and re-plan when something urgent appears. Saying “not this time” to a nice feature is part of the job.

Software Developer

Build the apps and tools people use every day.

Explore next

Game Designer — Invent rules and levels that are fun and fair.
Data Analyst — Turn numbers into honest answers.
Cybersecurity Analyst — Protect people and systems from online threats.

Keep exploring

Other languages

Loading MyLeoNes™…