Some points of it seem apt and some are overblown. I’ve never met a product owner who didn’t create priority for important bugs, or who didn’t go along with en

Some points of it seem apt and some are overblown. I’ve never met a product owner who didn’t create priority for important bugs, or who didn’t go along with engineers laying in groundwork for long-term success, unless it was a case of “customer will not renew the contract without this”. But it is antithetical to agile, as this quote demonstrates: > Scrum’s roles, artifacts, events, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices But an official scrum guide is as bunk/bankrupt as the official Scrabble dictionary: not reflective of the real world. So what if you’re not doing the “official” scrum? How arrogant of the authors to claim they had any basis to be “official”.