You're in deep trouble if a product takes 6 months to deliver. I deliver every couple of days, max. Every iteration creates a deliverable, so I deliver it. I learn what to do next as I'm doing the current thing. I have a continuous dialog with my customers to facilitate that.
---
RT @BarryLSmith
@allenholub Still not getting your point, @allenholub …. If a product may take a team 6 months to deliver, what do you consider an allowable …
https://twitter.com/BarryLSmith/status/1624811695402283010
Barry L Smith on Twitter

“@allenholub Still not getting your point, @allenholub …. If a product may take a team 6 months to deliver, what do you consider an allowable backlog (= work plan)? If they expect to take multiple iterations to produce a capability, are they not allowed to document the anticipated work?”

Twitter
@allenholub I don’t believe a first release of a product people will pay money for can be delivered in a couple of days, sorry. Once that first release is out and you are adding features to it you are definitely right though
@ecomba I've seen the contrary many times. They won't pay much, but they'll pay something. That tells you your product idea is viable. I won't stop you if you want to work in a waterfall with an infrequent big release, but I'd never consider doing that myself. I find that iteration and continuous feedback works much better.
@allenholub when I use the word “released” here I mean a product someone (business or consumer) will pay for
@ecomba An MMF is not an MVP. I release the MVP.
@allenholub I’d love to jump on a call with you and hear about that. It’s not the software creation/release that piques my interest, but how you get some company to pay for a week old product!
@ecomba What's the core of the core of the core idea? Take what you think of as the minimum marketable product. Cut that in half, and in half again, and in half again. That's your MVP. Build and release that. If the idea is viable, somebody will be willing to pay for it. If you can't find anybody who will pay for it, then the product isn't viable.
@allenholub I know the theory, don’t see it (people paying for it) in reality

@allenholub Over the years, I've been leaning more towards the bootstrapped Saas/indie hacker communities and how to build something someone would pay for works differently (with data from hundreds of successful saas businesses).

Simplified version: Validate the Market, market your product idea, and build.

If you don't validate the market, you might build what no one wants (a waste of time and money).

@allenholub If you don't let the world know about the product you want to build, you won't have any interest (even if your idea is good), and you will also waste time and money.

And if you build without having validated the market or marketed your idea, you most likely will build something no company will want to pay any money for; at the end of the day, you want to solve a real problem someone has.

@ecomba Best way to let the world know about the product is to release early and often. Sell strategic goals, not features.