---
title: "Working in a Team: Issues, Estimates and Iterations"
description: "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 "
canonical: https://lightmysky.com/learn/computing/working-in-a-team-issues-estimates-and-iterations-mt_HNNnVvADcF
source: https://lightmysky.com/learn/computing/working-in-a-team-issues-estimates-and-iterations-mt_HNNnVvADcF.md
retrieved: 2026-09-12
---

> **Agent view.** This is the Markdown twin of the page, for tools and assistants.
> When to use this site, and the call that answers each job: https://lightmysky.com/agent-instructions.md
> API description (OpenAPI 3.1): https://lightmysky.com/openapi.json · Authentication: https://lightmysky.com/auth.md
> Pricing: https://lightmysky.com/pricing.md · Catalog: https://lightmysky.com/llms.txt · Full catalog: https://lightmysky.com/llms-full.txt
> Every machine-readable file on this domain: https://lightmysky.com/.well-known/ai-catalog.json
> Ask for Markdown with `Accept: text/markdown`, a `.md` address, or `?mode=agent`.

# 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.

Subject: Computing · Area: Software Engineering · Ages 21 to 22
Page: https://lightmysky.com/learn/computing/working-in-a-team-issues-estimates-and-iterations-mt_HNNnVvADcF

## Ready when they can

- 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

## Lesson: Small pieces, honest numbers

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.

**Example.** 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.

**Tip.** 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.

**Recap.** Split work into reviewable pieces, estimate in honest ranges, and let each round's misses sharpen the next plan.

## Practice

8 questions on this page, each with its working shown.

## Needs first

- [Technical Debt and the Cost of the Next Change](https://lightmysky.com/learn/computing/technical-debt-and-the-cost-of-the-next-change-mt_iA8-0Qg4ID)
- [Requirements: Turning a Wish into a Testable Statement](https://lightmysky.com/learn/computing/requirements-turning-a-wish-into-a-testable-statement-mt_TFb-YNpvT1)

## Opens up

- [Dependencies, Licences and the Supply Chain](https://lightmysky.com/learn/computing/dependencies-licences-and-the-supply-chain-mt_2kilqPb0aV)
- [Scoping and Writing a Thesis-Scale Project](https://lightmysky.com/learn/computing/scoping-and-writing-a-thesis-scale-project-mt_Y46uRENRVf)