Requiring permission from a Change Advisory Board after a change is complete is absurd. A system has to be broken to need any discussion by that stage. Fix the system and kill the CAB. Its possible.
All application life cycles - even the funky new Agile/DevOps ones - will degenerate into the trad old generic app support model as the business loses interest and the build team loses funding, unless of course the app gets retired first.