The trouble with Scrum
For about the last ten years, most of the development shops I’ve seen and worked with are operating under a process that is Scrum-like on the surface. It’s standard to divide work into “stories,” to assign points to those stories, to organize time into “sprints” that are just about always two weeks, and to move those “stories” from left to right on a Jira board.
I have many, many things to say about how people mess up Scrum. A lot of it is embedded in the prior paragraph: they’re “Scrum-like” on the surface but they don’t even try to embrace the values of “commitment, courage, focus, openness and respect” that the Scrum Guide calls for.