Part 9 of 12 · 2 min read
Mistakes that leave a capstone unscoped
Common mistakes, and what the example does not do.
Mistakes that leave a capstone unscoped
- No baseline, so there is nothing to beat.
- Several users or jobs in one project.
- A target without a number or an evaluation set too small to show it.
- Estimating in medians and planning to the median.
- Building features before the evaluation harness.
- No cut line until the last week.
- Adding an agent where a rule would do.
- Never showing a real user.
What the example does not do
About this example What the example does not do
- No real project: the capstone, hours and spreads are invented. Your own tasks will have different shapes.
- Independent task durations plus one shared factor. Real tasks have dependencies, blocking and rework.
- The last-mile curve uses two points from one reported case and assumes exponential decay. It is a way to think, not a forecast.
- Item counts use a normal approximation and an assumed disagreement rate.
- The checker's text rules are crude: a vague user can slip past them and a good one can trip them. It is a prompt for questions.
- No budget model beyond a per-task cap, no user research method, no market analysis.
- Optional real experiment: write your own scope, estimate each task with a low, likely and high hour figure, track actuals for four weeks and compare them with the simulated 50th and 80th percentiles.
Check yourself
What does a scoped project look like in one sentence?
Show answer
For this user, the agent does this job, and you can show this measured result against this baseline. Two users, two jobs or no number means it is not scoped yet.
For the curious Plans slip, so cut by confidence and not hope
In the fictional plan (11 features, 116 hours of estimates against 80 available), the full plan had a 5 percent chance of finishing in 80 hours; core plus important 54 percent; core only 88 percent. A shared project-wide delay factor widens the tail. Keeping features until the 80th percentile fits left 4. The spreads, hours and the one-anecdote last-mile curve are assumptions; nothing here was built.
What you will use daily at work
| Practice | What it looks like |
|---|---|
| Write the scope sentence first | User, job, metric, baseline, target. |
| Build the non-agent baseline early | Rules, one prompt or the human process. |
| Size the eval set to the gain | Floor of about 100 items. |
| Decide the cut line before starting | Estimate with a spread, not one number. |