Team project
Introduced
Vocabulary
| English | Meaning |
|---|---|
| user stories | Short descriptions of user goals and value, supported by acceptance criteria. |
| standup | A short team meeting to coordinate progress, next steps and blockers. |
| retro | A retrospective meeting in which a team reviews its process and chooses improvements. |
The board
- User stories ("as a member, I can renew a loan") flow backlog → doing → review → done, each carrying its acceptance test. The standup syncs; the retro adjusts the process.
{exercise:uni-cs1207-board}
Practice
A story is done when —
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Done inherits CI verdict: works-on-my-machine is not a column.
Estimation, calibrated
- Stories sized in points ($1 \approx$ half a day); velocity stabilises at 8 points/week by week 3. Remaining backlog 52 points $\Rightarrow$ ~6.5 weeks, $\pm 1$ week, recalibrated every retro.
- A story without an acceptance test has no done — it has a mood. Done = CI green + reviewed + merged + docs updated.
{exercise:uni-cs1207-estimation}
Practice
52 points at 8/week forecasts —
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Velocity-calibrated, error bar stated, recalibrated per retro.
Blockers escalate
- The reminder story blocks on the notifier credential: visible on the board, raised at standup, resolved by pairing. Blockers older than 2 days escalate — the course history shows exactly one, resolved in a day.
- A standup of status reports to the manager misses the point — it is a plan among peers. A retro without a process change is a complaint session.
{exercise:uni-cs1207-blockers}
Practice
A blocker older than two days —
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Visible on the board, raised at standup, escalated at two days.