Well, I've been developing software for more decades that I'd like to admit, so I've engaged all the issues you mention (and many more). However, the fact that

Well, I've been developing software for more decades that I'd like to admit, so I've engaged all the issues you mention (and many more). However, the fact that these problems exist doesn't mean this agile fluency model has anything to do with solving them. Generally, my problem with this model is that it's arbitrary, vague and subjective. You, your team, and other stakeholders will need to take the time to learn the model, restate your issues in terms of the model and then... what? Even then, what steps or anything else actionable could result? In fact, the agile fluency model itself is pretty daunting, what with all the new terminology (all based on terms that are already massively overload, of course). We'd probably need an Agile Fluency Model Fluency Model, so we can label and discuss the stages of learning and applying the agile fluency model itself.