The most agile teams I have been on in my career did not use Scrum, so asking if one needs Scrum is indeed a good question. In fact, Scrum is a very poor fit for Behavior-Driven Development, and Scrum also is a poor fit for participatory product design. And Scrum dismissed the reality that not everyone is a generalists, and defines no way to incorporate experts as extended team members, or how to work with expert teams such as machine learning teams. And the PO role is a huge dysfunction. And, Scrum tends to create a feature mill, with ideas flowing only toward the dev team and never in the other direction, which is a huge dysfunction because if developers undeerstand how the product is being used, they will often have great ideas. And Scrum does not address cross-team collaboration for situations in which there are tens of teams, and tens of products (each having tens of teams) - and the cross-team issues are the hard ones: a single team is table stakes.

My advice: stay away from Scrum. Go to first principles and ask how you should be doing things, given the nature of your product, your org, and your challenges.