Sure, in a way.
Every time a new automation project gets discussed we (automation, QA and sometimes Dev) discuss if time and money spent on automation is worth it.
If this is an easy one off test that probably will only be done very infrequently automation is not worth it.
If this is a complicated and boring test that needs to be done over and over ad naseum, automation is your ticket.
You need to determine the cost/benefit to everything you do so that you can generate the appropriate ROI for you company. There are lots of factors that may or may not be important to you and your company and all of those important ones need to be accounted for.
This does not mean that you must spend hours talking about each potential automation project but sometimes a quick, "hey is this really worth it" can suffice.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!
Thanks for your response Ciege, but i think you are talking about ROI. What i am talking about is something like this:
1) VALUE: Business criticality of test cases?
2) SCOPE: Is automation of the application dependent on multiple applications?
3) STABILITY: How stable is the application environment? (i.e. does GUI or functionality change often)
4) MARKET DATA: Does automation depend on market data during market hours? (i.e. can only fill within +/- % of market price)
5) REPORTING: Does testing involve transaction reporting or compliance reporting?
6) COMPLEXITY: How challenging is the test case? (i.e., Does testing require scanning log files, querying databases, bouncing processes, manipulating data)?