Working in a Team: Issues, Estimates and Iterations · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

Small pieces, honest numbers

Computing · Software Engineering · ages 21-22
Name ______________________   Date ____________

  1. What should done mean for a piece?

    • Nearly finished and quite tested
    • Started with good intentions
    • Tested, reviewed, and merged

  2. What counts as a well-split piece of work?

    • One that touches every file at once
    • One that can be finished and reviewed on its own
    • One with no definition of done

  3. Estimates are promises the team must never break.

    Circle one:   True   False

  4. How should you estimate a piece with an uncertain new library?

    • A single number with no caveats
    • Silence, to avoid all blame
    • A range with its uncertainty, such as three to six days

  5. Break a two-week login feature into reviewable pieces. Which split works?

    • Form, check-password, and remember-me, each testable alone
    • One giant piece called login
    • Frontend colours, then backend colours

  6. What does a team learn from comparing plan with outcome?

    • What finished late and why, to sharpen the next plan
    • Who to blame for each delay
    • That planning is pointless

  7. Two pieces both miss their ranges, one from a sick teammate and one from an underestimated library. What should the next plan change?

    • Buffer for illness is noise, but the library lesson updates future ranges
    • Nothing, misses carry no information
    • Ban libraries and sickness alike

  8. A manager treats every estimate as a promise, and estimates quietly double over months. What happened?

    • The team learned honest forecasting
    • Padding replaced honesty, since promises punish truth
    • The work itself doubled in size
LightMySky · lightmysky.comW1-mt_HNNnVvADcF-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

Small pieces, honest numbers W1-mt_HNNnVvADcF-s1

  1. Tested, reviewed, and merged · Done is an agreed bar the piece fully clears.
  2. One that can be finished and reviewed on its own · Finishable and reviewable is the whole test of size.
  3. False · Estimates guide planning, and promise pressure corrupts them.
  4. A range with its uncertainty, such as three to six days · Ranges carry the wobble into the plan honestly.
  5. Form, check-password, and remember-me, each testable alone · Each slice finishes, reviews, and merges on its own.
  6. What finished late and why, to sharpen the next plan · Studied misses turn into better forecasts round by round.
  7. Buffer for illness is noise, but the library lesson updates future ranges · One-off luck teaches little, while repeated misjudgement recalibrates estimates.
  8. Padding replaced honesty, since promises punish truth · Promise pressure teaches padding and hiding, not accuracy.
Worksheet · LightMySky