Relative Mass Valuation

Correct Answer: They should compare the client-ordered features to each other in terms of their relative value, and prioritize it accordingly.

The Relative Mass Valuation technique involves comparing features to each other based on their relative value. Therefore, the Scrum Team should prioritize features according to this. This means that the order given by the client is not strictly followed but is used as a base for the prioritization, but the final order depends on the relative importance of these features. The other answers are incorrect for the following reasons: - Considering all features as equally important isn't aligned with the concept of the Relative Mass Valuation technique, which is about understanding the varying weightings of importance between different features - Prioritizing features based on their complexity contradicts the principle of maximized value which should guide the work in Scrum. Simply because a feature is complex does not automatically make it more valuable than a less complex one - Following the client's orders strictly without considering the value of the features could lead to time and effort being expended on features that are of little to no value to the end product. This is not a sensible approach to prioritizing work in Scrum.

Correct Answer: They should consider those tasks as the functioning of features depends on them.

In a Scrum project, all tasks that contribute to the functioning of the features, directly or indirectly, should be considered for a relative mass valuation exercise. Even though some tasks might not provide direct business value, they are essential for the overall functioning of the features. Therefore, the team should definitely consider these tasks. Disregarding tasks because they do not provide direct business value (as suggested in the second answer) could result in missing critical aspects of the project. Only considering tasks if they are critical and cannot be avoided (as hinted in the third answer) also isn’t a good practice, as it omits significant tasks that support the project's functionality. Finally, while involving the Product Owner in decision-making is a good idea, relying solely on their judgment for these tasks (as suggested in the fourth answer) would take away the teams' role and autonomy in planning and executing work.

Correct Answer: The team should adjust the relative values of the existing and new features to incorporate the changes.

In the Agile Scrum framework, the product backlog is not a fixed document and should be adjusted regularly based on new insights, changes, opportunities, and market dynamics. If during the development the Scrum Team has discovered new features with higher value, the optimal way to adjust to these changes is to re-assess and adjust the relative values of the existing and new features. This allows to incorporate the changes and ensure the highest value features are being worked on. The idea of neglecting the new features until the current sprint is completed contradicts the fundamentals of Agile which values responsiveness to change. Abandoning the Relative Mass Valuation technique and starting to prioritize features based only on development effort is not optimal as it may overlook the true value or impact of the features. Adding the new features to the bottom of the list, despite their high values is not logical or efficient. This approach might lead to misallocation of resources, as higher value features could be delayed.