This always annoys me. I land on a site that’s in a language I don’t understand (say, Dutch), and I want to switch to something else. I open the language selector and… it’s all in Dutch too. So instead of Germany/Deutchland, Romania/România, Great Britain, etc, I get Duitsland and Roemenië and Groot-Brittannië…
How does that make any sense? If I don’t speak the language, how am I supposed to know what Roemenië even is? In some situations, it could be easier to figure it out, but in some, not so much. “German” in Polish is “Niemiecki”… :|
Wouldn’t it be way more user-friendly to show the names in their native language, like Deutsch, Română, English, Polski, etc?
Is there a reason this is still a thing, or is it just bad UX that nobody bothers to fix?
It’s not my fault if the Scrum Master can’t provide a proper scope in the ticket. They said change the names, not the sorting.
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.
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.
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.