I think there are types of projects where Agile/Scrum works well and makes sense and that's mostly in web or direct customer facing applications and especially

I think there are types of projects where Agile/Scrum works well and makes sense and that's mostly in web or direct customer facing applications and especially in those with either very quick or already setup infrastructure. There small changes can be presented quickly and iterations can be fast. Unfortunately I've been working in backend data movement since college where the final product is very well defined in the old waterfall model. Our intermediate tables aren't any use to the internal customers and there's not really much iteration needed, they come to us with data that's somewhere other than where they need it and we bring it to where they do. Recently though our org has taken to Agile/Scrum and the results are a little painful especially with our projects that require significant infrastructure setup, all of which is owned by external teams often understaffed so their backlogs are weeks to months long and while we're waiting on provisioning or approval from governance we're stuck looking for stuff to do that will meaningfully move things forward.