When developing software a popular agile approach is the feature driven development methodology. In short: create a prioritised feature list and plan development from that baselne. The approach is fine for many situations, especially for handling development cycles for a bunch of change requests or errors. However, the approach and especially the use of featurelists does have some disadvantages. First, I find it is a shame that the value of the product being developed is equal to the value of the users required features. Often users are keen on features that makes their life easier, makes the product nicer, or just pops up when asked. The outcome is that the feature lists often contain a lot of nice-to-have features such as 'the list must be divided into two horisontal panels', 'the colours must be customisable', etc. Second, nothing ensures that the features listed are supporting the desired business benefits. To address these risks for failure the desired business benefits should be outlined and the desired business process should be outlined. Finally, the featurelist must contain features ensuring the desired business benefits and these should be prioritised.