2 ms·
I agree, but I think there's a still better way. If the "deadline" is too early, you risk unnecessary failure. If the "deadline" is too late, you end up develop
by wpietri 7y ago
I agree, but I think there's a still better way. If the "deadline" is too early, you risk unnecessary failure. If the "deadline" is too late, you end up developing to an arbitrary feature list again.
I'm a big fan of going hard for a minimum viable product. The notion is that you find the absolute minimum that will let you close the primary feedback loop: seeing what people do in the real world. Maybe it's only one set of users, like early adopters in a particular market segment. Maybe we leave out a lot of "real product" things, like help and docs, making up for it with handholding. But we ruthlessly cut scope until we have something in users' hands.
At that point, I think it's possible to shift from an internal focus (e.g., an arbitrary date or a made-up list of features) to an external focus, where we look at who's using it, who we're delivering value for, how we can sell it, and what the next most valuable improvements are. W release weekly or more often, driven by hypotheses and data. For me, that's when the real magic happens. Then we can focus less on internal politics, and more on what we're learning from the real world. And there's always something to learn.