Yeah, a process like this is applicable to maybe 5% of development projects out there, and is definitely not ripe for abuse by all and sundry in the other 95%.

Yeah, a process like this is applicable to maybe 5% of development projects out there, and is definitely not ripe for abuse by all and sundry in the other 95%. Demonstrate you're producing valuable work on a regular, fixed cadence. Use whateve process you want to do so. The hard part is defining value somewhere below "the whole project is done." Harder than it sounds, people get it wrong all the time, astoundingly so, almost to the point where I'm convinced it's some sort of evolutionary defect.