There are two main tenants of Scrum that, in my opinion, define it and tell you the worth of it for any project or product. Those two are: changing requirements and iterative releases.
There are many great posts on this site about Agile vs. Waterfall. The bottom line is that Waterfall is amazing if you can gather all the requirements up-front, and they won't change much. The hard part is getting those requirements right, on paper, before doing any of the work.
This means that waterfall would apply very well to industries like automobile, healthcare, aerospace, etc. where it's easier to clarify up-front what exactly you need.
On the other hand, iterative releases are very, very useful -- even with fixed and un-changing requirements. You could theoretically do it, but I don't see what benefit you'd get out of it.
Instead, I would focus on some other useful parts of Scrum, such as:
- Estimating tasks in vaguer units (story points) instead of time -- if requirements are unknown and/or changing.
- Breaking work down into small units that can be completed in a week or two, or less.
- Communicating daily across the team to say "here's what I did yesterday, what I'm going to do today, and what I got stuck on."
Your mileage may vary. I would say look at Scrum/Agile, and start pulling those practices that you can see will benefit you.