As a design pattern, Scrum purports to work for certain development teams, doing certain kind of work, with certain kinds of requirements, timelines, stakeholde

As a design pattern, Scrum purports to work for certain development teams, doing certain kind of work, with certain kinds of requirements, timelines, stakeholders, etc. Additionally by being modular, it purports to accommodate even wider ranges of these requirements. The only questions are * Does your particular development team and lifecycle fall under this spectrum? * What alternative patterns also might apply? And what's the right criteria to evaluate competing patterns? The answers are increasingly clear that Scrum works in a small minority of development scenarios, maybe < 5%. So it should be treated as a niche pattern applied when certain specific pathologies exist in your current SDLC / team. It's also helpful to understand those boundaries, and how misapplications of Scrum manifest in real world delivery mamagement. I wish this article was a bit more holistic, instead of a quasi-rant.