I don't agree, most points are false, or a misthought version of scrum is taken as a reference. E.g. "minimal amount of work" doesn't mean that it must be cheap

I don't agree, most points are false, or a misthought version of scrum is taken as a reference. E.g. "minimal amount of work" doesn't mean that it must be cheap or rushed - it means that it has to satisfy the need of the stakeholder, whoever he is. It's the team to evaluate the costs of each point, and the PO decision starts from there. The product decisions taken by the PO are about needs, priority and value, not about implementation or experience. And moreover, the "pride" in making your own code part... that's where the author totally misses the point. The main shift of agile is mindset, the shift from "I did it so I know it and I take pride from it" to "WE did it, so WE know it as a team and WE take pride of it". If you're not ok with the sharing, please go back to waterfall.