According to its inventor, Scrum™ was created to manage a team of dysfunctional COBOL programmers at a bank. But they're selling it to non-technical managers as a panacy for all SW development problems (and making ridiculously false claims in the process).
"Agile"/Scrum/SAFe is everything that is wrong with our industry.
Don't let me start with storypoints, or SW time estimations in general. Shape Up method using "appetite"[2] instead - a fixed length variable scope time budgets with circuit breakers[3].
Most modern SDLCs are mini-waterfalls with SDUF (Some Design Up Front).
Examples: informal mini-waterfall at FAANG ( design->plan->build(iteration)->ship ), Shopify's GSD (Get Sh*t Done), Shape Up method[1], Event Modeling, EventStorming.
The uniquence of the EventModeling is that it uses a single paradigm - visual canvas/board for almost everything: requirements gathering, UI/UX, Software Design, documentation, and Project Management.
--
1. https://basecamp.com/shapeup
2. Appetite
The amount of time we want to spend on a project, as opposed to an estimate.
https://basecamp.com/shapeup/4.5-appendix-06
3. Circuit breaker
A risk management technique: Cancel projects that don’t ship in one cycle by default instead of extending them by default.
