I am very adamant about following a strong scrum cycle (although, I'm loose with the details).
* Build a backlog
* Run a sprint (I like 2 week sprints at startups)
* Don't put anything new in the current sprint unless absolutely necessary.
* Rinse and repeat
The simple nature of having a "waiting" period for new features helps put perspective on them while giving you time to make sure they're broadly useful. If only a single person is asking for them, wait to build.
> Don't put anything new in the current sprint unless absolutely necessary.
As Jason Fried of 37Signals would say, "Launching something great that’s a little smaller in scope than planned is better than launching something mediocre and full of holes because you had to hit some magical time, budget, scope window."
* Build a backlog
* Run a sprint (I like 2 week sprints at startups)
* Don't put anything new in the current sprint unless absolutely necessary.
* Rinse and repeat
The simple nature of having a "waiting" period for new features helps put perspective on them while giving you time to make sure they're broadly useful. If only a single person is asking for them, wait to build.