What guidelines should we follow when considering a feature?

Question

I think we should come up with some guidelines to help determine whether features are appropriate when considering them for inclusion.

This doesn't have to be a strict set of rules, just guidelines to help facilitate the decision making process.

Answer 1

Features should meet at least one of these guidelines, listed in no particular order:

• Does it significantly improve playability? That is, does it make the gameplay more intuitive or less awkward? For example, the ability to cancel any decisions made before the turn is complete.
• Is it necessary for balance? If we don't have the feature, is there a high risk of one player gaining an unfair advantage over the other? For example, some mechanism for preventing infinite combos, or some disadvantage given to the player who gets the first move.
• Do we need it for completeness? Will we not have a finished product without this feature? For example, an overall theme, or an API hook for some game mechanic.
• Does it significantly improve enjoyability? If we think players will play longer and more often with this feature, we probably want it. For example, achievements or leaderboards. 

If a feature meets these guidelines and we decide we want it, we still need to prioritize. Do we really need this feature for our next milestone, or can it wait?

---

Please comment if anything looks wrong here or if more things should be added, or suggest something entirely different if you don't agree with these guidelines.

Comments

I agree with the guidelines. But "the ability to cancel any decisions made before the turn is complete" is a bit unclear, is that meant as an example of an intuitive feature?

---

It was supposed to be an example of a feature that would improve playability... something we might not have at first, but if someone says "I want this feature," it would be worth considering under these guidelines because it would improve playability.