3 ms·
Why isn't there: - a very strict requirements collection phase: You're only green-lighting one app a month, surely you could spend some time frontloading the d
by alanctgardner2 13y ago
Why isn't there:
- a very strict requirements collection phase: You're only green-lighting one app a month, surely you could spend some time frontloading the decision making so the people proposing the idea can be very specific.
- an MVP phase: build as little as possible to have a functioning product. Everyone needs to agree what the MVP is before starting, which is the purpose of the requirements gathering.
- bounties: get the people who set out the requirements to "kickstart" the project by kicking in cash. When the project is green-lit, the cash is apportioned to the tasks within the MVP and stretch goals - additional features to supplement the MVP.
It seems like there's too much of "we'll let everyone do everything!". The developers don't need to be making decisions about what features are worthwhile, the people who pay money should have some skin in the game. If people stand to gain real money, there's got to be a gatekeeper who decides whether a merge is worth paying for.