Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Scrum is quite popular dev.process these days and often Project Manager suddenly gets new title (Scrum Master). However it should be not just a new title, but new habits and new paradigm. What are the bad habits of your Scrum master?
The big bad habit our Scrum Master had at first was thinking we would take care of our own impediments. That’s one of the things the Scrum Master is supposed to do but she left it to us until it got unmanageable.
The other thing we’ve dealt with is the Scrum Master thinking they were in charge of riding the developers’ backs until tasks were taken care of. This creates a bad atmosphere on the team since they’re supposed to be self-managing.
To me and our team, the Scrum Master’s job is to be a shield and assistant for the team, blocking impediments and doing what they can to help expedite things. Ken Schwaber’s Agile Software Development with Scrum is an excellent intro to Scrum, it’s what our team used and we’ve been pretty successful with it. There’s also Agile Project Management with Scrum, which is more for the Scrum Master and Product Owner roles specifically.