SYSE.11:2 - Problem

A claimed increment is not decision-usable until the responsible engineers can answer:

1. Which actual System and starting configuration are changing?
2. Which receiving use, operating conditions, affected Systems, and interval bound the result?
3. Which changes belong inside the increment—for example, physical, software, description, procedure, or interface changes—and which remain alternatives?
4. Which input results are needed—for example, results from realization, platform, constituent coordination, configuration, specialist, or authority Work—and were they available before the Work that relied on them?
5. Which Agents performed which dated Work by which Methods, and which actual transformations and relations obtained?
6. What integration and operating observations support usability, and what claims remain unsupported?
7. What fallback, stop, separate assurance or release decision, and later change can reopen the result?

Without these distinctions, done becomes a proxy for actuality. Engineers can ship incompatible parts, overread a component test, confuse a release record with use, or keep adding features without producing a configuration that anyone can use.