I was recently either watching some video content or reading something from a MS employee who essentially said that feature management wasn't intended to allow customers to permanently avoid new features but rather allow them to decide how soon before they became mandatory they wanted to test and implement. The implication of the comment was that every feature will eventually become mandatory -- of course I think we would all agree MS hasn't always been good at communicating when.
Our typical practice has been to review features by module, assess the impact, and then implement those that either provide required functionality early or have a low general impact. This has worked pretty well for us.
The area I struggle with is deciding when we should apply features for modules we don't use or use very lightly. For example, we have minimal usage of the HR Module but in 28 F&O had a pretty extensive release of updates to this area and functions like accrual balances, etc. We also see country and language-specific updates in regions we don't do business in. Do you apply these updates, which aren't necessarily relevant and you don't have a good way to test or leave them alone?
I'm interested in other processes for feature enablement.
