How to use testcomplete in Agile

I am facing a similar issue in my current position of how to work in test automation in an agile environment.

The primary concerns I have are reusability and where to focus our efforts.

I have for some time been automating our test cases just for the sake of getting them done and appeasing my coworkers who are desperate to justify their necessity - but where does the meat go? I have yet to see any value in this type of automation. In fact I find writing test cases to be a complete waste of time and added fluff to the QA process. Writing out scenarios and breaking down requirements into meaningful action items to test I have found to be pretty useful but writing out all my steps for everything I test...waste of time.

Just as I drive to work every day I do not need to write the steps and document every turn I take to arrive at my destination. I do it quite well on my own - naturally - because I have done it for some time now and I am familiar with the steps involved to start my vehicle and arrive at work. Sure I occasionally look for alternate routes - or maybe even drive somewhere besides work - but the maps do not apply to subsequent trips and therefore do not see a purpose to keep them around.

I know how to drive my car - I know how to use google maps - I'm prepared for whatever lies ahead.

So automation can jump through a bunch of steps with different data sets, but so can I - and I learn more - catch more - do it faster without having it automated or wasting time on the fluffy redundant documentation of that process.

So I have typically been leaning towards Automation being valuable only in regression testing.

What do you all think about test cases and can you elaborate on the greatest value that automation has in the agile environment?