> Scrum forces the client to decide which features are most important Aaaaah, I think it's fair to say that Scrum forces the client to declare which features a

> Scrum forces the client to decide which features are most important Aaaaah, I think it's fair to say that Scrum forces the client to declare which features are most urgent and that in the ideal project the client aligns urgency and importance. However, just like real life, it is difficult to align these two orthogonal concepts. Sometimes things become urgent because they are tantalizingly easy to do. Sometimes things become urgent because someone important thinks they are important. Sometimes things become urgent because the client is personally invested in them. I agree that "as long as the most important 80% works chances are the project will be considered useful even if it does not do everything," but I am cautious about assuming that just because you ask the client to name the most important features ona sprint-by-sprint basis that you will agree in hindsight that the most important 80% of a product got done.