I feel sorry for the author of the article for working at such a company.
This person happens to be working at a company, where they’re not even taking Scrum seriously. What they’re doing, is in fact, not Scrum.
When it’s done correctly, it does make the team very productive and even enthusiastic, but - since it’s a teamwork - a great team is needed for that.
It’s true that it isn’t easy to do Scrum right. It is in the Scrum guide too: easy to understand, but hard to master.
I did have a chance to work in an amazing team at a great company, where the leadership, as well as our Scrum master were determined to stick to the Scrum guide as much as possible (way too many “Scrum” teams make an alternate “Scrum” for themselves, with which they’re essentially ruining it).
In our case, we didn’t start out perfect either! We failed most of our sprints, but the management still believed in Scrum, and sent the whole team to a Scrum elevation training each year. Even as an introverted person, I have to say, they were really fun and they were good as team building events too, besides the training itself. We always returned to the office with greater enthusiasm after each training, and our enthusiasm always lasted longer and longer. At the end our team was like a “rock star” team at the company, the management, the leadership, our scrum master, all of them were proud of our achievements. We never failed a sprint again, and we also put the necessary overtime in when it was needed.
Those were the good times. Unfortunately I haven’t managed to work in such a Scrum team again, and everywhere where I had an interview, they always had their own version of “Scrum”.
Most likely the author of the article won’t read this, but my message is, if you think, Scrum sucks, then in reality, your team (and maybe your company too) sucks.
I feel sorry for the author of the article for working at such a company.
This person happens to be working at a company, where they’re not even taking Scrum seriously. What they’re doing, is in fact, not Scrum.
When it’s done correctly, it does make the team very productive and even enthusiastic, but - since it’s a teamwork - a great team is needed for that.
It’s true that it isn’t easy to do Scrum right. It is in the Scrum guide too: easy to understand, but hard to master.
I did have a chance to work in an amazing team at a great company, where the leadership, as well as our Scrum master were determined to stick to the Scrum guide as much as possible (way too many “Scrum” teams make an alternate “Scrum” for themselves, with which they’re essentially ruining it).
In our case, we didn’t start out perfect either! We failed most of our sprints, but the management still believed in Scrum, and sent the whole team to a Scrum elevation training each year. Even as an introverted person, I have to say, they were really fun and they were good as team building events too, besides the training itself. We always returned to the office with greater enthusiasm after each training, and our enthusiasm always lasted longer and longer. At the end our team was like a “rock star” team at the company, the management, the leadership, our scrum master, all of them were proud of our achievements. We never failed a sprint again, and we also put the necessary overtime in when it was needed.
Those were the good times. Unfortunately I haven’t managed to work in such a Scrum team again, and everywhere where I had an interview, they always had their own version of “Scrum”.
Most likely the author of the article won’t read this, but my message is, if you think, Scrum sucks, then in reality, your team (and maybe your company too) sucks.
I’ve worked on by the book scrum teams, and not by the book scrum teams.
Scrum is dogshit.