Hi Rini, thank you so much.

For value: you mainly looking on what user pain points you addressing and how much added value you creating. It may be a bit subjective but as mentioned in other response shouldn’t be based on user research and validated with them.

As for feasibility, after you have rough expectations of the given functionality you gathering estimates from dev, and other teams to evaluate how much resources(time, money etc) will be required to implement it.

Goal of the exercise is primary to help prioritize features( even if it’s a-bit subjective), focusing on things that we can provide to users relatively fast and create immediate impact.