The last time you deleted or closed some unfinished work, what lead to that situation?

No amount of design is sufficient without exposing the feature to real life users.

I understand where this question comes from. But it's the wrong question.

Be represented in the upcoming State of DevOps report

Ask 10 people what "Agile" or "DevOps" means, and you'll get 15 answers. The terms have essentially become meaningless.

Surprises about what to build are the rule, not the exception.

Work closely with the users of the software, and establish tight feedback loops. No framework necessary.

Listen as I discuss Go, DevOps, and more, with Lane Wagner on the Backend Banter podcast.

When we buy outcomes, rather than inputs or outputs, we align the supplier's desires with our own

If this claim is true, there are only two possible explanations. Neither one is very convincing.

The question assumes that scope creep is something to be managed and/or prevented.