I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
Thank you, David. Glad you found the list useful.
Oh yes, Scrum is a touchy subject :) It has lots of haters. It is interesting that, in your case, you feel like the Scrum Master is the main problem. You were probably exposed to a bad one (or two).
Unfortunately, Scrum is often implemented poorly and partially. People pick and choose parts of it, they think that the word "Master" means something that it doesn't mean, and they don't really understand the big picture... for example, when it should be used, when it shouldn't, why certain things are in done in certain ways, etc.
The book in the list gives a good foundation for that understanding. I am going to venture to say that, if you didn't have good experiences with Scrum, that is probably a perfect book for you to consider. Just to consider :-) ...and yes, I know you probably won't, and you probably have real horror stories, but I had to try... :) :)
Lorenzo - you're response is very close to what I've been thinking about Scrum. I'm a grizzled veteran programmer with way too much experience to be affected by what a peach-fuzz wannabe manager thinks I should be doing between now and lunch. It creates bad blood, as you might imagine.
I ordered three books off your list! Innovators, Practicing Mind, and Quiet.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you, David. Glad you found the list useful.
Oh yes, Scrum is a touchy subject :) It has lots of haters. It is interesting that, in your case, you feel like the Scrum Master is the main problem. You were probably exposed to a bad one (or two).
Unfortunately, Scrum is often implemented poorly and partially. People pick and choose parts of it, they think that the word "Master" means something that it doesn't mean, and they don't really understand the big picture... for example, when it should be used, when it shouldn't, why certain things are in done in certain ways, etc.
The book in the list gives a good foundation for that understanding. I am going to venture to say that, if you didn't have good experiences with Scrum, that is probably a perfect book for you to consider. Just to consider :-) ...and yes, I know you probably won't, and you probably have real horror stories, but I had to try... :) :)
Lorenzo - you're response is very close to what I've been thinking about Scrum. I'm a grizzled veteran programmer with way too much experience to be affected by what a peach-fuzz wannabe manager thinks I should be doing between now and lunch. It creates bad blood, as you might imagine.
I ordered three books off your list! Innovators, Practicing Mind, and Quiet.