I don't think the way you are describing -with missings of clear scrum events (refinements (to clearify userstories)/retrospectives (listen to feedback to improve in a next sprint)/...) and essential, potential iterations by acceptance testing- is purely scrum, the agility is also far to find for me. Neither seems this a best practice to implement a Mendix project, more a waterfall.
BUT may this is the type of working which suits the organisation the most.
What is scrum for you, for your developer?
Why do you/your developers think that your/their scrum way should be applied in this organization (will it imply better software)?
Did you talk (convince) the team/PO/manager director?