Chapter 2 · Practice 4 of 4
Avoid scope that depends on data, hardware or people you do not control
Why it matters
Many projects stall for weeks waiting on something outside the team: a hospital that promised a dataset, a company API key that never arrives, sensors that have to be imported, a client who stops replying.
For every outside dependency, write down:
| Dependency | Who controls it | Do we have it today? | Fallback if it never arrives |
|---|---|---|---|
| Patient records dataset | Partner hospital | No, verbal promise | Public dataset or synthetic data |
| GPS hardware module | Market supplier | Ordered | Phone GPS for the demo |
If a must feature depends on something you do not have yet, either get it before the proposal is approved or move that feature to the could group. Examiners often ask about data access; having the answer in writing is a strong signal of feasibility.
Do
- List every outside dependency with a fallback
- Secure critical data or hardware before approval
Avoid
- A must feature that rests on a verbal promise