Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
The scrum master is not a product owner and shouldn't be providing scope or anything for that matter in tickets. No wonder agile is hated and dying, it's been corrupted beyond recognition by people who have no reading comprehension.
The product owner often doesn't understand technology well enough to know that mapping labels and sorting are different. They don't know what they don't know. The SM needs to help bridge that gap.
Sure, part of the job of the SM is to teach a PO that they need to research the market, but bridging the gap sounds like your saying the SM should find these things out for themselves and that's just not true. The SM by definition is less technically minded that the PO. They deal with processes, data and people, not with product specs and market research.
I think that the basic ideas are reasonable. Keep in touch with your team and evaluate the current situation, track progress, stuff like that.
It's just that the excessive codification of the practices becomes overbearing.
True, what you described is basically all there is to it, but in my opinion the corrupted versions where the SM is doing backlog management or where the rest of the company structure doesn't change just the dev team are more damaging than the more codified versions of it.