Many in the agile community have no clue what Capabilities are needed for their products since their customers don't know that until they see the working software. This doesn't mean those capabilities could not be discovered - that's the role of product market research. But it may be cheaper just to start building software, get the feedback and build new software - may be on a daily basis.

What's not addressed by these just build it advocates is what the Value at Risk for building the wrong thing. But that's another topic.

When you hear someone suggest something that doesn't make sense in your domain, you're probably right - it doesn't make sense in your domain. Ask in what domain are you making that suggestion? And, why do you think what works in your domain will work in my domain?

Many in the agile community have no clue what Capabilities are needed for their products since their customers don't know that until they see the working software. This doesn't mean those capabilities could not be discovered - that's the role of product market research. But it may be cheaper just to start building software, get the feedback and build new software - may be on a daily basis.

What's not addressed by these just build it advocates is what the Value at Risk for building the wrong thing. But that's another topic.

When you hear someone suggest something that doesn't make sense in your domain, you're probably right - it doesn't make sense in your domain. Ask in what domain are you making that suggestion? And, why do you think what works in your domain will work in my domain?