Please login or join to subscribe to this thread
Being a Scrum Mom could be detrimental to the team over time as they could become very dependable on others doing some of the things they should be and when you reach to that stage, it's difficult to reverse the effect as it will demotivate the team.
Always be aware how much pampering you should be doing as a Scrum Mom !
Thank you for sharing your opinion, I fully agree with your words, my favorite scrum mom’s motto: “Right or wrong, my team!” and then the team isn't challenged so intended performance is never achieved.
What in the world is a Scrum Mom?
For me Scrum is becoming ridiculous and I feel fortunate not having to work with it anymore. The value of a team is given by the value of its members and here the technical skills play the most important role. The performance of a team has nothing to do with ceremonies and odd terms such as Scrum Mon, Dad, Grandmother.
For me it looks like in many cases the focus is no longer on the actual technical software development issues but it has shifted to some sort of religion where very often people that have never written a line of code in their lives give lessons to the technical staff.
Thank you for sharing your opinion, I do not fully agree with you in my 20 years of IT most of the road blocks are not technicals, but with side situations , several unacessarie delays in the project that affects the performance of the team. However Scrum mom is not a ceremonie, but only the name (alias) that we give to the scrum master when he is overprotective, when is always prevent failing, when blocks all negative feedback from the stackholders, etc... He care so much in doing a good work and protecting the team, that his work is impeding the team of evolve and obtain a real feedback.
It's normal that you don't know the meaning of Scrum mom if you do not appreciate scrum or read about it.
PS : The performance of the team is related with all the environment where she is inserted, so all counts even when you have team members with excepcional technical skills.
For the whole project yes probably non-technical issue may cause more blockers but when it comes to the actual ability of the team to deliver, the non-technical issues have nothing to do it.It is all about the hard (technical) skills.
If the sponsor/business is not acting properly and if the PM is not facilitating properly then yes the project can fail or produce poor results even if a high performing team is employed to do the job. For example the team can produce an extraordinary product in a short period of time but that may not be what the businesses needed or wanted. Or because of poor communication it could take longer to finish the work because for example it can take a long time for the business to make decisions.
Whether the Scrum Master is a Mon or not would not impact the performance of the team. The developers would not be a doing a better or a worse job. They would be working at the best of their abilities no matter the methodology used. And their abilities would influence the outcome. The developer would spend most of the time doing his job without caring about the Scrum Master, PM, business user etc.
Maybe in the OP, provide insight into what it is.
Lyssa Adkins provides a ton of great advice in her Coaching Agile Teams book.
Chris Corrigan on taking ownership: "Everything you do for the group is one less thing they know they can do for themselves"
Team apathy and laziness is a risk if the SM starts to be a mum or a manager. I have worked with teams that regularly rotated the SM role between team members, which seemed like a fine way to keep people engaged and committed.
Who are (are) the owners of the process?
If you want to teach team members all the time to do their job, how do you think they will feel?
Never heard that term. At first I thought I read Soccer Mom.
Please login or join to reply