There are certainly some more advanced langauge features in Scala. If you can levarage these, they can make your life as a developer easier but honestly, language choice isn't my biggest problem. So anything you go to management with is at best subjective.
There are syntax features which you'll love and miss going back to Java (pattern matching and for-comprehencions for example) and you may find Scala's library APIs for intuative (the collections are easier to work with to map over etc and the API for Option/Optional is just better and the lambda syntax is more concise and their usage more flexible) but... if you're used to and productive with Java's stream API and have gotten used to Optional's API, there's not a complelling argument either way.
I've certainly worked with teams that felt Scala was more modern and would attract great talent, so the switch was motivated by recruitment.
If you're interested, I have a real world project that was written in Java 8 and ported to Scala. Both versions are available on branches at https://github.com/tobyweston/radiate
for direct comparison but it's not really a question of which has less code IMO, the Scala version affords a more pronouced move towards FP. It may (or may not) have less code but its certainly different! For example, using type-classes in Scala (which isn't possible in Java) makes for an interesting read.