Working in a Team: Issues, Estimates and Iterations
A team splits work into pieces small enough to finish, agrees what done means for each, and looks at what actually happened before planning the next stretch. Estimates are a planning tool rather than a promise, and treating them as promises is what makes teams stop giving honest ones.
What a learner can do afterwards
- Split a feature into pieces that can each be finished and reviewed
- Give an estimate with its uncertainty rather than a single number
- Explain what a team learns from comparing plan to outcome
1 · Read
You already know teams share work instead of toiling alone. A team splits each feature into pieces small enough to finish and review one by one. For every piece it agrees what done means: tested, reviewed, and merged, not nearly finished.
A two-week login feature splits into a form piece, a check-password piece, and a remember-me piece. Done for the form means it validates input, has tests, passed review, and merged. Each piece clears the same bar before the next starts.
Estimates guide planning; they are not promises. Give each piece as a range with its uncertainty, such as two to four days, so the plan shows its wobble. Treating estimates as promises only teaches people to pad them or hide bad news.
Before planning the next stretch, compare plan with outcome. Ask what finished late and why, then feed that into the next plan. Teams that study their misses forecast better every round.
Split work into reviewable pieces, estimate in honest ranges, and let each round's misses sharpen the next plan.
2 · Watch
Take it off screen
Where it sits
8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.